As Gene points out, you still want to make sure you don't have a dangling object reference when you come out of your TC block.
Custom does have a Destroy method if you need some code to run when your object reference is released regardless of why (i.e. normal operation or error condition). -- rk -----Original Message----- From: ProfoxTech [mailto:[email protected]] On Behalf Of Gene Wirchenko Sent: Friday, December 13, 2013 2:15 PM To: [email protected] Subject: Re: How to kill a class - Solved But does it kill the class? Custom does not have a .Release method so I simply use: release this If your problem had been in .Init(), then return .f. will prevent the instantiation. [snip] Sincerely, Gene Wirchenko _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/DF1EEF11E586A64FB54A97F22A8BD044229CABE5EF@ACKBWDDQH1.artfact.local ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
