>Yeh, well, take a few whacks at Bison. It's been -- um -- emotionally
>disturbed by this news. Apparently, it likes being dumped as much as people
>do ;-)
Hmmm...
sounds kinda scary to have emotionally disturbed a Bison ... !
>Possible, but that code would be even scarrier. The idea is to write a tool
>so I never, ever have to even open the generated C file.
What's so scary about interpreter code? If you have some discipline
coding, I'm sure one could write pretty understandable code.
>You did write one, didn't you, for Velocity [sic]?
It was more an interpreter. It didn't have a lexer which made things
rather slow, and it used lots of individual C++ class instances which
slowed down things to a crawl.
>LOL. It'll probably use malloc/free.
Not bad. Though the MSL'd memory and file management code is overly
complicated.
>How about any reasonable compiler, because an ANSI-compliant C++ compiler
>on every platform is a fool's paradice (at least until 2050).
Would be nice, but since everyone's heading towards ANSI these days, I
hope we can live with creating modified versions for non-ANSI compilers
that just differ in 2 or three #defines or so.
Cheers,
-- M. Uli Kusterer
------------------------------------------------------------
http://www.weblayout.com/witness
'The Witnesses of TeachText are everywhere...'
--- HELP SAVE HYPERCARD: ---
Details at: http://www.hyperactivesw.com/SaveHC.html
Sign: http://www.giguere.uqam.ca/petition/hcpetition.html
