From: Julia Lawall <julia.lawall@lip6.fr>
To: Timur Tabi <timur@kernel.org>
Cc: cocci <cocci@systeme.lip6.fr>
Subject: Re: [Cocci] Blank space in front of function definition name confuses spatch
Date: Wed, 23 Jan 2019 07:19:10 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.21.1901230718350.2762@hadrien> (raw)
In-Reply-To: <CAOZdJXUg+1M-ii-tEtYdjDyXuEUYbmHYSf-EqfzFh+OtuWLP7A@mail.gmail.com>
On Tue, 22 Jan 2019, Timur Tabi wrote:
> If I have a blank space in front of the return parameter and function
> name, spatch gets confused and rejects the file. I've attached a
> test.c and my nv_printf.cocci. If I remove the blank space before
> "NV_STATUS" and "mycrazyfunc", everything works. But with the blank
> space, it causes this error:
The problem only comes when te return type is a typedef. I will see if it
is possible to fix it.
julia
>
> ERROR-RECOV: found sync '}' at line 14
> parsing pass2: try again
> ERROR-RECOV: found sync '}' at line 14
> parsing pass3: try again
> ERROR-RECOV: found sync '}' at line 14
> parse error
> = File "/home/ttabi/test.c", line 1, column 1, charpos = 1
> around = 'NV_STATUS',
> whole content = NV_STATUS
> badcount: 13
> BAD:!!!!! NV_STATUS
> bad: mycrazyfunc
> bad: (
>
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2019-01-23 6:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 22:30 [Cocci] Blank space in front of function definition name confuses spatch Timur Tabi
2019-01-23 6:19 ` Julia Lawall [this message]
2019-01-24 20:19 ` Julia Lawall
2019-01-28 21:50 ` Timur Tabi
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.21.1901230718350.2762@hadrien \
--to=julia.lawall@lip6.fr \
--cc=cocci@systeme.lip6.fr \
--cc=timur@kernel.org \
/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).