From: "Dr. David Kirkby" <david.kirkby@onetel.net>
To: ams@gnu.org
Cc: aph@redhat.com, gcc-help@gcc.gnu.org
Subject: Re: Why is gcc going to default to "GNU dialect of ISO C99?"
Date: Wed, 10 Feb 2010 19:25:00 -0000 [thread overview]
Message-ID: <4B72FD26.2040004@onetel.net> (raw)
In-Reply-To: <E1NfGcp-0001XF-Oh@fencepost.gnu.org>
Alfred M. Szmidt wrote:
> I thought gcc's primary aim was to be a *C* compiler. That would
> suggest to me that enabling GNU extensions should not be the
> default, but an option.
>
> That is one of the goals, another goal is GCC is the compiler for the
> GNU system and its variant where we wish to make life easier for
> hackers by providing useful features, that might not be standard.
>
> You can usually work around these problems by calling c99/c89 instead
> of calling gcc.
>
I can't see how hackers can find it too hard to add an option, such as
-allow-GNU-extensions, so they, and anyone reading the code, are well aware they
are not writing C code, but some non-portable variant of it.
In contrast, permitting the extensions by default will lead people to be believe
they are writing C code, whereas in fact they are not.
Dave
next prev parent reply other threads:[~2010-02-10 18:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-10 17:00 Dr. David Kirkby
2010-02-10 17:26 ` Andrew Haley
2010-02-10 17:45 ` Dr. David Kirkby
2010-02-10 18:07 ` Alfred M. Szmidt
2010-02-10 19:25 ` Dr. David Kirkby [this message]
2010-02-10 20:59 ` Kevin P. Fleming
2010-02-10 18:39 ` Andrew Haley
2010-02-11 2:46 ` Ian Lance Taylor
2010-02-11 2:40 Dennis Clarke
2010-02-11 9:43 ` Alfred M. Szmidt
2010-02-11 12:00 ` Alexey Salmin
[not found] ` <C79952E6.1947E%eljay@adobe.com>
2010-02-11 13:48 ` Alexey Salmin
[not found] ` <C79973C1.194A3%eljay@adobe.com>
2010-02-11 14:58 ` Alexey Salmin
2010-02-11 15:11 ` John (Eljay) Love-Jensen
2010-02-12 5:32 ` Patrick Horgan
2010-02-11 13:44 Dennis Clarke
2010-02-11 14:00 ` Alexey Salmin
2010-02-11 14:14 Dennis Clarke
2010-02-11 14:42 ` Alexey Salmin
2010-02-11 14:50 Dennis Clarke
2010-02-11 17:14 Dennis Clarke
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=4B72FD26.2040004@onetel.net \
--to=david.kirkby@onetel.net \
--cc=ams@gnu.org \
--cc=aph@redhat.com \
--cc=gcc-help@gcc.gnu.org \
/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).