--- On Tue, 11/4/08, Akim Demaille <[EMAIL PROTECTED]> wrote:
> From: Akim Demaille <[EMAIL PROTECTED]>
> Subject: Re: bison-2.4 breaks gcc-4.3.2 build
> To: "Akim Demaille" <[EMAIL PROTECTED]>
> Cc: "Joel E. Denny" <[EMAIL PROTECTED]>, bug-bison@gnu.org, "Sergei
> Steshenko" <[EMAIL PROTECTED]>
> Date: Tuesday, November 4, 2008, 1:33 PM
> Le 4 nov. 08 à 22:09, Akim Demaille a écrit :
>
[snip]
> 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 :-).
Thanks,
Sergei.
