public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/14331] please add option to suppress warning message "no newline at end of file"
Date: Sat, 28 Feb 2004 20:35:00 -0000	[thread overview]
Message-ID: <20040228203551.21961.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040228101052.14331.ahrivera@yahoo.com>


------- Additional Comments From pinskia at gcc dot gnu dot org  2004-02-28 20:35 -------
Confirmed, note that on some C preprocessors will just error out as this is required by the standard.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
          Component|c                           |preprocessor
     Ever Confirmed|                            |1
           Keywords|                            |diagnostic
   Last reconfirmed|0000-00-00 00:00:00         |2004-02-28 20:35:50
               date|                            |


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


  reply	other threads:[~2004-02-28 20:35 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-28 10:10 [Bug c/14331] New: " ahrivera at yahoo dot com
2004-02-28 20:35 ` pinskia at gcc dot gnu dot org [this message]
2004-06-29 23:57 ` [Bug preprocessor/14331] " crowder at fiverocks dot com
2004-06-30 13:44 ` bangerth at dealii dot org
2004-06-30 13:51 ` giovannibajo at libero dot it
2005-03-25 18:29 ` dank at kegel dot com
     [not found] <bug-14331-8015@http.gcc.gnu.org/bugzilla/>
2005-11-02  1:43 ` pinskia at gcc dot gnu dot org
2007-01-08  1:22 ` tromey at gcc dot gnu dot org
2007-01-22  8:52 ` manu at gcc dot gnu dot org
2007-03-06 14:44 ` JBoncek at Hunter dot Com
2007-03-27 15:26 ` dave dot korn at artimi dot com
2007-03-27 23:22 ` manu at gcc dot gnu dot org
2007-04-07 13:08 ` dave dot korn at artimi dot com
2007-04-07 15:01 ` pbrook at gcc dot gnu dot org
2007-04-10 14:12 ` davek at gcc dot gnu dot org
2007-04-10 15:42 ` patchapp at dberlin dot org
2007-04-17 17:48 ` davek at gcc dot gnu dot org
2007-05-07 12:45 ` patchapp at dberlin dot org
2007-05-28 16:38 ` fxcoudert at gcc dot gnu dot org
2007-05-31  2:07 ` davek at gcc dot gnu dot org
2007-06-11 22:00 ` pinskia at gcc dot gnu 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=20040228203551.21961.qmail@sources.redhat.com \
    --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).