> VC++6.0 isn't a very good compiler and it's not very compatible with
> gcc, while Visual Studio 2005 compiler is much more
> compatible and has a better optimizer.
>
> Plus, VC++6.0 had a closed "proprietary" data format for .dsp
> and .dsw files, while the current Visual Studio uses a
> standard XML format.
>
> Finally, Microsoft gives away (as in free, no cost) Visual
> C++ Express edition, which includes the current compiler.
>
> I don't see any reason we'd want to target VC++6.0.
>
>
> P.s. With the current Visual Studio, it's easy to add Bison
> and Flex custom rules, so that it automatically calls them
> for .y and .l files.
Right. It can be done. It's not quite that easy though - we need to
rename the output files as well, the default names generated by
bison/flex won't work.
//Magnus