<br><br><div class="gmail_quote">2008/12/18 Steve Harwin <span dir="ltr"><<a href="mailto:SteveH@myriax.com">SteveH@myriax.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br>
<br>
The had a another look at my code whilst trying to come up with a sample<br>
that shows the problem and I found that there was a chance that I was<br>
not always disposing the LASReader object, the dispose call is now in a<br>
finally block and since making that change I have not been able to<br>
replicate the version issue. I will keep testing and get back to you<br>
with a sample if the problem reappears.<br>
</blockquote><div>Hi steve.<br>humm. I believe the garbage collector call dispose when they think itīs time. We can call dispose using dispose manually like in GDI graphics. Perhaps i am wrong??.<br><br>The IDisposable interface defines a pattern (with language-level support) that provides a deterministic<br>
mechanism for freeing unmanaged resources and avoids the garbage collectorrelated problems inherent<br>with destructors.<br><br>If we would use the typical c++ destructor:<br>~killCScharpCodeClass()<br>{<br>// i am Kill<br>
}<br>we can not call the destructor by hand but using dispose we can.<br><br>The doub i have itīs if we have to call dispose always or only when we want ensure the destructor was called immediately.<br><br><br>Regards.<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
Thanks<br>
<font color="#888888">Steve<br>
</font><div><div></div><div class="Wj3C7c"><br>
_______________________________________________<br>
Liblas-devel mailing list<br>
<a href="mailto:Liblas-devel@lists.osgeo.org">Liblas-devel@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/liblas-devel" target="_blank">http://lists.osgeo.org/mailman/listinfo/liblas-devel</a><br>
</div></div></blockquote></div><br>