Joao, What a great wikipedia reference. Thanks! This new information makes the issues a bit clearer to me. One take on it would be: a) For garbage collection and implicit control, go with the finalizer concept. Though, there are those limitations and bad properties mentioned in the WikiPedia entry. b) For users who want to use an explicit control strategy, (i.e. call cleanup code and then assign to null), users could avoid declaring finalizer methods and go with explicit cleanup methods instead. Regards, Doug > -----Original Message----- > From: Joao Geada [mailto:joao@clkda.com] > Sent: Wednesday, January 10, 2007 10:20 AM > To: Warmke, Doug > Subject: Re: [sv-cc] FW: a question about system verilog > class deconstructor > > Doug: > > technically (in software engineering terms) these things > would not be destructors > but finalizers. http://en.wikipedia.org/wiki/Finalizer > > Joao > -- > ============================================================== > ================ > Dr Joćo Geada CLK > Design Automation > Chief Architect 295 Foster > Street, Suite 102 > 978-486 1056 x204 > Littleton, MA 01460 > ============================================================== > ================ > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Wed Jan 10 10:51:03 2007
This archive was generated by hypermail 2.1.8 : Wed Jan 10 2007 - 10:51:12 PST