Re: bison and C++

[Satya]

> Putting the in the .y file would not suffice, as those functions need
> to be put in a file compiled by the C++ associated C-compiler;


Well, when Bison generates an xyz.tab. c file, it can be compiled by a C++
compiler. Thats the idea.

one
> cannot then use C++ containers. If the C-parser is compiled using a C+
> + compiler, would it succeed, in view of that support for this has
> been terminated, then the parser stack will not invoke copy
> constructors when reallocating: it will only work with POD semantic
> types.
The parser stack will not allow any special types anyway. You can put only
*pointers* to STL or user defined data types on the stack. I don't see how
reallocation of the stack can affect this. Maybe I am missing something. Can
you elaborate pls.. (maybe an example?)

satya.
--
Work expands to fill the time available for its completion (Parkison's law).
http://cs.uic.edu/~spopuri