From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Moving a function body to an other source code place with SmPL
Date: Mon, 14 May 2018 17:12:52 +0200 [thread overview]
Message-ID: <03b3476d-083f-216b-bfef-03b0b1b25d21@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.20.1805141632540.17398@hadrien>
>> It would be occasionally nice if an implementation of a function could be
>> completely stored into a metavariable.
>> Is a statement list variable appropriate for this use case?
>
> Yes.
Thanks for your acknowledgement that it should usually work.
I have noticed a moment ago that a blank line is not marked by the SmPL
asterisk operator (for a small source code example) so far.
Can such whitespace characters be also preserved there anyhow?
>> Can these data be moved to an other function (or macro definition)?
>
> Yes. A statement list variable can be added anywhere a list of statements
> is allowed, ie not necessarily as the complete body of a block.
How will the software behaviour evolve if I stumble on the message
?Fatal error: exception Coccinelle_modules.Common.Timeout? after passing
the parameter ?--timeout 123? for a change attempt with a C++ source file?
(Am I too impatient here?)
Regards,
Markus
next prev parent reply other threads:[~2018-05-14 15:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 13:10 [Cocci] Moving a function body to an other source code place with SmPL SF Markus Elfring
2018-05-14 14:35 ` Julia Lawall
2018-05-14 15:12 ` SF Markus Elfring [this message]
2018-05-14 15:15 ` Julia Lawall
2018-05-14 15:26 ` SF Markus Elfring
2018-05-14 15:33 ` Julia Lawall
[not found] ` <9507e4af-3a80-f691-e75a-e4ddec1548c8@users.sourceforge.net>
2018-05-14 19:41 ` [Cocci] Checking the support for source code transformations with special characters Julia Lawall
[not found] ` <ca7b8507-86e7-dab4-2394-07df379034e7@users.sourceforge.net>
2018-05-15 7:13 ` [Cocci] Checking data processing for statement lists 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=03b3476d-083f-216b-bfef-03b0b1b25d21@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=cocci@systeme.lip6.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.