From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: cocci@inria.fr
Subject: Re: [cocci] Completing support for fork-join work flows
Date: Tue, 4 Apr 2023 10:33:54 +0200 [thread overview]
Message-ID: <b5a22dcf-0bd2-c268-00d0-caf28347c704@web.de> (raw)
In-Reply-To: <54b3a612-6f31-d3be-507c-d17ff1446574@inria.fr>
>>>> https://gitlab.inria.fr/coccinelle/coccinelle/-/blob/e910982fe0830c9dccc9a8d3a4639484947a7559/docs/manual/cocci_syntax.tex#L658
>>>>
>>>> Would you ever like to distinguish the scope for such actions?
>>>
>>> Why are you referring to the section about metavariables?
>>
>> The description starts for the elements “initialize“ and “finalize“ of the
>> semantic patch language here, doesn't it?
>
> And?
I suggest to care occasionally more for the distinction of items like the following.
1. SmPL main program
2. spatch child (or background) processes
3. processing threads
4. tasks
5. effect handlers
6. Multicore OCaml
Regards,
Markus
prev parent reply other threads:[~2023-04-04 8:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 16:43 [cocci] Completing support for fork-join work flows Markus Elfring
[not found] ` <b59a8472-95df-b592-78d6-9543aef463ac@inria.fr>
2023-04-04 5:37 ` Markus Elfring
2023-04-04 6:29 ` Julia Lawall
2023-04-04 7:01 ` Markus Elfring
[not found] ` <54b3a612-6f31-d3be-507c-d17ff1446574@inria.fr>
2023-04-04 8:33 ` Markus Elfring [this message]
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=b5a22dcf-0bd2-c268-00d0-caf28347c704@web.de \
--to=markus.elfring@web.de \
--cc=cocci@inria.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 read-only IMAP folder(s) and NNTP newsgroup(s).