[vorbis-dev] Problems trying to run the examples in windows v orbis sdk

[Chris Parsons]

If DLL 'B' has an explicit call to DLL 'A', DLL 'A' will always be loaded
first even if the application initially calls DLL 'B'.

DLL's always get loaded in a 'Bottom up' fashion, where if 'A' calls 'B'
calls 'C' they will get loaded in the order 'C' B' 'A'.

Chris

-----Original Message-----
From: Chris Wolf [mailto:cwolf at starclass.com]
Sent: Thursday, September 06, 2001 5:45 PM

Ok, I added file mapped shared memory and copied the backend mapping
function pointers from vorbis.dll into it.
I was able to successfully see vorbisenc.dll invoke a function from a
pointer in shared memory,
pointing into vorbis.dll.

The question is this.  If DLL 'A' initializes the shared memory upon which
DLL 'B' is dependent,
what insurance is there that A gets loaded before B? (and thus A's DllMain
getting called before B's DllMain)
It just so happens, that in my case, vobis.dll gets loaded before
vorbisenc.dll.  I'd like to avoid explicit loading.
(I guess I could have B load then unload A, if I really had to...)

Oh, and BTW, we don't need inter-process access here -- the same process
loads the two DLL's.

        -Chris

--- >8 ----
List archives:  http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/
To unsubscribe from this list, send a message to 'vorbis-dev-request at xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is needed.
Unsubscribe messages sent to the list will be ignored/filtered.