[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bison development
From: |
Akim Demaille |
Subject: |
Re: Bison development |
Date: |
16 Jan 2002 18:32:01 +0100 |
User-agent: |
Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Common Lisp) |
>>>>> "Hans" == Hans Aberg <address@hidden> writes:
>> The idea is we are aware Bison is not modular, and that's what
>> we're doing. When will you understand that?
Hans> When I see it or the specs.
To see it you need to have a look.
Hans> I recall that you said that your C++ programs already have been
Hans> broken, which clearly happened because you have not developed a
Hans> proper C++ skeleton file.
No, because some PITA came asked for more C++ in a C skeleton. What
is broken is the use of the C skeleton for C++ development.
Hans> I think the problem is that your focus is on developing Bison
Hans> version 1.31.0000001. :-)
Every step made for 1.31 is a step for 1.49x.
Hans> nor do you want have the development work itself. :-)
>> No, we want it where it is needed, not where it will require more
>> work from us.
Hans> Well, try to run your broken C++ programs then. Drop a note on
Hans> this list when you have had some success. :-)
I'll only remember that you don't offer your help where we need some.
Thanks.
- Bison development, Hans Aberg, 2002/01/14
- Re: Bison development, Akim Demaille, 2002/01/15
- Re: Bison development, Hans Aberg, 2002/01/15
- Re: Bison development, Akim Demaille, 2002/01/16
- Re: Bison development, Hans Aberg, 2002/01/16
- Re: Bison development,
Akim Demaille <=
- Re: Bison development, Hans Aberg, 2002/01/16
- Re: Bison development, Akim Demaille, 2002/01/17
- Re: Bison development, Magnus Fromreide, 2002/01/17
- Re: Bison development, Akim Demaille, 2002/01/17
- Re: Bison development, Hans Aberg, 2002/01/17
- Re: Bison development, Hans Aberg, 2002/01/17