On Sun, 15 Aug 2004, Roman Zippel wrote:
> On Sat, 14 Aug 2004, Adrian Bunk wrote:
> > > This is less a problem, as here it's clear that you want a boolean result,
> > > but something like "FOO=n" is really a string compare and FOO could be of
> > > any type (that 99% of all symbols are boolean/tristate symbols doesn't
> > > really help).
> >
> > Wouldn't it be better to require a string or hex to always be quoted
> > like "somestring"?
>
> What about normal numbers? I don't think requiring quotes everywhere for
> this is a good idea.
And numbers (both decimal and hex) can easily be distinguished from y, n, and m
anyway.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
kbuild-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kbuild-devel
