On Mon, 8 Jun 2020, Markus Elfring wrote:
> > > > @r depends on !patch@
> > > // It doesn't work. Is it normal?
> > > //position p: script:python() { matches.extend(p); relevant(p) };
> >
> > "Doesn't work" means you get a parse error? The parser of the code inside
> > the {} is pretty fragile.
>
> I find such information also interesting.
>
>
> > Perhaps this could be improved somewhat, but it is limited by the fact
> > that Coccinelle doesn't know how to parse python properly.
>
> Should the software be able to determine just the amount of script code
> between the curly brackets?
What if there is a string or comment inside the script code, ant it
contains only a }?
Anyway the problem is that the Coccinelle lexer doesn't know that it is
looking at script code, or eg {} around a selection of types.
> > which is not run in parallel.
>
> Will a SmPL child process get a chance to perform customised finalisation
> code?
> Would you like to continue the clarification according to a topic
> like “Complete support for fork-join work flows”?
> https://github.com/coccinelle/coccinelle/issues/50
Those issues are addressed by the use of the merge functionality.
julia_______________________________________________
Cocci mailing list
[email protected]
https://systeme.lip6.fr/mailman/listinfo/cocci
