From: Patrick Horgan <phorgan1@yahoo.com>
To: Alexey Salmin <alexey.salmin@gmail.com>
Cc: gcc-help@gcc.gnu.org, dclarke@blastwave.org, aph@redhat.com,
david.kirkby@onetel.net, ams@gnu.org
Subject: Re: Why is gcc going to default to "GNU dialect of ISO C99?"
Date: Fri, 12 Feb 2010 05:32:00 -0000 [thread overview]
Message-ID: <4B748A50.3060900@yahoo.com> (raw)
In-Reply-To: <87a8dc11002110143u533f4451xc9fd0eb88ae3fca5@mail.gmail.com>
Alexey Salmin wrote:
> It all reminds me a story when I won a bottle of beer from my
> scientific adviser back in 2005. We had a bet: will gcc compile this
> code:
> #include <stdio.h>
> int main() {
> printf("a");
> int a;
> printf("b");
> return 0;
> }
> He was so sure that gcc won't allow it that didn't ever tried :) Thus,
> I think gnu extensions by default are not so bad :)
>
if you use -pedantic it will at least whine about it.
Patrick
next prev parent reply other threads:[~2010-02-11 22:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-02-11 17:14 Dennis Clarke
2010-02-11 14:50 Dennis Clarke
2010-02-11 14:14 Dennis Clarke
2010-02-11 14:42 ` Alexey Salmin
2010-02-11 13:44 Dennis Clarke
2010-02-11 14:00 ` Alexey Salmin
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
2010-02-10 20:59 ` Kevin P. Fleming
2010-02-10 18:39 ` Andrew Haley
2010-02-11 2:46 ` Ian Lance Taylor
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=4B748A50.3060900@yahoo.com \
--to=phorgan1@yahoo.com \
--cc=alexey.salmin@gmail.com \
--cc=ams@gnu.org \
--cc=aph@redhat.com \
--cc=david.kirkby@onetel.net \
--cc=dclarke@blastwave.org \
--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).