-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Theo Van Dinter writes:
> On Wed, Mar 10, 2004 at 11:24:39AM -0800, Justin Mason wrote:
> > Because it's a public, supported API, used by at least 2 apps that use the
> > M:SpamAssassin perl API that I know of, and probably more.
> >
> > - -1 on removing it ;) I'll figure out some way to avoid the leak.
>
> I thought we were cleaning up the API for 3.0? That would include
> getting rid of functions we don't call ourselves and making the third
> party apps use the new API.
I don't really agree with that unless supporting the old APIs is hard
work -- this one really isn't, and really is widely used. I'd prefer
to minimise user pain, if it's easy enough to do.
> Anyway, the leak would be fixed, I believe, if you called check then
> $msg->{metadata}->finish(). iirc, the metadata code is what causes leaks
> during iterations. the rest of the Message object should, in theory,
> be ok for perl GC.
OK, will do that.
- --j.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Exmh CVS
iD8DBQFAT4vzQTcbUG5Y7woRAm68AKCguMmPdFyMN+dR6EfSXM2BljfCWwCeOPBy
/hg48IhKcYaqtr6X2cErKuA=
=IL8u
-----END PGP SIGNATURE-----
