🚀 go-pugleaf

In article <1992Oct07.192423.2842@ans.net> db3l@ans.net (David Bolen) writes:
>Note that this doesn't solve the problem when a DLL has functions
>removed from it's interface, as OS/2 will not even allow the
>application to start due to unresolved references.  So if you want to
>make sure and support backlevel applications, you have to at a minimum
>have stub functions for all previous revisions of your DLL to get by
>the load-time checking.

The solution is to structure your DLL as an API.  That is, every
function returns error codes, or zero for OK.  If values need to be
passed back, use output parameters.  Now, you do not EVER delete a
reference from the DLL.  Instead, you change the code so it just
returns a constant (you should define a constant like
FUNCTION_NOT_IMPLEMENTED for this purpose).

This way, references are always resolved by the linker, and your code
will always get far enough to check versions.  Plus, if you call a
function that hasn't been implemented, you know it from the non-zero
return code.
-- 
David Charlap         |"there aren't 50,000 things for which it's worth writing
dic5340@hertz.njit.edu| software; and the computer industry doesn't have enough
----------------------+ programmers to create that much good software.
Therefore, most of it must be worthless" -- Boris Beizer "The Frozen Keyboard"