> - setting null/nothing is not needed for locally defined > objects, these > objects are "marked" for collection as soon as they go of > scope, since they > are not reachable anymore.
FWIW setting to null/nothing can actually have detrimental effects on the GC. If you set to null/nothing at the end of a routine, and the last time it was used was near the beginning, then if a GC occurred some place in the middle, the setting to null/nothing would actually be classified as a use, and the object would not be eligible for collection. So if you do set to null/nothing, make sure you do it immediately you are finished with it. Merak =================================== This list is hosted by DevelopMentor� http://www.develop.com NEW! ASP.NET courses you may be interested in: 2 Days of ASP.NET, 29 Sept 2003, in Redmond http://www.develop.com/courses/2daspdotnet Guerrilla ASP.NET, 13 Oct 2003, in Boston http://www.develop.com/courses/gaspdotnet View archives and manage your subscription(s) at http://discuss.develop.com
