From: Julia Lawall <julia.lawall@inria.fr>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: cocci@systeme.lip6.fr
Subject: Re: [Cocci] [00/43] cocci: Add support for meta attributes to SmPL
Date: Sun, 2 Aug 2020 17:34:26 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2008021733340.2531@hadrien> (raw)
In-Reply-To: <8f357aa0-7811-a5b8-a061-814899654e88@web.de>
[-- Attachment #1: Type: text/plain, Size: 1287 bytes --]
On Sun, 2 Aug 2020, Markus Elfring wrote:
> >> How do you call the following items in the update step “[PATCH 42/43] tests:
> >> Add test case to match meta attribute”?
> >> https://lore.kernel.org/cocci/25fb4894-65d3-dc57-dbfd-93d3482d8fee@web.de/
> >> https://systeme.lip6.fr/pipermail/cocci/2020-July/008036.html
> >>
> >> attribute name __attr__;
> >> attribute a;
> >
> > attribute a; declares a metavariable that matches attributes.
> >
> > attribute name __attr__; declares that __attr__ is the name of an attribute.
>
> Is this specification also a declaration of a metavariable?
No.
>
>
> > These "name" declarations can be used in the parsing of the C code as a
> > hint that __attr__ should be parsed in a special way.
>
> Will a more helpful explanation be added to the software documentation
> like the SmPL manual?
> https://github.com/coccinelle/coccinelle/blob/e06b9156dfa02a28cf3cbf0913a10513f3d163ab/docs/manual/cocci_syntax.tex#L452
The discussion of attribute name and name in general already seems clear
enough.
>
> Which display do you get for the command “spatch --parse-cocci tests/metaattr.cocci”
> according to the discussed development version of your software?
There is no warning. The code is now on github. You can test it
yourself.
julia
[-- Attachment #2: Type: text/plain, Size: 136 bytes --]
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2020-08-02 15:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e4f3c4e8-03e8-dbc2-5871-0d111b3086a4@web.de>
2020-08-02 7:06 ` [Cocci] [PATCH 00/43] cocci: Add support for meta attributes to SmPL Julia Lawall
[not found] ` <eead5e2a-da8d-83cd-eeb4-f193702b800f@web.de>
2020-08-02 11:48 ` Julia Lawall
[not found] ` <82af6b44-ea09-b86f-81f7-e96e8594a31d@web.de>
2020-08-02 13:13 ` [Cocci] [00/43] " Julia Lawall
[not found] ` <065fee88-5206-5d9b-c83c-4e6a20aefd85@web.de>
2020-08-02 14:34 ` Julia Lawall
[not found] ` <8f357aa0-7811-a5b8-a061-814899654e88@web.de>
2020-08-02 15:34 ` Julia Lawall [this message]
[not found] ` <c1822815-456f-316d-93b5-88beb55a0d69@web.de>
2020-08-02 16:16 ` Julia Lawall
[not found] ` <74a5a472-4431-46e7-bd8b-95886f031c93@web.de>
2020-08-02 17:00 ` Julia Lawall
[not found] ` <3474ebf5-c902-63e9-8244-08a0f3407b72@web.de>
2020-08-03 5:46 ` Julia Lawall
2020-08-03 8:22 ` Jaskaran Singh
[not found] ` <04cb5eb3-bed8-9e8e-255b-fbae06144016@web.de>
2020-08-08 11:35 ` Jaskaran Singh
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=alpine.DEB.2.22.394.2008021733340.2531@hadrien \
--to=julia.lawall@inria.fr \
--cc=Markus.Elfring@web.de \
--cc=cocci@systeme.lip6.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).