From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: Coccinelle <cocci@systeme.lip6.fr>
Subject: Re: [Cocci] Reducing source code around return statements with SmPL?
Date: Tue, 24 Sep 2019 18:00:40 +0200 [thread overview]
Message-ID: <8bb5e576-050f-958d-1eab-0f85b6c10f1f@web.de> (raw)
In-Reply-To: <alpine.DEB.2.21.1909241750490.2281@hadrien>
>> * Can a SmPL specification like “v << check2.rc;” look also reasonable here
>> (despite of the error message which is reported so far)?
>
> Many things may look reasonable.
This is generally fine.
> I tell you how Coccinelle is designed,
Thanks for such feedback.
> you can ignore the information if you like.
I am trying once more to achieve another bit of collateral evolution
in this software area.
Will it become helpful to use content also from inherited metavariables directly
(instead of referring only to the base item)?
Regards,
Markus
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2019-09-24 16:01 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-23 8:50 [Cocci] Reducing source code around return statements with SmPL? Markus Elfring
2019-09-23 8:59 ` Julia Lawall
2019-09-23 11:17 ` Markus Elfring
2019-09-24 15:27 ` Markus Elfring
2019-09-24 15:30 ` Julia Lawall
2019-09-24 15:40 ` Markus Elfring
[not found] ` <alpine.DEB.2.21.1909241750490.2281@hadrien>
2019-09-24 16:00 ` Markus Elfring [this message]
[not found] ` <alpine.DEB.2.21.1909241804490.2281@hadrien>
2019-09-24 16:14 ` Markus Elfring
2019-09-24 19:24 ` Markus Elfring
2019-09-24 20:16 ` Julia Lawall
2019-09-24 20:35 ` Markus Elfring
2019-09-24 20:49 ` Julia Lawall
2019-09-24 20:55 ` Markus Elfring
2019-09-25 6:13 ` Markus Elfring
2019-09-25 6:22 ` Julia Lawall
2019-09-25 6:28 ` Markus Elfring
[not found] ` <alpine.DEB.2.21.1909250837140.2482@hadrien>
2019-09-25 6:40 ` Markus Elfring
[not found] ` <alpine.DEB.2.21.1909250854190.2482@hadrien>
2019-09-25 7:00 ` Markus Elfring
[not found] ` <alpine.DEB.2.21.1909251138120.2654@hadrien>
2019-09-25 11:00 ` Markus Elfring
2019-09-24 18:20 ` Markus Elfring
2019-09-24 20:21 ` Julia Lawall
2019-09-24 20:48 ` Markus Elfring
2019-09-24 20:52 ` Julia Lawall
2019-09-24 21:00 ` Markus Elfring
2019-09-24 21:03 ` Julia Lawall
2019-09-25 6:04 ` Markus Elfring
2019-09-25 8:22 ` Markus Elfring
2019-09-25 8:22 ` Markus Elfring
2019-09-24 18:33 ` Markus Elfring
2019-09-25 11:33 ` [Cocci] [PATCH] Coccinelle: Add a SmPL script for the reconsideration of specific combinations of assignment and return statements Markus Elfring
2019-10-01 14:30 ` [Cocci] [PATCH v2] " 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=8bb5e576-050f-958d-1eab-0f85b6c10f1f@web.de \
--to=markus.elfring@web.de \
--cc=cocci@systeme.lip6.fr \
--cc=julia.lawall@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 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).