languages/imcc Bison and Flex dependence

I note that currently imcc uses Bison and Flex.  Is there any compelling
reason for this?  I've sort of got it working with Sun's yacc and flex. Do
folks think it would be worthwhile for me to polish things up a bit and
post patches so it builds fine with either?

Or is the use of Bison/Flex a temporary convenience not intended for
general consumption and not worth worrying about?

Or would it be easier to simply include the bison and flex output in the
parrot distribution?

Or should we require bison and flex to build imcc?

[Historical aside:  One issue with some parsers is how well they handle
stack overflow (often set by YYMAXDEPTH).  Some parsers automatically
extend the stack; others don't.  In perl4, we ended up with the complex
perly.fixer script to run sed on the yacc output to patch it to handle
extending the stack.  In perl5, we decided to pre-generate the files with
byacc and then supply a single stack-fixing patch for the byacc output.
Pre-generating has worked well, except for the occasional time when
a pumpkin holder forgets to run C< make run_byacc >.]

-- 
    Andy Dougherty		doughera@lafayette.edu
    Dept. of Physics
    Lafayette College, Easton PA 18042

• languages/imcc Bison and Flex dependence by Andy Dougherty
• Re: languages/imcc Bison and Flex dependence by Leopold Toetsch