Re^4: How do I make the garbage collector throw an exception when it fails to auto-close a filehandle?

I’d want it global. Otherwise I’d subclass IO::Handle and instantiate that class instead; that works just as well and won’t conflict with anything else.

How does overriding DESTROY break thread safety?

Makeshifts last the longest.

Comment on Re^4: How do I make the garbage collector throw an exception when it fails to auto-close a filehandle?

Replies are listed 'Best First'.
Re^5: How do I make the garbage collector throw an exception when it fails to auto-close a filehandle? by ikegami (Patriarch) on Jan 14, 2007 at 06:22 UTC
If you attempted to limit the effect of the change to that one function (and those it calls) using `local *IO::Handle::DESTROY = sub { ... };`, your code wouldn't be thread-safe.	[reply] [d/l]


good chemistry is complicated, and a little bit messy -LW
	PerlMonks