[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: bison-2.4 breaks gcc-4.3.2 build

From: Sergei Steshenko
Subject: Re: bison-2.4 breaks gcc-4.3.2 build
Date: Tue, 4 Nov 2008 13:39:38 -0800 (PST)

--- On Tue, 11/4/08, Akim Demaille <address@hidden> wrote:

> From: Akim Demaille <address@hidden>
> Subject: Re: bison-2.4 breaks gcc-4.3.2 build
> To: "Akim Demaille" <address@hidden>
> Cc: "Joel E. Denny" <address@hidden>, address@hidden, "Sergei Steshenko" 
> <address@hidden>
> Date: Tuesday, November 4, 2008, 1:33 PM
> Le 4 nov. 08 à 22:09, Akim Demaille a écrit :
> Adding an option is a PITA.
> I'm tempted by the envvar approach, but that's
> hacky :)
>       BISON_NO_ADDED_SEMICOLON=1 bison ...

Actually, adding a command line option is better generally speaking.

This is because command line option affects only the tool in question
('bison' in this case) while environment variables can collide since they
are global. At all, I once was forced in a work environment with 400+
environment variables, and awfully strange things were happening in it -
because when environment space is overflown, there is not even a warning.

So for the rest of my life I'm against environment variables :-).


reply via email to

[Prev in Thread] Current Thread [Next in Thread]