Question

I am migrating from Visual Studio 6 to Visual Studio 2008 and I have a function of a component I am using named SetDefaultPrinter.

Unfortunately there is a windows library function now, SetDefaultPrinter, with the same name. And the macro associated with it is getting in the way of me using my function.

This is my workaround I have to call my function:

#undef SetDefaultPrinter
    pNova->SetDefaultPrinter();
#ifdef UNICODE
#define SetDefaultPrinter  SetDefaultPrinterW
#else
#define SetDefaultPrinter  SetDefaultPrinterA
#endif // !UNICODE

Is there a less ugly way around this? And no, I do not have control over that external component to change the name of the function.

Answer 1

This is why C++ added namespaces; too bad the Windows definitions can’t use them.

In another source module, where you do NOT include windows.h or any other Windows include files, generate a stub function to call your clashing function.

void MySetDefaultPrinter(CNova * pNova)
{
    pNova->SetDefaultPrinter();
}