# Visual Studio 2008: 'W' is for WTF?

This topic is 2923 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

## Recommended Posts

It is saying there is not such member 'GetObjectW' for ObjectGroup when CLEARLY the only method being called is 'GetObject'

What.

##### Share on other sites
Does that file directly or indirectly include windows.h or any of the other Windows headers? If so then you're now experiencing the joy of preprocessor rewrites of your code.

##### Share on other sites
Nope.

Lemme get back to my work computer and throw the source up here for you to browse.

##### Share on other sites
You're definitely including a Windows header somewhere in this source file. Otherwise, you wouldn't get an error message since the Tmx::Object::GetObject would also be changed to Tmx::Object::GetObjectW. Therefore the Tmx::Object header is not including a Windows header and map.cpp (or one of its dependencies) is. See if /showIncludes shows anything suspicious.

Also, here's a quickfix:
 #undef GetObject // OMG TEH WIN32 D:< 

##### Share on other sites
Did some research. Turns out the library I was using includes windows and it DOES in fact have a method named GetObject.

Using the quickfix before usage made it work. Thanks a bunch.

But WHY does Win32 DO that?? That's so messed up!

##### Share on other sites
They didn't consider the consequences of their decision hard enough at the time.

##### Share on other sites

Did some research. Turns out the library I was using includes windows and it DOES in fact have a method named GetObject.

Using the quickfix before usage made it work. Thanks a bunch.

But WHY does Win32 DO that?? That's so messed up!

If you enable unicode support in your build windows.h automatically replaces a certain set of functions with their unicode equivalents and since its done using preprocessor macros they are effectivly just dumb text replacements (Which is one of the reasons why C++ macros are such an awful idea)

This problem exists for pretty much all functions in the Windows API.

##### Share on other sites

They didn't consider the consequences of their decision hard enough at the time.

at the time, the dominant language was C, not C++, so function overloading wasn't an option. They could have just made everyone call the W version directly, but then people would have whined about how dumb all the API names were (like you sometimes see for the unicode C-runtime functions, e.g. wcslen). Plus Microsoft was already fighting an uphill battle to get people to accept that Unicode was a good thing rather than a waste of memory (ASCII should be good enough for anybody!) And even the people who were willing to accept Unicode didn't want to have to go through their entire program changing function names - porting to NT (from Win16) was enough work already. Plus if they did that then it wouldn't compile for 16-bit anymore and that was where the real market was.

The macros were a perfectly reasonable compromise at the time. It is unfortunate that they don't provide a way to use overloading instead of macros for C++ nowadays, but I imagine there's little real benefit and it would very likely increase compile times in addition to making the headers simply bigger.

##### Share on other sites
Learned new things today. Great reply, Anon Mike. +Like

• ### Game Developer Survey

We are looking for qualified game developers to participate in a 10-minute online survey. Qualified participants will be offered a \$15 incentive for your time and insights. Click here to start!

• 15
• 21
• 22
• 11
• 25