Home/ Questions/Q 5982611
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-22T22:06:42+00:00

I have some trouble with #define statements in my C++ code, however I’m not

  • 0

I have some trouble with #define statements in my C++ code, however I’m not familiar how to handle this in VC++:

>filetaint.cpp
1>.\filetaint.cpp(272) : error C2872: 'UINT32' : ambiguous symbol
1>        could be 'C:\Program Files\Microsoft SDKs\Windows\v6.0A\\include\basetsd.h(82) : unsigned int WIND::UINT32'
1>        or       '..\..\include\gen\types_foundation.TLH(80) : LEVEL_BASE::UINT32'
1>.\filetaint.cpp(275) : error C2872: 'UINT32' : ambiguous symbol
1>        could be 'C:\Program Files\Microsoft SDKs\Windows\v6.0A\\include\basetsd.h(82) : unsigned 
[...]

========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========

So the issue is that, that the compiler doesn’t know whether to use the definition from my Windows SDK “basetsh.h or from types_foundation.h. I want it to use the latter. Is there any construct in C++ namespaces to tell the compiler what to chose? I want to avoid to patch the SDK or the library itself. 

#include "filetaint.h"
#include "dift.h"

using namespace WIND;

The types_foundation.TLH contains the right statement. It is already in the VC++ paths in VS 2008. I’m a little confused here… but I guess I have to find a way to tell my compiler to ignore the SDK for the time being ;).

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I want it to use the latter.

    Then qualify your usage with the namespace name: LEVEL_BASE::UINT32.

    Alternatively, remove the using directives from your code and qualify all of the names that you use from the libraries. It’s a good idea to avoid using directives in most cases: they are far more trouble than they are worth.

    • 0