Re: bison'd files don't compile under Microsoft VC++

[David Gluss]

You're espousing essentially the philosophy of HP...where programs
have to have special defines to compile with usual practice, as opposed
to what the standards bodies have defined.  Yes, we're used to these
arguments.  The bright side is that they provide job security for some
guys who like fooling around with this stuff.
Unfortunately I've been programming for 36 years and I'm
having trouble giving it up, and I prefer doing new things to fixing old
ones.
Please recall that I'm not begging you to go support MS in a new product...
I just wish you guys hadn't broken an existing working one.
DG
----- Original Message -----
From: "Hans Aberg" <address@hidden>
To: "David Gluss" <address@hidden>
Cc: "Akim Demaille" <address@hidden>; <address@hidden>; <address@hidden>;
"Paul Eggert" <address@hidden>
Sent: Thursday, February 14, 2002 2:24 AM
Subject: Re: bison'd files don't compile under Microsoft VC++


> At 17:13 -0800 2002/02/13, David Gluss wrote:
> [Please quote only relevant material.]
> >this is the MS compiler as of a week ago.
> >DG
> >It would be really nice if I (and everyone else in the world) didn't have
to
> >change their source code.
>
> Don't program then. :-)
>
> >  Considering how trivial the patch is, and how
> >pervasive the Microsoft C compiler is, I'm surprised that this seems such
> >a hard problem.
>
> You know, MS has officially said that "there is no standard we can't
> improve" that is, systematically trying to destroy the usefulness of
> standards by using the weight of the company. -- If that policy causes
> problems for MS users, then MS users should go to MS and complain, not to
> those that follow the standards.
>
>   Hans Aberg
>
>