> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Wednesday, June 07, 2006 10:36 AM > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] DLLs containing user-defined SQL functions > > > 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....
Pardon my ignorance about *nix, but what happens during this whole global symbol mapping thing if two libraries both export the same function name? If SQLite only looked to the exe to provide this function, then what would happen to folks writing their own libraries that abstracted the database layer, but wanted to provide their own userdef functions from within their library ... would SQLite find the function in their library instead of the exe? What if the exe and/or two other dependent libraries all exported the function too and had their own userdefs ... how would SQLite handle all these libraries wanting to add their userdefs to SQLite?
