MSVC vs. others

Do you need help? Ask here!

Bug reporting belongs here: http://developer.wz2100.net/newticket
User avatar
Buginator
Professional
Professional
Posts: 3285
Joined: 04 Nov 2007, 02:20

Re: MSVC vs. others

Post by Buginator »

OvermindDL1 wrote: Sorry, school/work decided to slam me for a bit.

The changes I made are relatively simple, just changed the couple varidic macro's to something useful otherwise.  I think there was one more change in the code somewhere, but it was simple as well.

I do have a pre-processor program that can fully preprocess the C99 syntax.  If I really wanted then I could just have VS run that as the preprocessor instead of having it do it itself, easy to setup, but meh...
OK, I am confused.  How do those changes make it be able to compile via C++?
Right now we do compile via /TP (Compile as C++ code), but that is not the same as converting the code to C++.

The filename extension determines how files are processed.  If you rename all the .c files to .cpp, and try to compile again, you will get tons of errors that you must fix.  That is what I thought you were talking about.
and it ends here.
User avatar
OvermindDL1
Trained
Trained
Posts: 35
Joined: 22 Dec 2007, 06:58
Location: NM, USA

Re: MSVC vs. others

Post by OvermindDL1 »

More specifically, the only issue is with the pre-processor.  In GCC (MingW and so forth as well), they support the C99 pre-processor, not all of VS can, it does still compile as C, but it uses the C++ pre-processor.
Image