Re^5: (in cleanup) Can't call method "close" on an undefined value at somePerlModule.pm line number.

[roboticus]

thanos1983:

Typically you only need a destructor when you're using a resource that perl can't figure out how to release automatically.

I don't recall ever needing to use a destructor in perl, but the situations I can think of are typically things like having circular references that don't get freed automatically. Generally, though, my code doesn't worry about that, because between perl and the operating system, when the script ends, all the resources will be closed and freed.

I don't have any suggestions on how to recognize when you need one--but another monk might have a few. If it were me, I'd ignore destructors until you get more comfortable with learning OOP. Once you get a good handle on it, you'll probably start to figure out when destructors make sense.

...roboticus

When your only tool is a hammer, all problems look like your thumb.