> So what did you mean by saying 'dangerous'? You should have read a little further in the message: "Possibly everything is fine for sqlite3 but documenting it as a general solution is IMHO not correct.". The scenario I was talking about assumed an initialization (before lib2 is loaded) and a finalization routine which would/could run in different librarie. This is not the case in your example. I proposed to test if the library was loaded before loading again as a more general solution to the problem. Don't get me wrong. I'm happy this is working for you. I'm only saying it is not a good idea to document/promote this as a general solution for avoiding problems with double loaded libraries. Ludo
-- _______________________________________________ Lazarus mailing list [email protected] http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
