Mail Archives: djgpp-workers/1999/10/21/04:00:58
Eli Zaretskii wrote:
> You forget about third-party libraries. There's libc, then there's
> second-level libraries like libdbg.a, then there are libsocket, etc.
> Only after all that, there's an application. Each one of these levels
> can install an FSEXT (libdbg.a already does), and the order of invocation
> should be app->lib->lib->libc.a->DOS.
Well, but in which order are FSEXTs defined in 3rd party libraries
called ?
That's not easy to define... If link order is important, then each FSEXT
could register itself at queue's tail (IIRC, constructors are called in
link order, right ?).
> How can several libraries define the order manually? I don't think
> there's a provision for this in the current fsext code.
It could be link order. So if lib1 and lib2 provide FSEXTs for the same
device, just the one coming first on the command line will be used.
"gcc usercode.c lib1.a lib2.a" will use services from lib1, but
"gcc usercode.c lib2.a lib1.a" will use services from lib2 ... This way
it's completly under user control...
BYtE,
Diego.
__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com
- Raw text -