From: Mike Stump <mstump@apple.com>
To: Gabriel Dos Reis <gdr@integrable-solutions.net>
Cc: Mark Mitchell <mark@codesourcery.com>, Mike Stump <mrs@apple.com>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: static const double pi = 3.1415;
Date: Wed, 19 Feb 2003 15:57:00 -0000 [thread overview]
Message-ID: <2E054BFC-4421-11D7-B22E-003065A77310@apple.com> (raw)
In-Reply-To: <m3u1f0913i.fsf@uniton.integrable-solutions.net>
On Tuesday, February 18, 2003, at 11:33 PM, Gabriel Dos Reis wrote:
> I agree in principle; I'm just trying to find a middle-solution.
> Maybe there is none ;-)
I'd claim the standard is wrong, and we shouldn't be afraid to fix it.
Isn't the 5year coming up?! By having real world experience, we do,
with the extension, we strengthen the case for it.
Personally, I don't find
int i = 1;
to be substantially different from:
double i = 1;
:-( As far as extensions go, I've seen worse.
next prev parent reply other threads:[~2003-02-19 15:45 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-16 2:21 Mike Stump
2003-02-17 15:02 ` Gabriel Dos Reis
2003-02-18 8:55 ` Mark Mitchell
2003-02-18 9:12 ` Gabriel Dos Reis
2003-02-18 16:26 ` Mark Mitchell
2003-02-18 18:10 ` Joe Buck
2003-02-18 20:03 ` Phil Edwards
2003-02-18 20:29 ` Mark Mitchell
2003-02-18 22:27 ` Mike Stump
2003-02-19 18:24 ` Mark Mitchell
2003-02-20 20:38 ` Mike Stump
2003-02-20 21:16 ` Mark Mitchell
2003-02-19 7:55 ` Gabriel Dos Reis
2003-02-19 15:57 ` Mike Stump [this message]
2003-02-19 16:21 ` Gabriel Dos Reis
2003-02-19 17:12 ` Nathan Sidwell
2003-02-19 17:34 ` Mike Stump
2003-02-19 17:37 ` Nathan Sidwell
2003-02-19 17:44 ` Nathan Sidwell
2003-02-19 18:18 ` Mike Stump
2003-02-20 12:04 ` Nathan Sidwell
2003-02-20 19:52 ` Mike Stump
2003-02-19 8:52 ` Kai Henningsen
2003-02-19 9:22 ` Gabriel Dos Reis
2003-02-20 22:42 ` Kai Henningsen
2003-02-21 9:09 ` Gabriel Dos Reis
2003-02-21 16:48 ` Olivier Galibert
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=2E054BFC-4421-11D7-B22E-003065A77310@apple.com \
--to=mstump@apple.com \
--cc=gcc@gcc.gnu.org \
--cc=gdr@integrable-solutions.net \
--cc=mark@codesourcery.com \
--cc=mrs@apple.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).