Re: Problems with multithreading and slow compilation

[Laurence Finston]

On Wed, 7 Jul 2004, Paul Eggert wrote:

> > Would the Bison developers have any interest in implementing
> > the following features?
> >
> > 1) making it possible to redirect the debugging output to files,
> >    one for each invocation of `yyparse()'.
> >
> > 2) Protecting `stdout' and `stderr' with mutexes, to keep
> >    writes to these streams from being interrupted
> >    (unless they are already, of course).
>
> These both sound like worthy features.  Can you get the effect that
> you want by defininig YYFPRINTF?  If so, then perhaps we just need to
> make this sort of thing easier (since not everyone will think of doing
> that).
>

I'll give it a try when I get a chance and let you know.  Thanks for the
suggestion.

>
> > What I'd like is a way of breaking up the actions for the rules into
> > multiple compilation units, so that only the parts that have changed
> > will need to be recompiled.  Is this something the Bison developers
> > might consider implementing?
>
> We might consider it, yes, but it sounds hard.
>

It sounds hard to me, too.  I think it might be worthwhile for large
parsers, though.

Laurence