public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: Neil Booth <neil@daikokuya.demon.co.uk>
Cc: <pfk@RZ.uni-jena.de>, <gcc@gcc.gnu.org>
Subject: Re: Proposal
Date: Tue, 18 Sep 2001 02:30:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.33.0109181019360.11043-100000@kern.srcf.societies.cam.ac.uk> (raw)
In-Reply-To: <20010917235928.A11347@daikokuya.demon.co.uk>

On Mon, 17 Sep 2001, Neil Booth wrote:

> This is possibly a good idea.  It's a trivial patch to implement it
> (c-lex.c I think, unless Zack finally applies his number patch); a
> comment even exists in the code mentioning that it might be a future
> extension.

However, we shouldn't add it to GCC yet.  Since this feature would not
actually allow you to do something that couldn't reasonably be done before
or make it substantially simpler to do so, and since it might be
appropriate for a future version of the standard, a more appropriate
procedure would be:

* Create a patch for GCC, and the exact proposed changes to the text of
C99.  (The patch is desirable here to show implementation experience.)

* Iterate with comp.std.c about the exact semantics and the desirability
of the feature.

* In due course, when the time comes for adding new language features to
the C standard (so not for a few years yet), propose it via your National
Body for inclusion in C0X.

* Once it is in a C0X draft, then addition to GCC as part of tracking C0X
drafts (with a strong warning that any features added as part of C0X
tracking may be removed or changed without notice to keep up with changing
drafts) would be appropriate.

History shows that extensions tend to cause problems, so we should be wary
of adding it until it is in a C0X draft.

-- 
Joseph S. Myers
jsm28@cam.ac.uk

  reply	other threads:[~2001-09-18  2:30 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-15 11:45 Proposal Frank Klemm
2001-09-15 12:15 ` Proposal Gerald Pfeifer
2001-09-17 16:00 ` Proposal Neil Booth
2001-09-18  2:30   ` Joseph S. Myers [this message]
2001-09-18 10:21     ` Proposal Zack Weinberg
2001-09-18 11:14       ` Proposal Joseph S. Myers
2001-09-18 22:20         ` Proposal Zack Weinberg
2001-09-19  1:14           ` Proposal Joseph S. Myers
2001-09-18 12:23       ` Proposal Frank Klemm
2001-09-18 22:37         ` Proposal Zack Weinberg
2001-09-19  0:02           ` Proposal Neil Booth
2001-09-19  2:23             ` Proposal Tim Hollebeek
2001-09-19  2:41               ` Proposal Richard Earnshaw
2001-09-19 13:38         ` Proposal Joe Buck
2001-09-18 15:35       ` Proposal Robert Lipe
2001-09-18 16:59         ` Proposal Russ Allbery
2001-09-20 11:17           ` Proposal Kai Henningsen
2001-09-20 12:34             ` Proposal Russ Allbery
2001-09-18  9:48   ` Proposal Frank Klemm
2001-09-18 11:06     ` Proposal Neil Booth
2001-09-18 11:37     ` Proposal Kevin Handy
2001-09-18 15:48       ` Proposal Neil Booth
2001-09-18 15:55         ` Proposal Toon Moene
2001-09-27  5:39     ` Proposal Alexandre Oliva
2001-09-27  7:09       ` Proposal Frank Klemm
2001-09-27 16:22         ` Proposal Zack Weinberg
2001-09-29 15:45           ` Proposal Frank Klemm
2001-09-30  9:35             ` Proposal Zack Weinberg
2001-09-27 16:36         ` Proposal Neil Booth
2001-09-29 15:45           ` Proposal Frank Klemm
2001-09-29 17:22             ` Proposal Daniel Jacobowitz
2001-09-29 18:32               ` OT: Proposal Michael Matz
2001-10-03  3:52         ` Proposal Fergus Henderson
2001-09-17  8:55 Proposal Thomas R. Truscott
2001-09-18  9:32 Proposal dewar
2001-09-18 12:30 Proposal dewar
2001-09-18 23:01 ` Proposal Zack Weinberg
2001-09-19  0:06 Proposal dewar
2001-09-19  2:34 Proposal dewar
2001-09-19  2:44 Proposal dewar
2012-09-03 15:16 Proposal Afeez Basit
2012-09-03 18:35 Proposal Afeez Basit
2013-06-26 17:41 Proposal Barrister David Lopez Esq
2013-06-26 18:15 ` Proposal Paolo Carlini
2013-06-26 18:40   ` Proposal Daniel Santos
2013-06-26 17:47 Proposal Barrister David Lopez Esq

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=Pine.LNX.4.33.0109181019360.11043-100000@kern.srcf.societies.cam.ac.uk \
    --to=jsm28@cam.ac.uk \
    --cc=gcc@gcc.gnu.org \
    --cc=neil@daikokuya.demon.co.uk \
    --cc=pfk@RZ.uni-jena.de \
    /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).