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 parsing for a nested SmPL disjunction
Date: Fri, 26 Jun 2020 20:30:36 +0200 [thread overview]
Message-ID: <c5ef6ff2-2ea5-ba9c-82be-305ecc9ab877@web.de> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2006262019430.10382@hadrien>
>> <+... when any
>> (t2 y = <+...
>> ( sizeof(*(resource))
>> |
>> * *(resource)
>> ) ...+>
>
> You are missing a ; here.
I assumed that I may omit the semicolon in such a SmPL code.
Can the specification of a SmPL nest construct ever be sufficient here?
Regards,
Markus
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2020-06-26 18:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 17:35 [Cocci] Checking the parsing for a nested SmPL disjunction Markus Elfring
2020-06-26 18:20 ` Julia Lawall
2020-06-26 18:30 ` Markus Elfring [this message]
2020-06-26 18:35 ` Julia Lawall
2020-06-26 18:38 ` Markus Elfring
2020-06-26 18:42 ` Julia Lawall
2020-06-26 18:48 ` Markus Elfring
2020-06-26 18:49 ` 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=c5ef6ff2-2ea5-ba9c-82be-305ecc9ab877@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).