News for hackers. Stuff that matters.
Re:Apple's Module proposal to replace headers for C-based la... by dietrichepp on Monday November 26, 2012 @08:03PM (#4834951)
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.
Re:Apple's Module proposal to replace headers for C-based la... by fleitz on Tuesday November 27, 2012 @02:49AM (#4836122)
Which is pretty much how linking to a shared library works, your #defines and #includes have no effect.
Re:Apple's Module proposal to replace headers for C-based la... by dietrichepp on Friday November 30, 2012 @02:35AM (#4852270)
Well, 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.