[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bison's semantic parsers
From: |
Hans Aberg |
Subject: |
Re: Bison's semantic parsers |
Date: |
Tue, 10 Oct 2000 12:59:28 +0200 |
At 11.35 +0200 0-10-10, Akim Demaille wrote:
>Actually I never understood what drove to these names: hairy is
>definitely simpler to read that simple, and simple is much more hairy
>that hairy, imho.
I think that simple perhaps become hairy becuase of that dynamic allocation
stuff and the like. Isn't it time to switch to C++ when writing Bison? What
about GCC, does it still have problems with STL and such?
>There is a URL you didn't list: the PhD from Corbett. I have not read
>it yet because... it's in bitmap format! (While it clearly was written
>in TeX). Someday I'll download it (you have to do that page per
>page!!!) and read it, there is certainly much information in there.
>
>http://sunsite.berkeley.edu/Dienst/UI/2.0/Describe/ncstrl.ucb/CSD-85-251
Thank you, I tried to look for it but could not find it. Bit maps and
taking it down in pieces sound strange. Perhaps one take it down via some
script and pack it down as a tgz.
Hans Aberg
- Re: Bison's semantic parsers, Hans Aberg, 2000/10/07
- Re: Bison's semantic parsers, Akim Demaille, 2000/10/10
- Re: Bison's semantic parsers,
Hans Aberg <=
- Re: Bison's semantic parsers, Richard Stallman, 2000/10/11
- Re: Bison's semantic parsers, Hans Aberg, 2000/10/11
- Re: Bison's semantic parsers, Hans Aberg, 2000/10/12
- Bison and C++, Hans Aberg, 2000/10/14
- Re: Bison and C++, Richard Stallman, 2000/10/15
- Re: Bison and C++, Hans Aberg, 2000/10/15