Hi! I'm having a pretty big mess just because my static destructors are called before my non-static destructors. Now my question is; is this related only to win32 applications where one uses runtime.terminate?
The problem is that I am using external libraries, and in one of these cases you initialize the library and later on release it. I initialize and release the library in static de-/constructors. The external library I use is a sound library (FMOD). I have a sound class which uses library functions which in turn needs the library to be *initialized* and not *released*, when called. In the sound class, I release the sound file in the destructor, but this fails because the static destructor (which releases the library itself) has already been called, and therefore all library function calls are invalid. Are there any workarounds or solutions? And is it absolutely necessary to use the runtime initialize and terminate functions, since it works without any problems in a normal (non-win32) application. From what I know, static de-/constructors are called when the main function exits, but does it occur when the runtime, terminates when using a win32 application?