🚀 go-pugleaf

"Oren Halvani" <Spam@Me-Please.com> wrote in message
news:41955b2e$1@newsgroups.borland.com...

> let me see if i understand it right, if Wininet.lib is not a static
> library will my progrtam run on all Windows versions (Win 9.x,
> ME, NT, 2000, XP, 2003) ?

If you are dynamically loading the DLL via LoadLibrary(), then yes.  You
will, of course, have to make sure that when you use GetProcAddress() to
retreive a function pointer, that the pointer is not returned as NULL before
you try to call the function.  Some WinInet functions are not implemented on
all OS versions.

> if i use LoadLibary instead, will my programm even start
> if the WinInet.dll isn't existing, correct ??

Yes, it will start.

> of course its muuuuch easier to link the lib instead of calling
> thousand times LoadLibrary( ) and GetProcAddress( )

True, although you don't need to make thousands of calls.  You should only
call LoadLibrary() once, and keep the DLL loaded for the entire duration
that you are going to use it, and then call FreeLibrary() when you are not
using the DLL anymore.  As for GetProcAddress(), you only have to call it
once for each individual function that you are interested in.  Are you
planning on call a thousand separate WinInet functions?  I doubt it.

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 have to make sure, that my program can also run without the WinInet.dll

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.


Gambit