Re: Valgrind and Bison memory leaks

[Joel E. Denny]

On Wed, 8 Nov 2006, Paul Eggert wrote:

> OK, I reviewed that patch and installed the following
> slightly-different one.  The main thing was that funny union, which
> confused me, and so I replaced it with a char const * value and a char
> * storage pointer (which might be null, but can be freed).

Thanks, I'll look it over later today.

> "make maintainer-check-valgrind" has a lot of failures still, but I
> assume more patches will come later?

I had no failures after my original patch.  I'll review this one later.