Hello, Regardless of program loading design, wouldn't this feature be better coded using function pointers? Ie. Have a "register/load" function that maps functions in the exe?
PS. It would be helpful to have sqlite3OSMalloc() and sqlite3OSFree() as function pointers as well, so an application can do it's own memory management without recompiling SQLite library. Best regards, Kervin --- [EMAIL PROTECTED] wrote: > "Igor Tandetnik" <[EMAIL PROTECTED]> wrote: > > > > Note an inherent chicken and egg problem: you > can't build two DLLs (or > > an EXE and a DLL) using this approach where a > circular dependency > > exists, that is, where DLL A needs a function > exported from DLL B, and > > at the same time DLL B needs a function exported > from DLL A. To > > successfully link DLL A, you need an import > library from DLL B, but an > > import library is produced as a side effect of > link process, and to link > > DLL B you need an import library from DLL A, which > you can't build until > > you've built B, ... There is a way to break this > circle with the use > > of so called export files (.exp ), but the > technique is rather > > cumbersome. You don't want to go that way unless > there's a gun to your > > head. > > > > It's official then: The lack of sensible shared > library loader > is yet another reason to avoid windows at all costs. > In fact, > I'm thinking this reason will go near the top of the > list.... > > Thanks, everybody, for your help. > > -- > D. Richard Hipp <[EMAIL PROTECTED]> > >
