🚀 go-pugleaf

Remy Lebeau (TeamB) wrote:

>On the other hand, if you do statically link to the lib file, then not only
>does the DLL itself have to exist, but so does every individual function
>that your code calls.  If you run your program on a system that does not
>have every single WinInet function that your code calls statically, then
>your program will fail to start at all.

I don't think that last part is correct.
I don't think the startup even knows which functions you use.
It just fills in the table with what it finds in the dll.
If a table entry isn't filled in (new function, didn't exists in old
dll) then if the application calls it, it gets a return error of
function not supported.

For example: CopyFileEx on '98 system has GetLastError of 120.
Same for MoveFileEx
Took me a while to figure out that "This function is only valid in
Win32 mode" means it's a new funtion  :->


>Then LoadLibrary() and GetProcAddress() are your only option.  Of course,
>had you been using BCB 5 or 6, you could make use of their Delay-Load
>mechanism to statically link to the DLL functions in your code while still
>providing run-time loading of the DLL when needed.  A very nice feature to
>use if you have it available.

It's an ilink32 option.
(Not saying it's not new in b5, just if one were to look for it,
that's where you'd find it)