From: wsa@the-dreams.de (Wolfram Sang)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Removing pointer declaration
Date: Sat, 8 Jun 2013 21:02:17 +0200 [thread overview]
Message-ID: <20130608190217.GB2997@katana> (raw)
In-Reply-To: <alpine.DEB.2.02.1306082052560.1968@localhost6.localdomain6>
Hi Julia,
On Sat, Jun 08, 2013 at 08:53:19PM +0200, Julia Lawall wrote:
> On Sat, 8 Jun 2013, Wolfram Sang wrote:
>
> > Hi,
> >
> > This spatch:
> >
> > @@
> > int *p;
>
> This should be "identifier p".
I noticed meanwhile. Is it because the type cannot be checked because
the pointer has not been declared yet? And, in general, can I get some
more info about what went wrong besides "parse error" somehow? --debug
didn't help.
Thanks!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <https://systeme.lip6.fr/pipermail/cocci/attachments/20130608/837973f5/attachment.asc>
next prev parent reply other threads:[~2013-06-08 19:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-08 17:28 [Cocci] Removing pointer declaration Wolfram Sang
2013-06-08 18:53 ` Julia Lawall
2013-06-08 19:02 ` Wolfram Sang [this message]
2013-06-08 19:06 ` Julia Lawall
2013-06-10 7:34 ` Michael Stefaniuc
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=20130608190217.GB2997@katana \
--to=wsa@the-dreams.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