3 ms·
They're not ditching the processor, they're just making it so the preprocessor state is isolated for modules. You can still #define all you want, but it won't
by dietrichepp 14y ago
They're not ditching the processor, they're just making it so the preprocessor state is isolated for modules. You can still #define all you want, but it won't cross the boundary between your code and a module.
- fleitz 14y agoWhich is pretty much how linking to a shared library works, your #defines and #includes have no effect.
- dietrichepp 14y agoWell, no. If you make a #define it will affect code in the #include. This is why you sees puts defined as extern int puts(__const char *__s); The reason for the double underscore is so the definitions won't be affected if 's' is a macro.