public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "falk at debian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/17096] gcc-3.4.1 allows statements before declarations
Date: Thu, 19 Aug 2004 08:47:00 -0000	[thread overview]
Message-ID: <20040819084747.8515.qmail@sourceware.org> (raw)
In-Reply-To: <20040819083835.17096.metze@samba.org>


------- Additional Comments From falk at debian dot org  2004-08-19 08:47 -------
>From the manual:

           The -ansi option does not cause non-ISO programs to be rejected
           gratuitously.  For that, -pedantic is required in addition to
           -ansi.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17096


  reply	other threads:[~2004-08-19  8:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-19  8:38 [Bug c/17096] New: " metze at samba dot org
2004-08-19  8:47 ` falk at debian dot org [this message]
2004-08-19  8:51 ` [Bug c/17096] " jsm at polyomino dot org dot uk
2004-08-19  9:25 ` metze at samba dot org

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=20040819084747.8515.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).