public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/58887] Allow recursion in variadic macros?
Date: Sun, 27 Oct 2013 15:48:00 -0000	[thread overview]
Message-ID: <bug-58887-4-8Ac7zcR6RL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58887-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58887

--- Comment #3 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
We take the view that the preprocessor is deliberately meant to be limited 
and overly complicated features in it would be contrary to the spirit of 
C.  Of course if they are introduced in the standard we need to implement 
them, but otherwise this proposed feature seems inappropriate.


  parent reply	other threads:[~2013-10-27 15:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-58887-4@http.gcc.gnu.org/bugzilla/>
2013-10-26 21:13 ` [Bug preprocessor/58887] Allow recursion in varadic macros? pinskia at gcc dot gnu.org
2013-10-27 13:44 ` mtewoodbury at gmail dot com
2013-10-27 15:48 ` joseph at codesourcery dot com [this message]
2013-10-27 21:52 ` [Bug preprocessor/58887] Allow recursion in variadic macros? mtewoodbury at gmail dot com
2013-10-27 21:56 ` mtewoodbury at gmail dot com
2013-10-28 11:35 ` mtewoodbury at gmail dot com
2013-10-28 13:38 ` joseph at codesourcery dot com
2013-10-28 13:56 ` joseph at codesourcery dot com
2013-10-28 17:48 ` mtewoodbury at gmail dot com
2013-10-28 18:51 ` joseph at codesourcery dot com
2013-10-30 10:04 ` mtewoodbury at gmail dot com
2013-10-30 16:56 ` joseph at codesourcery dot com
2013-10-30 19:00 ` mtewoodbury at gmail dot com

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=bug-58887-4-8Ac7zcR6RL@http.gcc.gnu.org/bugzilla/ \
    --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: 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 read-only IMAP folder(s) and NNTP newsgroup(s).