🚀 go-pugleaf

"Dmitry" <dmitry@pikalevo.com> wrote in message
news:46679fe4@newsgroups.borland.com...

> this solution seems  not trivial for my situation since i use
> bpl packages as dll libraries.

BPLs are more than just DLLs.  LoadPackage() calls LoadLibrary()
internally, but it also calls the package's initialization procedures
as well.  LoadLibrary() alone does not do that.  You MUST use
LoadPackage() instead of LoadLibrary() directly for BPL files.

> there are many other problems arise when i change my code
> to LoadPackage.

Then your code is likely using the packages incorrectly to begin with.

> For example i staring to get exeptions about double units since
> i change LoadLibrary to LoadPackage.

The same unit cannot be loaded by multiple packages in the same
process space at one time.  That is a core requirement of the BPL
architecture.  Shared code has to be in its own package that the other
package then list in their Requires list.

> Packages being loaded by LoadLibrary, normaly can use each other
> classes defined with PACKAGE macro.

LoadLibrary() does not execute a package's initialization code.

> perhaps i just have to obviously load all bpl that my application
> uses by LoadLibrary at application start, since LoadPackage
> does dependency check and loads packages also.

Or you could simply design your packages correctly in the first place.


Gambit