[kbuild-devel] Re: architectures with their own "config PCMCIA"

2004-08-16 Thread Adrian Bunk
On Mon, Aug 16, 2004 at 01:01:35AM +0200, Roman Zippel wrote: > Hi, Hi Roman, > On Sun, 15 Aug 2004, Geert Uytterhoeven wrote: > > > > 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 di

[kbuild-devel] Re: architectures with their own "config PCMCIA"

2004-08-16 Thread Adrian Bunk
On Sun, Aug 15, 2004 at 09:37:30PM +0200, Geert Uytterhoeven wrote: > 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

[kbuild-devel] Re: architectures with their own "config PCMCIA"

2004-08-16 Thread Roman Zippel
Hi, On Sun, 15 Aug 2004, Geert Uytterhoeven wrote: > > 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. I did consider this at some point, but I didn't

[kbuild-devel] Re: architectures with their own "config PCMCIA"

2004-08-16 Thread Geert Uytterhoeven
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/tri

[kbuild-devel] Re: architectures with their own "config PCMCIA"

2004-08-16 Thread Roman Zippel
Hi, 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).