RE: Bison fast questions

[Cenzato Marco]

Hi Paul!

> Does that compiler define __C99__FUNC__ instead?  
The MS Visual Studio 2005 compiler doesn't define __C99__FUNC__.

> Please list all the predefined macros
You can find a full list of the predefined macros in MS VS 2005 C/C++ compiler 
at
<http://msdn2.microsoft.com/en-us/library/b0084kay.aspx>

About flex, the flex version at <http://lex.sourceforge.net/> is 2.5.31
when the version I've test (downloaded at 
<http://gnuwin32.sourceforge.net/packages/flex.htm>)
is 2.5.4a: at this point I prefer to use the latest and workaround the /W64 
related wornings postprocessing the generated c souce with sed.

Thank you very much

Good 2006

-----Original Message-----
From: Paul Eggert [mailto:address@hidden 
Sent: giovedì 29 dicembre 2005 22.55
To: Cenzato Marco
Cc: address@hidden
Subject: Re: Bison fast questions

"Cenzato Marco" <address@hidden> writes:

> I've downloaded both bison for windows 2.1 and flex for windows 2.5.4a
>
> The parser is ok: I've integrated it into my development environment
> (MS VS 2005) and - except for a #define __STDC__ that MS Compiler
> with MS extensions enabled doesn't define

Does that compiler define __C99__FUNC__ instead?  If so, this problem
should be fixed in the next version of Bison; see
<http://www.mail-archive.com/address@hidden/msg00401.html>.

If not, what macros does it define?  Please list all the
predefined macros, if possible.

> No so good news about Flex, indeed.

> I've 2 warning when compiling Flex generated .c source code with
> the same /W64 switch:
> warning C4267: '=' : conversion from 'size_t' to 'int', possible loss of data
> warning C4244: 'initializing' : conversion from '__w64 int' to 'int', 
> possible loss of data.
> Both that warnings are serious, as you can see... 
>
> Do you know who the flex maintainers are? Can I write to them?

Please see <http://lex.sourceforge.net/>.  Not much activity lately,
I'm afraid.