From: craig@jcb-sc.com
To: alex.buell@tahallah.demon.co.uk
Cc: craig@jcb-sc.com
Subject: Re: i18n of egcs
Date: Fri, 30 Apr 1999 23:15:00 -0000 [thread overview]
Message-ID: <19990428135134.3178.qmail@deer> (raw)
Message-ID: <19990430231500.S8RRfTEvo9V8GjAcb9pydKDz5dhWLcmPvzkrqkJxrFw@z> (raw)
In-Reply-To: <Pine.GSO.4.10.9904281439090.20755-100000@eos30>
>On 28 Apr 1999 craig@jcb-sc.com wrote:
>
>> (It is one thing for a *speaker* to choose the "most appropriate" term
>> or phrase. It is quite another for a *listener* to insist on only
>> that one most appropriate term, rejecting any other. In this case,
>> plenty of people already acquainted with the ANSI C standard as such
>> should not be forced to learn to say "ISO C" all the time. *We* (egcs
>> developers) force *ourselves* to say that, because we're essentially
>> in the role of "public speakers" here. That doesn't mean we should
>> force *everyone* to use "ISO C", even on command-line options.)
>
>May I add my 0.02 euros here. I, as an European, would much prefer to see
>the -iso option included - maybe aliased to -ansi, I understand ISO and
>ANSI are one and the same, are they not? The rest of the world *is* bigger
>than America even if their military forces *are* bigger. 8)
That wasn't the issue. I was responding to the issue of whether,
in introducing `-iso', the `-ansi' option should be *dropped*.
Just because ISO C == ANSI C does not mean people should be forbidden
from asking for ANSI C compliance, just as they're not forced to
invoke `gisoc' instead of `gcc' to compile their C programs.
tq vm, (burley)
P.S. At current rates, by about mid next week, America's military
forces probably won't be bigger than the Euros', anyway. :)
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 [this message]
1999-04-28 7:17 ` alex.buell
1999-04-28 15:41 ` Martin v. Loewis
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=19990428135134.3178.qmail@deer \
--to=craig@jcb-sc.com \
--cc=alex.buell@tahallah.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).