RE: Link with static and dynamic version of SAME lib

From:

=?Utf-8?B?QnJ1bm8gdmFuIERvb3Jlbg==?= <bruno_nos_pam_van_dooren@hotmail.com>

Newsgroups:

microsoft.public.vc.language

Date:

Wed, 12 Jul 2006 03:48:03 -0700

Message-ID:

<B348761A-2B58-4DD6-B391-E6C6293E281A@microsoft.com>

I have this huge c++ app. In one of the projects, I am statically
linking with another library, say libmyalgos.lib. Now this is already
gone on production machines since 2 years. Now I have made many
enhancements to myalgos. But I don't want to break existing
application. So I want to make a DLL, say myalgos.dll and link it with
that project. Based on a configuration parameter I want to use either
the static function or the function from the DLL. To avoid conflict, I
have changed all the function names in the DLL by prefixing a NW_ to
the original name (like
#define sortdbbycol1 NW_sortdbbycol1 )
The program is compiling and linking properly. My question is how do I
now decide at runtime whether the static function or the NW_ version is
to be used based on a config file parameter?
Thanks in advance for your help.

access all functions through function pointers.
point the function pointers at runtime to the functions you want, based on a
value/values in a configuration file.

execute said function pointers.

This would be a simple solution.
You could even use a buttone to change between the old and new functions.
hat way you could enable users to do comparison tests.

--

Kind regards,
    Bruno.
    bruno_nos_pam_van_dooren@hotmail.com
    Remove only "_nos_pam"