From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: Coccinelle <cocci@systeme.lip6.fr>
Subject: Re: [Cocci] Checking the influence of an omitted semicolon on a code adjustment
Date: Sat, 28 Nov 2020 21:04:14 +0100 [thread overview]
Message-ID: <8d2bfa68-c8e0-9c5a-b2f5-057e534f5976@web.de> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2011282048540.2725@hadrien>
>>> You can't have an expression directly following a statement.
>>> Only statements follow other statements.
>>
>> This information is reasonable.
>>
>> Does the Coccinelle software insist on the specification of another semicolon
>> in the SmPL script for the identification of an adjustable statement?
>
> Yes
I imagine that another view can become applicable here.
* It is possible to move a function call with a known property into a parameter
of a subsequent function/macro call.
* I care more for the implementation detail that a following function/macro
call exists and less that this source code needs to be an complete statement
(together with the usual semicolon at the end).
I stumble on further software challenges if I would like to make the simple
transformation approach a bit more variable on the number of surrounding parameters.
Regards,
Markus
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2020-11-28 20:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-28 17:21 [Cocci] Checking the influence of an omitted semicolon on a code adjustment Markus Elfring
2020-11-28 17:45 ` Julia Lawall
2020-11-28 18:56 ` Markus Elfring
2020-11-28 19:00 ` Julia Lawall
2020-11-28 19:11 ` Markus Elfring
2020-11-28 19:49 ` Julia Lawall
2020-11-28 20:04 ` Markus Elfring [this message]
[not found] ` <0148bab2-6148-e403-985d-df2e7cade490@web.de>
2020-11-29 11:54 ` [Cocci] Adjusting some calls according to pass-through functions Julia Lawall
[not found] ` <3b134eb3-7ccf-454c-3266-64cfaec5a307@web.de>
2020-11-29 12:25 ` Julia Lawall
[not found] ` <978f08c3-21ed-d434-d2ef-163335ae990e@web.de>
2020-11-29 12:52 ` Julia Lawall
[not found] ` <1dc8f835-11b1-0ec0-8ba4-45cffdf13465@web.de>
2020-11-29 13:47 ` Julia Lawall
[not found] ` <cb266001-ed38-da76-389c-5a7bf7f59e9e@web.de>
2020-11-29 13:43 ` Julia Lawall
[not found] ` <79d4245d-6f34-7b8d-d632-99afcc1d228a@web.de>
2020-11-29 14:44 ` Julia Lawall
[not found] ` <beeb673b-65b5-fdef-f300-c86a4bd0abc7@web.de>
2020-11-29 15:18 ` Julia Lawall
[not found] ` <cf0e2d68-d76b-5892-b97e-36a270732028@web.de>
2020-11-29 15:52 ` Julia Lawall
[not found] ` <b548f18b-2fa7-1fcf-5bbb-3011d8a270e5@web.de>
2020-11-29 16:24 ` 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=8d2bfa68-c8e0-9c5a-b2f5-057e534f5976@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).