Now when I run it throws a message box. Could someone elaborate on this design choice? The error has to be captured via or suppressed using with no complementary catch statement. Is the idea to force users to use within ?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.
Report problems with documented functionality
5 posts • Page 1 of 1
In Version 1.1.28
Thanks! I suspect I'm the only person who initializes classes within a temporary object.
Who is online
Users browsing this forum: No registered users and 14 guests