public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Neil Booth <neil@daikokuya.demon.co.uk>
To: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
Cc: zack@codesourcery.com, gcc-patches@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: RFC: should we use -Werror?  (& sample patch to do it)
Date: Wed, 05 Sep 2001 15:06:00 -0000	[thread overview]
Message-ID: <20010905230530.A10346@daikokuya.demon.co.uk> (raw)
In-Reply-To: <200109051951.PAA27543@caip.rutgers.edu>

Kaveh R. Ghazi wrote:-

>  > No, the error issues from the tokenizer, which doesn't know anything
>  > about __extension__, nor should it (it would have to understand the
>  > expression grammar then).
> 
> Er, I just tried it and it works...

Well, only sort of.  You miss strings that appear only to the
preprocessor, like those in #defines that don't get used, #include
etc.

String handling will be moving closer to cpplib and out of the parser
sometime soon, so we really don't want it to rely on something in the
front ends.

Neil.

  reply	other threads:[~2001-09-05 15:06 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-05 12:52 Kaveh R. Ghazi
2001-09-05 15:06 ` Neil Booth [this message]
2001-09-05 19:09 ` Zack Weinberg
  -- strict thread matches above, loose matches on Subject: below --
2001-09-07 18:47 Kaveh R. Ghazi
2001-09-07 18:39 Kaveh R. Ghazi
2001-09-07 19:49 ` Zack Weinberg
2001-09-06  9:16 dewar
2001-09-05 20:54 Dan Nicolaescu
2001-09-06  8:44 ` Loïc Joly
2001-09-05 20:36 lucier
2001-09-05 12:09 Kaveh R. Ghazi
2001-09-05 12:33 ` Zack Weinberg
2001-09-07 10:10   ` Marc Espie
2001-09-26 16:52 ` Fergus Henderson
2001-09-26 17:05   ` Joseph S. Myers
2001-09-05 10:59 Kaveh R. Ghazi
2001-09-05 11:17 ` Zack Weinberg
2001-09-05 10:44 Kaveh R. Ghazi
2001-09-05 10:39 Kaveh R. Ghazi
2001-09-05 11:50 ` Richard Henderson
2001-09-04 20:32 Kaveh R. Ghazi
2001-09-04 23:32 ` Neil Booth
2001-09-05  0:27 ` Richard Henderson
2001-09-05  6:57 ` Geoff Keating
2001-09-05 10:35 ` Zack Weinberg
2001-09-05 10:40   ` Neil Booth

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=20010905230530.A10346@daikokuya.demon.co.uk \
    --to=neil@daikokuya.demon.co.uk \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=ghazi@caip.rutgers.edu \
    --cc=zack@codesourcery.com \
    /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).