Re: __attribute__((always_inline)) fiasco

From: viro
Date: Thu Sep 23 2004 - 12:46:29 EST


On Thu, Sep 23, 2004 at 10:33:15AM -0700, William Lee Irwin III wrote:
> On Thu, Sep 23, 2004 at 09:50:26AM -0700, William Lee Irwin III wrote:
> >> The // apart from being a C++ ism (screw C99; it's still non-idiomatic)
> >> will cause spurious ignorance of the remainder of the line, which is
>
> On Thu, Sep 23, 2004 at 06:21:04PM +0100, viro@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx wrote:
> > Usual Albert's taste level aside, you are wrong. Comments are replaced
> > with whitespace on phase 3 (tokenizer) and preprocessor lives on phase 4.
> > IOW, that // will never be seen by preprocessor.
>
> I'll be sure to put this on file with the rest of the numerous "while
> legal in C, never *EVER* do this" oddities.

Huh? Comments (all sorts of comments) are dealt with before you get to
preprocessing. Which *is* the right behaviour - anything else would be
much, much messier. What's the problem with that?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/