Thanks for the replies, everyone. Yes, I see now that objects can be finalized while instance methods are still executing -- the first couple of test apps I put together, to demonstrate this, gave me false results for some reason.
Ok, so I grant that GC.KeepAlive(this) does have some effect. But what does this have to do with IntPtr fields? I mean, is there something special about IntPtr (like, maybe the reads/writes aren't atomic on all 64-bit processor architectures?) or can the rule be extended to include any field that represents the identity of an unmanaged resource, regardless of what type or how wide it is -- is the rule simply intended to prevent double-free bugs? -S =================================== This list is hosted by DevelopMentor� http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
