From:	nordwick AT scheme DOT XCF DOT Berkeley DOT EDU (Jason Alan Nordwick)
Subject:	Re: fLex and bYacc revisited....
22 Feb 1998 17:36:38 -0800 :
Message-ID:	<19980222193231.15198.qmail.cygnus.gnu-win32@scheme.xcf.berkeley.edu>
References:	<34EE6FE8 DOT 36751538 AT erols DOT com>
Mime-Version:	1.0
To:	Sean McBride <sean DOT mcbride AT erols DOT com>
Cc:	"gnu-win32 AT cygnus DOT com" <gnu-win32 AT cygnus DOT com>

Sean McBride, on Sat 2/21/1998, wrote the following:
> 
> I do have a good reason... I am trying to get the code that results from
> fLex and bYacc to compile in an existing COM application... therefore, I
> am trying to import just the libraries I need to get it to compile then
> do the collisions manually... do you know of anything that is already
> done that may speed this process up ... or maybe some lex yacc clones
> that produce out of the box MS VC++ compilable code...?
> 

What collisions are there ?  Different lex implementations have different
code in the libraries.  Almost all have main().  Many have helpful
routines that support other features, such as yymore(), yyless(),
yywrap(), and REJECT.  Yacc implementations also vary, but most
almost always contain main() and yyerror().

The only two that you will probably have to deal with would be
yywrap() and yyerror(), but if you put them in the third sections
of lex and yacc (respectively) it will be no problem:

  int yywrap ( )           { return 1; }
      yyerror( char *msg ) { fprintf( stderr, "%s\n", msg ); }

There are the defaults.

I don't know if this helps, but I would like to know what the problem
is and I have to soon port an application I wrote for work to win32
it is has 3 lexers and 2 parsers so I would really like to know how you
solved the problems.

Thanks
Jay


-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -