Ok, here we go again..it's a new project, a new cubical and a code base that I need to start familiarizing...well that adds up to, I don’t get time to blog or at least read something new, ye the same old story..
After much consideration I applied for an ADSL line at home, my first thought was not too, as the weekends are allocated for family, friends and long hours of sleep, but then again I could at least do something...so I went for it.
The funniest thing was that I applied through SLT last month and still my ADSL line was not activated. Finally I called the branch I applied the line through, to find out that my application never reached the ADSL division, great!!!.
I had something to say to SLT that day over the phone...and the operator called me back after 10 minutes to apologize and to say that she will submit it to the ADSL division right away. So hopefully I will be back to blogging in a couple of days.
This is a post about object finalization in .NET. Finalization is not as inexpensive as we think, it increases the pressure put on GC.All objects that need finalization are moved into a finalizable queue and the actual finalization happens in a separate thread. Because the objects full state may be needed, the object itself and all the object it points to are promoted to the next generation (this is needed so that GC does not clean these objects off in the current round), and these objects are cleaned up only after the following GC. Due to this reason, resources that need to be released should be wrapped in as small a finalizable object as possible, for instance if your class needs a reference to an unmanaged resource, then you should wrap the unmanaged resource in a separate finalizable class and make that a member of your class and furthermore the parent should be a non-finalizable class. This approach will assure that only the wrapped class (class that contains the unmanaged resourc...
Comments
Post a Comment