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.
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.
--
Randomly Generated Tagline:
"Meanwhile the US military officials are looking for their next target
in the war on terrorism. Today President Bush restated his commitment
to the war on terror, saying, "You're either with us, or against us,
or, in the case of Saudi Arabia, both."" - Bill Maher
pgppMQRcNHq2p.pgp
Description: PGP signature
