From: Jerome Glisse <jglisse@redhat.com>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: cocci@systeme.lip6.fr
Subject: Re: [Cocci] Changing function pointer typedef
Date: Fri, 8 Mar 2019 14:32:14 -0500 [thread overview]
Message-ID: <20190308193212.GE5618@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1903082022351.2518@hadrien>
On Fri, Mar 08, 2019 at 08:23:48PM +0100, Julia Lawall wrote:
> > test.spatch
> > @@
> > type T1, T2;
> > @@
> > -typedef int (*filler_t)(T1,
> > +typedef int (*filler_t)(T1, struct address_space *,
>
> If this is the whole rule, it is clear that it will not work. A semantic
> patch rule has to e a complete syntactic unit. So something with an open
> parenthesis and no corresponding close parenthesis will not be accepted.
Yeah and adding "T2);" to the rule does not help either it error to
error in collection of - tokens: line 4 less than line 6
Any variation really do error in some way or another.
Cheers,
Jérôme
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2019-03-08 19:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-08 18:19 [Cocci] Changing function pointer typedef Jerome Glisse
2019-03-08 18:57 ` Julia Lawall
2019-03-08 19:11 ` Jerome Glisse
2019-03-08 19:23 ` Julia Lawall
2019-03-08 19:32 ` Jerome Glisse [this message]
2019-03-17 18:43 ` 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=20190308193212.GE5618@redhat.com \
--to=jglisse@redhat.com \
--cc=cocci@systeme.lip6.fr \
--cc=julia.lawall@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).