Re: Bison generating C++

[Hans Aberg]

At 10.38 +0200 0-10-19, Akim Demaille wrote:
>There is something I think I should clarify about Bison.  There will
>be essentially no new feature before 1.29 is released.
>
>There is still a lot of dirty work to do, and by experience I know we
>have to put a hard limit.

Well, you are the guy ending up doing most of the programming, so it is up
to you to decide that.

> We won't work on issuing C++, nor even
>*think* about it because that means having long threads to debate this
>and that etc.  We don't have time now, let's save these threads for
>when we will really address these issues.

I did not think of that thread problem. :-)

>1.28 is a broken release, because of the gettext it includes.  People
>need a decent release of Bison.
>
>*Then*, we'll face the future :)

The tweak suggested by me is in itself not really a step into the future,
so a tactics you might employ is to do all that other Bison things you have
in mind right now first, and when that is finished, you throw the tweak in,
so that people start thinking about C++ output then. :-)

  Hans Aberg