On Tue, Jan 18, 2022 at 2:54 PM Reuben Thomas <r...@sc3d.org> wrote: > > On Tue, 18 Jan 2022 at 18:38, Paul Eggert <egg...@cs.ucla.edu> wrote: > > > > I'm not sure a newer compiler would fix the bugs, as they're typically > > present in the ctype.h supplied by the OS. If the newer compiler comes > > with a fixed ctype.h you're OK; if it reuses or copies the old ctype.h > > you'll have a problem. > > I understood that the system compiler on Mac OS <10.8 did not have C99 > semantics for "inline". If it does, then indeed it doesn't matter, my > code will work anyway. In any case, I'm not concerned with the > contents of ctype.h or other headers; my concern is my ability to > declare my own functions "inline". In particular, I'm not affected by > ctype functions being declared in such a way that they don't have > external linkage.
If you are OS X 10.8 and above, then you will likely be using Apple Clang (or LLVM Clang), and you likely won't have troubles. OS X 10.6 switched to llvm-gcc. It should not have a problem with inline. https://releases.llvm.org/2.8/docs/CommandGuide/html/llvmgcc.html OS X 10.5 and earlier use GCC 4.2, and the compiler has Apple extensions, like the ability to parse Objective C and generate native code for it. It had the static/inline/external problems Paul discussed. Jeff
