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

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

Agreed, and that is what my bug report says :-). The connection is supposed to be one-at-a-time, which, to me as well, means that they should be catching if a second call is made before the first connection is released.

--MidLifeXis

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

Replies are listed 'Best First'.
Re^3: Is assigning undef required for DESTROY to run? by Bloodnok (Vicar) on Feb 24, 2009 at 09:12 UTC
More than that, IMO, the module shouldn't be advertising the constructor as an integral part of the interface - rather, something more like that shown in Monadic Classes. A user level that continues to overstate my experience :-))	[reply]

In Section Seekers of Perl Wisdom