public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "brian at dessent dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/38456] Suggestion: slight improvement of scoping rules Date: Tue, 09 Dec 2008 18:54:00 -0000 [thread overview] Message-ID: <20081209185312.8408.qmail@sourceware.org> (raw) In-Reply-To: <bug-38456-17050@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from brian at dessent dot net 2008-12-09 18:53 ------- Subject: Re: New: Suggestion: slight improvement of scoping rules I seriously don't think you will ever convince anyone to change a facet of gcc which is currently following the standard to something that is non-standard. Besides, you can solve the unique name problem like this: #define UNIQUIFY2(a,b) a##b #define UNIQUIFY1(a,b) UNIQUIFY2(a,b) #define UNIQUIFY(x) UNIQUIFY1(x_,__COUNTER__) #define macro(a) \ ({ \ __typeof(a) UNIQUIFY(a) = (a); \ /* ... some code ... */ \ }) __COUNTER__ was new in 4.3. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38456
next prev parent reply other threads:[~2008-12-09 18:54 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-12-09 18:21 [Bug c/38456] New: " lc235951 at students dot mimuw dot edu dot pl 2008-12-09 18:54 ` brian at dessent dot net [this message] 2008-12-09 19:01 ` [Bug c/38456] " steven at gcc dot gnu dot org 2008-12-09 19:11 ` lc235951 at students dot mimuw dot edu dot pl
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=20081209185312.8408.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).