> Some light from Camel book 3rd edition, > 12.6.1. Garbage Collection with DESTROY Methods: > "When an interpreter shuts down, all its objects are destroyed, > which is important for multithreaded or embedded Perl applications. > Objects are always destroyed in a separate pass before ordinary > references. This is to prevent DESTROY methods from using references > that have themselves been destroyed." > > But something wrong in ActiveState Perl ;-(( > Are objects destroyed earlier than references and filehandles? > > I found two ways to avoid errors: > 1. Rename DESTROY and manually call it like ordinary object method. > 2. Objects must destroyed before "global destruction" (like above). > > -- > Best regards, > Lev
Lev, I agree with your two assertions. It would appear that the answer to the question is that filehandles are destroyed earlier than objects based upon my testing. This is a very interesting subject that has repercussions for filehandles in objects. I would love the opinion of an internals guru. Dirk Bremer - Systems Programmer II - ESS/AMS - NISC St. Peters USA Central Time Zone 636-922-9158 ext. 8652 fax 636-447-4471 [EMAIL PROTECTED] www.nisc.cc _______________________________________________ Perl-Win32-Users mailing list [EMAIL PROTECTED] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
