From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: cocci@systeme.lip6.fr
Subject: Re: [Cocci] transforming arguments to statement macros?
Date: Sun, 5 Jan 2020 14:54:41 +0100 [thread overview]
Message-ID: <58ae2bb2-45f1-49b0-d271-515434d048eb@web.de> (raw)
In-Reply-To: <alpine.DEB.2.21.2001051100550.2579@hadrien>
> It uses a regular expression to detect that a statement starts with the
> word ASSERT, and matches the next statement as well, and then in another
> rule adds a ; before the subsequent statement.
Can related improvements for the supported programming interfaces help
to split the available information into more useful pieces?
> If you add the ; after the ASSERT statement it comes out after ASSERT,
> not after the commented argument list. But with this semantic patch,
> the ; comes out on a line of its own, and would have to be moved up manually.
Can this software behaviour be avoided if the semicolon would be inserted
by using the function “make_stmt” of Coccinelle's library in
a SmPL script rule?
Regards,
Markus
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2020-01-05 13:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-02 22:03 [Cocci] transforming arguments to statement macros? David Young
2020-01-03 6:32 ` Julia Lawall
2020-01-03 16:03 ` David Young
2020-01-05 9:47 ` Markus Elfring
2020-01-05 10:05 ` Julia Lawall
2020-01-05 11:32 ` Markus Elfring
2020-01-05 13:54 ` Markus Elfring [this message]
2020-01-06 12:07 ` [Cocci] Adding semicolons after macro calls Markus Elfring
2020-01-06 12:20 ` Julia Lawall
2020-01-06 12:48 ` [Cocci] Improving support for data processing around " Markus Elfring
2020-01-08 22:05 ` [Cocci] transforming arguments to statement macros? Julia Lawall
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=58ae2bb2-45f1-49b0-d271-515434d048eb@web.de \
--to=markus.elfring@web.de \
--cc=cocci@systeme.lip6.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).