Changed __Delete to catch and report exceptions when called during object cleanup. It previously had the (erroneous) effect of "postponing" the exception until the next function call or the end of the try-block/thread.
Now when I run
FileDeleteit throws a message box. Could someone elaborate on this design choice? The error has to be captured via
catchor suppressed using
trywith no complementary catch statement. Is the idea to force users to use
try, catch, finallywithin