To elaborate… C[++] is really two different languages, with mostly distinct feature sets, handled in most cases by different compilers, interpreters, parsers, etc.
The unnamed language with keywords like #ifdef and #include which produces text output is a templating system that is functionally independent of the unnamed language with keywords like for and unsigned which actually compiles to a binary.
You can use cpp to run all the logic and conditionals in that first language to produce output, even if you replace the second language with something else like python or assembly.
You can use cc to compile that second language from source to binary, without support from the preprocessor.
That second language, the one that cc understands and compiles, does not have the ability to import functions or values or whatever from other files.
I’d argue that’s not true. That’s what the extern keyword is for. If you do #include, you don’t get the actual printf function defined by the preprocessor. You just get an extern declaration (though extern is optional for function signatures). The preprocessed source code that is fed to cc is still not complete, and cannot be used until it is linked to an object file that defines printf. So really, the unnamed “C preprocessor output language” can access functions or values from elsewhere.
The unnamed language that is compiled by
cc
.To elaborate… C[++] is really two different languages, with mostly distinct feature sets, handled in most cases by different compilers, interpreters, parsers, etc.
The unnamed language with keywords like
#ifdef
and#include
which produces text output is a templating system that is functionally independent of the unnamed language with keywords likefor
andunsigned
which actually compiles to a binary.You can use
cpp
to run all the logic and conditionals in that first language to produce output, even if you replace the second language with something else like python or assembly.You can use
cc
to compile that second language from source to binary, without support from the preprocessor.That second language, the one that
cc
understands and compiles, does not have the ability to import functions or values or whatever from other files.I’d argue that’s not true. That’s what the extern keyword is for. If you do
#include
, you don’t get the actualprintf
function defined by the preprocessor. You just get an extern declaration (though extern is optional for function signatures). The preprocessed source code that is fed tocc
is still not complete, and cannot be used until it is linked to an object file that definesprintf
. So really, the unnamed “C preprocessor output language” can access functions or values from elsewhere.Holy shit this is fascinating!