All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: Josh Triplett <josh@freedesktop.org>
Cc: linux-sparse@vger.kernel.org
Subject: Re: Feature request - allow boolean operations of undefined cpp symbols
Date: Fri, 20 Apr 2007 18:42:32 -0400	[thread overview]
Message-ID: <1177108952.8787.6.camel@dv> (raw)
In-Reply-To: <46288FA2.4040700@freedesktop.org>

On Fri, 2007-04-20 at 03:02 -0700, Josh Triplett wrote:

> This states that we must substitute 0 for any undefined preprocessor symbol
> in a #if or #elif condition, no matter what kind of expression they show up
> in.

My point was that it's more likely to be a user error in case of
non-trivial expressions.  But arguing with Linus about probabilities of
user errors and other fuzzy matters is not something I'm prepared to.

> However, Pavel, if you feel you could make part of -Wundef suitable to join
> the default set of warnings, feel free.

I really don't care about this part.  I actually think that sparse
should augment gcc capabilities rather than duplicate them.  If we
cannot do better than gcc, we can just stop bothering.

-- 
Regards,
Pavel Roskin

      reply	other threads:[~2007-04-20 22:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-02 17:37 Feature request - allow boolean operations of undefined cpp symbols Pavel Roskin
2007-02-02 18:25 ` Linus Torvalds
2007-02-02 21:56   ` Christopher Li
2007-02-02 22:30     ` Pavel Roskin
2007-02-02 22:10       ` Christopher Li
2007-02-02 22:58         ` Pavel Roskin
2007-02-02 22:45     ` Linus Torvalds
2007-04-20 10:02   ` Josh Triplett
2007-04-20 22:42     ` Pavel Roskin [this message]

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=1177108952.8787.6.camel@dv \
    --to=proski@gnu.org \
    --cc=josh@freedesktop.org \
    --cc=linux-sparse@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.