> From: "Kendall Bennett" <[EMAIL PROTECTED]>
>
> Wolfram Gloger <[EMAIL PROTECTED]> wrote:
>
> > Huh ? If this really happens, it is an obvious, and rather
> > horrible preprocessor bug. `4ub' _must_ be parsed as a single
> > preprocessor number token (although it is not a valid integer
> > constant token). See the ANSI C standard 6.1.8.
>
> It may well be an ANSI violation for this to work, but we all know
> that many compilers do not always follow the ANSI guidelines as much
> as we would like. Portability work is about making sure the code
> works with all compilers, more so than following the ANSI standard
> ;-).
I agree up to a certain point (the standard isn't perfect anyway), but
upon encountering such a basic bug in the preprocessor, I would run
(not walk) to the next alternative compiler.
> > And your examples for `badly used token pasting' and `rampant
> > problems' in the sources were ?
>
> The token pasting problem was in several places in the code, and we
> have fixed that in our copies.
I'm not going to nitpick further, but still I don't like your words:
the token pasting wasn't `badly' used -- it was completely normal.
You haven't `fixed' the code, you have installed a workaround.
Your post just came across at least partly as a complaint that
everyone is `just' using gcc, which is IMHO unfounded. No-one can
possibly account for violations of the standard in some compiler (even
more so if that compiler costs $$). The mesa sources have always been
quite clean and portable in my experience.
Regards,
Wolfram.
_______________________________________________
Mesa-dev maillist - [EMAIL PROTECTED]
http://lists.mesa3d.org/mailman/listinfo/mesa-dev
