This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
codebase:add_cpp [2017/05/25 03:21] vodur |
codebase:add_cpp [2017/05/25 03:30] vodur |
||
---|---|---|---|
Line 17: | Line 17: | ||
[[http://www.geeksforgeeks.org/write-c-program-produce-different-result-c/|http://www.geeksforgeeks.org/write-c-program-produce-different-result-c/]] | [[http://www.geeksforgeeks.org/write-c-program-produce-different-result-c/|http://www.geeksforgeeks.org/write-c-program-produce-different-result-c/]] | ||
- | C/C++ interop is well supported. We can compile C files as C into object files and C as C++ into object files and link them without issue. | + | C/C++ interop is well supported. We can compile C files as C into object files and C++ as C++ into object files and link them without issue. |
To access C functions from C++, C++ code will need to include the C headers (wrapping in extern "C" { }). | To access C functions from C++, C++ code will need to include the C headers (wrapping in extern "C" { }). | ||
Line 92: | Line 92: | ||
Basically, C++ is not guaranteed to be implemented as a char but it generally is, and almost certainly is and always will be when using GCC. We can even add the static asserts as above just for some peace of mind. | Basically, C++ is not guaranteed to be implemented as a char but it generally is, and almost certainly is and always will be when using GCC. We can even add the static asserts as above just for some peace of mind. | ||
+ | |||
+ | https://bitbucket.org/aarchon/mud_src/commits/branch/CPP_COMPAT | ||