L
Lieven De Foor
Guest
Then that must be one of the reasons why overriding Dispose() in a hybrid is not allowed? Does the proxy get an override for Dispose(), first calling base
ispose(disposing) and as last step calling back to the ABL to have things cleaned there? If it was overridable, then calling SUPERispose(disposing) would have to be the final statement in that method, or else you would mess things up pretty badly (no GC of the object would happen). If Dispose() is not called during the lifetime of the object, then the finalizer will ensure it gets called eventually, and that could happen on another thread, so that's probably another reason not to allow overriding it ( knowledgebase.progress.com/.../Why-is-the-Dispose-method-FINAL-in-ABL) See also docs.microsoft.com/.../dispose-pattern We've had some Dispose related issues fixed, but I'm afraid we've recently logged a new one (00463658), which might end up on your plate sooner or later...
Continue reading...
ispose(disposing) and as last step calling back to the ABL to have things cleaned there? If it was overridable, then calling SUPERispose(disposing) would have to be the final statement in that method, or else you would mess things up pretty badly (no GC of the object would happen). If Dispose() is not called during the lifetime of the object, then the finalizer will ensure it gets called eventually, and that could happen on another thread, so that's probably another reason not to allow overriding it ( knowledgebase.progress.com/.../Why-is-the-Dispose-method-FINAL-in-ABL) See also docs.microsoft.com/.../dispose-pattern We've had some Dispose related issues fixed, but I'm afraid we've recently logged a new one (00463658), which might end up on your plate sooner or later...Continue reading...