Re: [Cocci] Checking the parsing for a nested SmPL disjunction

On Fri, 26 Jun 2020, Markus Elfring wrote: > 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? > >>> > >>> No. <+... ...+> matches a subtree of an AST. For a variable > >>> initialization, there is

Re: [Cocci] Checking the parsing for a nested SmPL disjunction

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? >>> >>> No. <+... ...+> matches a subtree of an AST. For a variable >>> initialization, there is no subtree of the AST that includes both the >>> right si

Re: [Cocci] Checking the parsing for a nested SmPL disjunction

On Fri, 26 Jun 2020, Markus Elfring wrote: > >> 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? > > > > No. <+... ...+> matches a subtree of an AST. For a variable > > initialization, there is no subtree

Re: [Cocci] Checking the parsing for a nested SmPL disjunction

>> 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? > > No. <+... ...+> matches a subtree of an AST. For a variable > initialization, there is no subtree of the AST that includes both the > right side of an = a

Re: [Cocci] Checking the parsing for a nested SmPL disjunction

On Fri, 26 Jun 2020, Markus Elfring wrote: > >> <+... 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

Re: [Cocci] Checking the parsing for a nested SmPL disjunction

>> <+... 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 __

Re: [Cocci] Checking the parsing for a nested SmPL disjunction

.+> > > > elfring@Sonne:~/Projekte/Coccinelle/janitor> spatch --parse-cocci > show_problematic_disjunction-20200626.cocci > … > minus: parse error: > File "show_problematic_disjunction-20200626.cocci", line 14, column 0, > charpos = 196 > arou

[Cocci] Checking the parsing for a nested SmPL disjunction

2 y = <+... ( sizeof(*(resource)) | * *(resource) ) ...+> | *action(..., resource, ...) ) ...+> elfring@Sonne:~/Projekte/Coccinelle/janitor> spatch --parse-cocci show_problematic_disjunction-20200626.cocci … minus: parse error: File "show_problematic_disjunction-2020

Re: [Cocci] Checking the display of SmPL isomorphism results (with pointers)

On Fri, 26 Jun 2020, Markus Elfring wrote: > Hello, > > I have tried another tiny script variant out for the semantic patch language > (according to the software combination “Coccinelle 1.0.8-00131-g675b9670”). > > @display@ > expression* x; > statement is, es; > @@ > *if (!x) > is > else >

[Cocci] Checking the display of SmPL isomorphism results (with pointers)

Hello, I have tried another tiny script variant out for the semantic patch language (according to the software combination “Coccinelle 1.0.8-00131-g675b9670”). @display@ expression* x; statement is, es; @@ *if (!x) is else es elfring@Sonne:~/Projekte/Coccinelle/janitor> spatch --parse-