gnupic: Re: [gnupic] gpasm memory leaks
Subject:
Re: [gnupic] gpasm memory leaks
From:
Scott Dattalo ####@####.####
Date:
4 Jun 2007 21:28:13 +0100
Message-Id: <466475D5.5040009@dattalo.com>
David,
Ian questions the value of your gpasm memory leak investigation and goes
so far to suggest that free never be called. I was going to question the
value of your investigation too when I realized that the real value is
in the knowledge you'll gain in understanding gpasm. However, in general
for small programs that have constrained memory footprint I don't even
bother with deallocating memory. gpasm sort of fits into that category.
On the other hand, gpasm is really just a part of gputils which consists
of several utilities and a library. If we anticipate the library being
used in some other application where memory consumption is critical,
then free'ing memory is a good idea. The pCode optimizer may be such a
case.
Scott
