> -----Original Message-----
.... revamped
> > >How about Inline::Jacc?
> > >
> > > Jochen's Alternative Compiler Compiler
> >
> It has the additional interpretation as "Just another
> compiler compiler",
> which is a nice meld of "Yet another compiler compiler" and
> "Just another
> Perl hacker".
Sounds all good to me.
Lates new from Inline::Pbyacc. There are 2 version of byacc that generate
perl code. Very unfortunatly they use the same version number but produce
completly different code. I will contact byacc owner(s) and see how we can
fix the version number.I don't want to force Inline users to use the modules
I compile, rather I would have Inline::Pbyacc check the version and adapt or
croak.
*****byacc1 : generates non object oriented code uses yylval
good: easy to 'objectify'
good: easy to link to Inline::Flex (easy to set yylval for the C lexer)
bad: can't use multiple instances of the perl parser class. I don't think we
can use multiple instances of Inline::Flex either
*****byacc2 : generates object oriented code, yylex returns a list. This was
made, I think, to ease the writting of the lexer in perl
good: OO
good: still easy to link to Inline::Flex (I will add some macros to do that
(� la "inline.h"))
bad: I don't think we can use multiple instances of Inline::Flex either.
bad: uses Fstream class instead of IO.
*****byyacc3: does not exist yet, I have to write the patches
good: what do you want here?
Can someone set priority so I develop the module that they need (I don't
need any special module I just think its cool)
Nadim
