On Sat, Jan 22, 2000 at 12:13:38PM -0500, [EMAIL PROTECTED] wrote:
> JNP> 'shutdown' method? I think you need to call 'cancel'. If you have
> JNP> a subclass, you can override the cancel method to add your own
> JNP> clean up:
>
> i don't subclass. i enclose the evnt object in my higher level object in
> most cases. the reason is i need more data that you have and i don't
> want to risk attribute collisions. one of perl's weakest OO areas. i
> also don't want to use damian's complex modules to solve this.
>
> so i will have to have my own method to close a server. and i generally
> use different names than you to work in my scheme. $server->shutdown()
> is my current choice.
Oh, that is perfectly reasonable.
> my problem is my own circular link highr than yours. so i require an
> explicit call to cancel/shutdown which will break the circle and clean
> up crap. it should get fully garbage collected. i will be testing this
> for memory leaks sometime. my daemons will be running forever and may
> create/destroy servers. definitely will create/destroy clients. i can't
> afford memory leaks.
Oh OK. Then you have to do the heavy lifting. It's a chore, but
Devel::Leak might help.
--
"Never ascribe to malice that which can be explained by stupidity."
via, but not speaking for Deutsche Bank
