From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>, cocci@inria.fr
Subject: Re: [cocci] Clarification for input data of scripted SmPL constraints
Date: Fri, 26 Jan 2024 14:24:59 +0100 [thread overview]
Message-ID: <c9453e9d-b153-4036-ad5a-488159b2273c@web.de> (raw)
In-Reply-To: <51875417-549f-3fc-f661-15d87fa41140@inria.fr>
>> But how does the software situation look like if you would like to use contents
>> from multiple metavariables (which were hopefully matched in combination)
>> for advanced condition checks?
>
> To a limited extent they can be listed in the ().
* Would you like to point any script examples out?
* How do you think about to improve the corresponding software documentation?
> If there ... in the rule, it is often forbidded to use this feature,
Would you like to extend explanations for such a hint?
> and you have to use a separate script rule.
Will development concerns be clarified further?
Regards,
Markus
prev parent reply other threads:[~2024-01-26 13:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 12:50 [cocci] Clarification for input data of scripted SmPL constraints Markus Elfring
2024-01-26 12:52 ` Julia Lawall
2024-01-26 13:24 ` 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=c9453e9d-b153-4036-ad5a-488159b2273c@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).