> > > @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?
> If you tried this and it didn't work, it could be because of parallelism.
> When you use the -j option, each child process has its own address space,
There are the usual concerns to consider around multi-programming.
> and by default they are not combined for the finalize,
Are you looking for an other combination approach?
> 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
Regards,
Markus
_______________________________________________
Cocci mailing list
[email protected]
https://systeme.lip6.fr/mailman/listinfo/cocci
