Re: Leaks from bison 2.0/Flex 2.5

[Hans Aberg]

On 3 Oct 2005, at 15:35, Hans Aberg wrote:

> This leak is due to the allocation of a C-string for error  
> messages. The leak can be fixed by using std::string instead (which  
> I did in the skeleton file I am using).
>
> Bison and Flex are designed to just run as a program in one go, in  
> which case leaks will be recovered when the program terminates. In  
> such a use, they are probably not significant enough to be fixed, I  
> think, even though it would be more pleasing.

A lapse, mixing up Bison & Flex with the parsers/lexers they  
generate: It might be important to fix this then, if the parser is  
invoked many times in a program running for an extended time.

  Hans Aberg