cocci.inria.fr archive mirror
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: cocci@systeme.lip6.fr, Denis Efremov <efremov@ispras.ru>
Subject: Re: [Cocci] Python interface
Date: Mon, 8 Jun 2020 09:21:13 +0200	[thread overview]
Message-ID: <0a07fbfd-df53-2386-dd02-4d179d963e81@web.de> (raw)

> > > @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
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci

             reply	other threads:[~2020-06-08  7:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-08  7:21 Markus Elfring [this message]
2020-06-08 10:31 ` [Cocci] Python interface Julia Lawall
2020-06-08 11:09   ` Markus Elfring
  -- strict thread matches above, loose matches on Subject: below --
2020-06-08 12:22 Markus Elfring
2020-06-08 12:09 Markus Elfring
2020-06-08 12:09 Markus Elfring
2020-06-07 15:05 Denis Efremov
2020-06-07 20:12 ` Julia Lawall
2020-06-07 21:20   ` Denis Efremov
2020-06-07 21:23     ` Julia Lawall
2020-06-08 10:27 ` Julia Lawall
2020-06-08 11:00   ` Denis Efremov
2020-06-08 11:21     ` 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=0a07fbfd-df53-2386-dd02-4d179d963e81@web.de \
    --to=markus.elfring@web.de \
    --cc=cocci@systeme.lip6.fr \
    --cc=efremov@ispras.ru \
    --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).