From: Markus Elfring <Markus.Elfring@web.de>
To: Jakob Koschel <jkl820.git@gmail.com>
Cc: Julia Lawall <julia.lawall@inria.fr>, cocci@inria.fr
Subject: Re: [cocci] Working with parameter/expression lists by SmPL
Date: Fri, 19 Aug 2022 19:00:29 +0200 [thread overview]
Message-ID: <d9e428c2-f4d2-13bb-bf42-447a1f0ffa73@web.de> (raw)
In-Reply-To: <17A83354-2406-47E5-94EE-4955E09819DA@gmail.com>
> I'm trying to detect certain code patterns spanning across files with this.
> They will *probably* not easily be automatically patchable since I'm trying to
> find bugs with this in an ongoing research project.
Would you like to add a link for this evolving information source?
> You're right, the positions can be omitted here, but I'm using them with a
> simple python script afterwards to report the matches I found where the positions
> will be useful.
Would you like to improve the distinction for the usages of mentioned variables
any further by using operation modes (or variants) for SmPL scripts?
Would it become helpful to use the name ”interesting_func” as another metavariable?
>> …
>>> +++ /tmp/cocci-output-test1.c
>>> @@ -6,7 +6,8 @@ int interesting_func(int argc, char *str
>>> }
>>>
>>> int main(int argc, char *argv[]) {
>>> - int x = 0;
>>> + int x = 0
>>> + // test;
>>>
>>> func1(x, "asdf");
>>> }
>> Do you vary comment additions for your test results?
> yes exactly.
Do you stumble on any more development challenges for adding comments
by the Coccinelle software?
How do you think about possibilities to add multi-line comments
(instead of specifying desirable messages behind double slashes)?
https://en.cppreference.com/w/c/comment
Are you looking for better source code formatting according to semicolons?
> Only issue I'm having now is that it doesn't work across files.
Would you like to explain remaining development concerns any more?
Regards,
Markus
next prev parent reply other threads:[~2022-08-19 17:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 8:54 [cocci] match arbitrary argument position Jakob Koschel
2022-08-16 11:37 ` Julia Lawall
2022-08-16 12:35 ` Jakob Koschel
2022-08-16 17:55 ` Markus Elfring
2022-08-17 14:26 ` Jakob Koschel
2022-08-17 19:21 ` Markus Elfring
2022-08-16 21:07 ` Julia Lawall
2022-08-17 14:18 ` Jakob Koschel
2022-08-17 14:36 ` Julia Lawall
2022-08-17 14:50 ` Jakob Koschel
2022-08-17 15:26 ` Julia Lawall
2022-08-17 19:48 ` [cocci] Working with parameter/expression lists by SmPL Markus Elfring
2022-08-18 12:51 ` Jakob Koschel
2022-08-18 17:42 ` Markus Elfring
2022-08-19 9:12 ` Jakob Koschel
2022-08-19 9:57 ` Julia Lawall
2022-08-19 10:00 ` Jakob Koschel
2022-08-19 17:00 ` Markus Elfring [this message]
2022-08-20 12:57 ` Jakob Koschel
2022-08-21 8:10 ` Markus Elfring
2022-08-21 9:09 ` Julia Lawall
2022-08-21 9:46 ` Markus Elfring
2022-08-21 10:01 ` Julia Lawall
2022-08-21 11:33 ` Markus Elfring
2022-08-18 18:00 ` [cocci] Checking a comment addition Markus Elfring
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=d9e428c2-f4d2-13bb-bf42-447a1f0ffa73@web.de \
--to=markus.elfring@web.de \
--cc=cocci@inria.fr \
--cc=jkl820.git@gmail.com \
--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.