Yesterday I realized that I had not called the close method for an open file. I would like to trap this situation when the file handle goes out-of-scope so that I can make sure that the close is in place.
A side affect of implementing the DESTROY method is that the method complains when the interpreter is stopped because the die function was invoked.
I would like to know why the reference is going out-of-scope in the DESTROY method so that I can elect to report the message or just let it go.