Quantcast
Channel: What dangers lurk by un-defining proprietary compiler macros? - Stack Overflow
Browsing all 2 articles
Browse latest View live

Answer by Bathsheba for What dangers lurk by un-defining proprietary compiler...

Using a variable that starts with an underscore followed by a capital letter is undefined behaviour.Don't do it.(I've seen _MT standing for "use multithreaded runtime").

View Article



What dangers lurk by un-defining proprietary compiler macros?

In my C++ class, I have a private variable defined asunsigned int _MT;This worked fine until I tried using the Intel C++ compiler. When I used the Intel compiler (version 15.0.xx) I get the error:......

View Article
Browsing all 2 articles
Browse latest View live




Latest Images