From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: Eric Wheeler <cocci@lists.ewheeler.net>, cocci@inria.fr
Subject: Re: [cocci] Can Coccinelle concatenate or append to existing string literals?
Date: Sun, 13 Mar 2022 14:00:12 +0100 [thread overview]
Message-ID: <aee7f53b-63d2-2312-4702-7f65bc43b705@web.de> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2203131056330.18925@hadrien>
>> Will another test result for a SmPL script like the following trigger any further
>> collateral evolution?
>>
>> @addition@
>> @@
>> void f()
>> {
>> foo("foo"
>> + "_bar"
>> );
>> }
> Maybe this would be a good thing in principle,
Will the chances grow to improve Coccinelle software components
so that similarly simple source code adjustments will become directly supported?
> but I don't think it would be the desirable solution in Eric's case.
I am curious how the extended transformation approach will look like.
> He should just use python to construct the string he wants.
Other scripting languages (OCaml for example) can provide further design options.
> In that way, the user will better be able to connect the output to the string
> that is found in the code.
How many development efforts would you like to invest for expressing desirable changes
in a succinct way?
Regards,
Markus
next prev parent reply other threads:[~2022-03-13 13:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-13 0:53 [cocci] Can Coccinell concatinate or append to existing string literals? Eric Wheeler
2022-03-13 7:05 ` Julia Lawall
2022-03-13 9:45 ` [cocci] Can Coccinelle concatenate " Markus Elfring
2022-03-13 9:57 ` Julia Lawall
2022-03-13 13:00 ` Markus Elfring [this message]
2022-03-13 16:31 ` [cocci] Can Coccinell concatinate " Luis Chamberlain
2022-03-13 17:24 ` [cocci] Can Coccinelle concatenate " Markus Elfring
2022-03-13 17:33 ` Julia Lawall
2022-03-13 18:30 ` [cocci] Checking the construction of a fresh identifier Markus Elfring
2022-03-15 2:40 ` [cocci] Can Coccinell concatinate or append to existing string literals? Eric Wheeler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aee7f53b-63d2-2312-4702-7f65bc43b705@web.de \
--to=markus.elfring@web.de \
--cc=cocci@inria.fr \
--cc=cocci@lists.ewheeler.net \
--cc=julia.lawall@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.