1) Is it wise to allow a thread to escape its class? For instance, myThreadClass might call other classes (which may call other classes) and wander around the code a little before coming back. I've pre-cautionary protected all diskIO methods with CriticalSection.
2) If a thread is suspended and the main app thread/loop calls myThreadClass.MyMethod, will your code pause until (hopefully) the thread is resumed? 3) If you can't base your class on Thread, is it OK to instantiate a thread class and then call yourself? For instance myIneritedClass creates MyThreadClass (stored as a property) which immediately calls myInheritedClass.DoYourThing 4) Should threads be "closed"? Is it OK to allow a thread to just run out of code? Should it be specifically killed? Is it gracefully killed when the object has no references and gets eventually garbage collected? Thanks for the advice, oh ye Thread Gurus! _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
