public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Frank Klemm <pfk@fuchs.offl.uni-jena.de>
To: Neil Booth <neil@daikokuya.demon.co.uk>, gcc@gcc.gnu.org
Subject: Re: Proposal
Date: Tue, 18 Sep 2001 09:48:00 -0000	[thread overview]
Message-ID: <20010918021527.A14623@fuchs.offl.uni-jena.de> (raw)
In-Reply-To: <20010917235928.A11347@daikokuya.demon.co.uk>

On Mon, Sep 17, 2001 at 11:59:28PM +0100, Neil Booth wrote:
> 
> > It is not allowed to compose numbers with '_' inside of macros.
> > 
> >   #define MILLION	_MERGE5 ( 1, _, 000, _, 000 )
> > 
> > This allows easily to write a filter to generate C89 or C99 files.
> 
> I don't understand quite what you're saying here.  If you're saying
> dissallow concatenation with ## then I would strenuously object, since
> 
> 1) disallowing it seems gratuitous,
> 2) it's specifically allowed by the standard, and
> 3) it would be introducing yet more special cases to the preprocessor,
>    which already has too many of those for my liking.
> 
For instance you have a program which uses _ in numbers. 
But not all compilers will will support this in the beginning.

It should be possible to write a program which removes these _ inside of
numbers to allow to compile such source files with other compilers.

Without this rule it is impossible to write such a program without
preprocessing the source file. And preprocessed files are no source files
anymore.

To prevent this it is forbidden to use this feature in conjunction with
token concatenation. At least as long as this is not an ISO standard.

For instance try to convert 

   #define MILLION	MY_MERGE_5 ( 1, _, 000, _, 000 )

to the old representation. Note that MY_MERGE_5 is a self defined macro.

-- 
Frank Klemm

  parent reply	other threads:[~2001-09-18  9:48 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   ` Proposal Joseph S. Myers
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   ` Frank Klemm [this message]
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=20010918021527.A14623@fuchs.offl.uni-jena.de \
    --to=pfk@fuchs.offl.uni-jena.de \
    --cc=gcc@gcc.gnu.org \
    --cc=neil@daikokuya.demon.co.uk \
    /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).