From: "Martin v. Loewis" <martin@mira.isdn.cs.tu-berlin.de>
To: alex.buell@tahallah.demon.co.uk
Cc: craig@jcb-sc.com, alex.buell@tahallah.demon.co.uk, egcs@cygnus.com
Subject: Re: i18n of egcs
Date: Fri, 30 Apr 1999 23:15:00 -0000 [thread overview]
Message-ID: <199904282240.AAA00900@mira.isdn.cs.tu-berlin.de> (raw)
Message-ID: <19990430231500.OPUfJHO8E7edHtEEpXc-a4qH6usRDepXVCsOaBtiK4M@z> (raw)
In-Reply-To: <Pine.GSO.4.10.9904281508040.20781-100000@eos30>
> I don't think we should drop the -ansi option for compatibility
> reasons, but rather introduce -iso as an aliased flag. Then
> everyone's happy, yes?
Well, I'd like to speak against a -iso option, and no, I don't request
a -din option :-)
There are many ISO standards out there: ISO C-90 (what is the
number?), ISO 14882 'Programming Languages - C++' 1998, and soon ISO C
99. I believe ISO has standards for Pascal and Fortran as well. There
is already a scheme how enforcing a specific standard can be requested
from the compiler.
If the option is changed, I'd rather like it to be -standard-c,
-standard-c++, or even -x iso-c, -x iso-c++.
Regards,
Martin
next prev parent reply other threads:[~1999-04-30 23:15 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-27 11:43 Philipp Thomas
1999-04-27 13:06 ` Gabriel Dos_Reis
1999-04-27 13:33 ` Philipp Thomas
1999-04-28 0:46 ` Steinar Bang
1999-04-28 5:37 ` Gabriel Dos_Reis
1999-04-30 23:15 ` Gabriel Dos_Reis
1999-04-28 6:05 ` craig
1999-04-28 6:47 ` alex.buell
1999-04-28 6:53 ` craig
1999-04-28 7:17 ` alex.buell
1999-04-28 15:41 ` Martin v. Loewis [this message]
1999-04-28 15:46 ` Zack Weinberg
1999-04-28 23:16 ` Martin v. Loewis
1999-04-28 23:25 ` Gabriel Dos_Reis
1999-04-28 23:55 ` Joe Buck
1999-04-29 8:00 ` craig
1999-04-29 8:17 ` Joern Rennecke
1999-04-30 12:40 ` Philipp Thomas
1999-04-30 23:15 ` Philipp Thomas
1999-05-05 1:43 ` Steinar Bang
1999-05-31 21:36 ` Steinar Bang
1999-04-30 23:15 ` Joern Rennecke
1999-04-30 23:15 ` craig
1999-04-30 23:15 ` Joe Buck
1999-04-30 23:15 ` Gabriel Dos_Reis
1999-04-29 13:19 ` Richard Henderson
1999-04-30 23:15 ` Richard Henderson
1999-04-30 23:15 ` Martin v. Loewis
1999-04-30 23:15 ` Zack Weinberg
1999-04-30 23:15 ` Martin v. Loewis
1999-04-30 23:15 ` alex.buell
1999-04-30 23:15 ` craig
1999-04-30 23:15 ` alex.buell
1999-04-28 6:54 ` Gabriel Dos_Reis
1999-04-30 23:15 ` Gabriel Dos_Reis
1999-04-30 23:15 ` craig
1999-04-30 23:15 ` Steinar Bang
1999-04-30 23:15 ` Philipp Thomas
1999-04-27 22:24 ` Jeffrey A Law
1999-04-30 23:15 ` Jeffrey A Law
1999-04-30 23:15 ` Gabriel Dos_Reis
1999-04-30 0:27 ` Jeffrey A Law
1999-04-30 2:22 ` Andreas Schwab
1999-04-30 23:15 ` Andreas Schwab
1999-04-30 15:06 ` Philipp Thomas
1999-04-30 23:15 ` Philipp Thomas
1999-05-04 0:33 ` Jeffrey A Law
1999-05-31 21:36 ` Jeffrey A Law
1999-07-09 2:56 ` Jeffrey A Law
1999-07-31 23:33 ` Jeffrey A Law
1999-04-30 23:15 ` Jeffrey A Law
1999-04-30 23:15 ` Philipp Thomas
-- strict thread matches above, loose matches on Subject: below --
1999-04-28 9:17 Mike Stump
1999-04-30 23:15 ` Mike Stump
1999-04-05 17:27 Mike Stump
1999-04-30 23:15 ` Mike Stump
1999-03-25 3:43 Philipp Thomas
1999-03-31 23:46 ` Philipp Thomas
1999-04-03 21:29 ` Jeffrey A Law
1999-04-04 18:00 ` Philipp Thomas
1999-04-30 23:15 ` Philipp Thomas
1999-04-30 23:15 ` Jeffrey A Law
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=199904282240.AAA00900@mira.isdn.cs.tu-berlin.de \
--to=martin@mira.isdn.cs.tu-berlin.de \
--cc=alex.buell@tahallah.demon.co.uk \
--cc=craig@jcb-sc.com \
--cc=egcs@cygnus.com \
/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).