This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: -std's (was Re: v3 link failures analyzed)
- To: "Joseph S. Myers" <jsm28 at cam dot ac dot uk>
- Subject: Re: -std's (was Re: v3 link failures analyzed)
- From: Gabriel Dos Reis <gdr at codesourcery dot com>
- Date: 10 Jan 2001 21:36:32 +0100
- Cc: Gabriel Dos Reis <gdr at codesourcery dot com>, <libstdc++ at gcc dot gnu dot org>, <gcc at gcc dot gnu dot org>
- Organization: CodeSourcery, LLC
- References: <Pine.LNX.4.30.0101101935040.9635-100000@kern.srcf.societies.cam.ac.uk>
"Joseph S. Myers" <jsm28@cam.ac.uk> writes:
| On 10 Jan 2001, Gabriel Dos Reis wrote:
|
| > When you just want to compile a program with the most recent
| > standard without having to keep that of xxx:yyyy. We shouldn't get
| > more pendatic than necessary. It is a practical matter.
|
| If changing a Makefile once a decade is felt to be undue effort for this,
| then perhaps the option should be -std=iso9899 (for C - at present meaning
| iso9899:199409 until C99 support is complete) and -std=iso14882 (for C++)
| without qualifying dates?
The matter isn't changing makefiles a decade. It is about providing
user-friendly and intuitive flags reflecting existing practices. It
is about providing a non-obscure flag reflecting the most stringent
compliance to the most recent standard in use. I don't find it
reasonable to require user to recall the exact spelling. And I don't
find it unreasonable to provide a flag select the most recent standard.
Isn't it easier to teach that -iso selects both the most recent
standards for C or C++ instead of insisting on different numbers?
-- Gaby
CodeSourcery, LLC http://www.codesourcery.com