Printable View
My old IDE (Quincy) had options for creating/compiling both C and C++ source files, my new IDE (Visual Studio 6) only has the one: C++. Now, I know C code is essentially C++ code too and can be compiled in a C++ compiler, but I would think that, if given the option, compiling it in a C-specific compiler might be more appropriate.
So.. is there any advantage to be gained in using a C-specific compiler for compiling C code over compiling it in a C++ compiler?
Thanks.
Simply put your code between this:Code:extern "C" {
}
extern "C" has nothing to do with C programming or the OP's problem. You might want to look up what that means before suggesting it.Quote:
Originally Posted by Desolation
To the OP: Yes, there are advantages of compiling C in a C compiler over a C++ compiler. C and C++ both conform to different rules and standards that will effect your resulting application if compiled and linked as a different language from the one in which it was written. For instance returns on things like malloc() and the value of NULL is different in C and C++.
There are many free C compilers that you can and should use to compile your C programs. Try GCC or Dev-C++ if you prefer an IDE.
IIRC extern "C" is for linkage only. It doesn't actually allow you to parse and compile C source AS C.
Unless your compiler has an option to compile as C then you are kinda suck. Yes you'll be able to get really close but there will always be a few differences you won't be able to get avoid.
Thanks guys, I didn't feel quite right putting C code through a C++ compiler!
Dev-C++ looks like a nice full-featured IDE, I'll give it a try, thanks!
Most compilers follow the convention
foo.c would be compiled as C
foo.cpp would be compiled as C++
Also, most compilers can be forced into one language or another by various command line switches.
Totally from Memory
VS 6.0 command to compile in C is /TC
As Salem said, in VS 6.0, just name the file with a .c extention, and it will be compiled as C code, not C++.