in reply to Re: Is assigning undef required for DESTROY to run?
in thread Is assigning undef required for DESTROY to run?

Yes it is a singleton, yes it is badly written, but no, it says it is a singleton. My code was abusing it. My issue with it is that it didn't protect itself (it stops me from doing everything else with it ;-)

Update: Just to be clear, I don't mean that it should protect me (necessarily) from my doing stupid stuff, but protect itself from being able to dump core. Dumping core implies memory corruption implies potential data corruption implies lack of trust in the underlying data storage.

--MidLifeXis

  • Comment on Re^2: Is assigning undef required for DESTROY to run?