From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Handling of compound literals?
Date: Sun, 06 Apr 2014 08:21:57 +0200 [thread overview]
Message-ID: <5340F285.1000701@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.02.1404051717280.2029@localhost6.localdomain6>
>> That's actually not a cast but a compound literal
>> http://gcc.gnu.org/onlinedocs/gcc/Compound-Literals.html
>
> [...] I'm still not sure to see how to solve the ambiguity problem.
How do you think about to ask any other parser and compiler developers?
Regards,
Markus
next prev parent reply other threads:[~2014-04-06 6:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 8:30 [Cocci] spatch issue with C struct initialization Marcel Apfelbaum
2014-04-03 10:16 ` Julia Lawall
2014-04-03 13:31 ` Marcel Apfelbaum
2014-04-03 14:19 ` Julia Lawall
2014-04-03 14:29 ` Marcel Apfelbaum
2014-04-03 14:33 ` Julia Lawall
2014-04-03 14:38 ` Marcel Apfelbaum
2014-04-04 11:21 ` Julia Lawall
2014-04-05 15:01 ` Michael Stefaniuc
2014-04-05 15:17 ` Julia Lawall
2014-04-06 6:21 ` SF Markus Elfring [this message]
2014-04-06 7:45 ` Marcel Apfelbaum
2014-04-06 10:57 ` Julia Lawall
2014-04-20 20:29 ` Julia Lawall
2014-04-22 8:21 ` Marcel Apfelbaum
2014-04-03 14:22 ` 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=5340F285.1000701@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--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