Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
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?
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).