Rename function vs undef : conflicts with Windows API

Question

This has actually occurred twice now. I'm writing a cross-platform application, and some of my function names conflict with the Windows API. What I did (for example with LoadObject) was...

#undef GetObject

Is this an okay approach, or should I rename my functions?

Answer 1

If you're working with C++ you should put your functions into classes and namespaces to avoid these sort of problems (a.k.a methods).

Answer 2

You could put your functions in a namespace or a class (if applicable). If you are calling within a class then remember the this keyword. this->aliasedFunction();

Answer 3

If you intend for your code to be used alongside of the Windows API, I'd recommend renaming the functions. Yes, that's a hassle, but it's (in my opinion) better than undefining parts of the Windows API, even if you don't use those parts (someone else using your code might need to use those parts).