[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Re: Memory (de)allocation ...
From: |
Hans Aberg |
Subject: |
Re: Re: Memory (de)allocation ... |
Date: |
Mon, 5 May 2003 20:40:27 +0200 |
At 19:12 +0100 2003/05/05, Ricardo Rafael wrote:
>> There is a C++ skeleton file for generating C++ called lalr1.cc in Bison
>> 1.75. I could not make it work, so I made my own version; unfortunately my
>> version also requires some additional Bison tweaks, so it would not help
>
> thanks but I need production quality template (code) now! :)
>Migrating from Bison C Pure-Parser to a C++ reentrant template is not an
>option (at least right now!). I just wanted to know from anyone who has
>already been in the same situation (eliminate memory leakage from
>production quality code using reentrant Flex(C++)/Bison(C)).
It is not just the question of leakage -- the C stacks do not invoke the
C++ copy constructors either. So at the first C stack reallocation, if you
have non-trivial C++ copy constructors, your program goes out of the window.
> Anyone else?!
Have you tried the moon? :-)
Hans Aberg