Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@whizzter
Copy link

No description provided.

@rofl0r
Copy link

rofl0r commented Nov 23, 2015

where does MSVC use outp ? that's a C namespace violation

@whizzter
Copy link
Author

Ok investigated it a bit more, made a minimal test case and found out that it seems to be a compiler bug inside MSVC 2008 and forward (2005 compiles fine).

If compiling the file as a C file (renaming the file to .cpp makes it compile again for some reason) this minimal example will produce an error.

char *outp;
int main(int argc,char **argv) { return 0; }

Chatted with a few guys while testing and we suspect that the outp (x86 port output function) has been made an intrinsic and that intrinsic is somehow buggy when compiling as a C file with MSVC (the symbol for outp is defined in conio.h but the error persists regardless of if the file is included)

Then the question is, do we try to work around this compiler bug or do we just ignore people using MSVC?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants