tag:blogger.com,1999:blog-2428374771421713311.post2005559595718494422..comments2024-03-10T12:04:17.661-07:00Comments on The Oracle at Delphi: When code lies - A better solutionAnonymoushttp://www.blogger.com/profile/10119008505905401707noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-2428374771421713311.post-21845707927030194552007-11-22T00:57:00.000-08:002007-11-22T00:57:00.000-08:00Lars, This trick is unecessary in .NET because of...Lars,<br><br> This trick is unecessary in .NET because of the GC.<br><br>Allen.Allen Bauerhttp://blogs.codegear.com/abauer/noreply@blogger.comtag:blogger.com,1999:blog-2428374771421713311.post-38510352500102620752007-11-22T12:05:56.000-08:002007-11-22T12:05:56.000-08:00C Johnson, What is wrong about it? It is merely ...C Johnson,<br><br> What is wrong about it? It is merely working with the tools that are available at the moment.<br><br>Allen.Allen Bauerhttp://blogs.codegear.com/abauer/noreply@blogger.comtag:blogger.com,1999:blog-2428374771421713311.post-79021048740732526402007-11-21T16:08:26.000-08:002007-11-21T16:08:26.000-08:00Be warned that this trick does not work in .Net. I...Be warned that this trick does not work in .Net. In .Net interfaces don't use reference counting and there is no telling as to when the garbage collection kicks in. And if the GC kicks in and cleans up the object the destructor Destroy is not called. in .Net the destructor is only called when Free is explicitly called.<br><br>Nonetheless it's a good trick in win32.Lars Truijensnoreply@blogger.com