Re: [Pythonmac-SIG] MacOS X _POSIX_C_SOURCES and stuff

2006-02-09 Thread Bill Northcott
On 09/02/2006, at 5:44 PM, Ronald Oussoren wrote: > > This has nothing to do with C++ vs. C, but that Carbon/Carbon.h is > not POSIX compliant (and that's likely also true for other Apple > headers). Why do you say it is not POSIX compliant? As my test program demonstrates, it works correct

Re: [Pythonmac-SIG] MacOS X _POSIX_C_SOURCES and stuff

2006-02-08 Thread Ronald Oussoren
On 9-feb-2006, at 1:50, Bill Northcott wrote: On 09/02/2006, at 5:45 AM, Ronald Oussoren wrote: #define _POSIX_C_SOURCE 200112L #include int main () { } Is that a valid POSIX program? Don't define _POSIX_C_SOURCE if you use system libraries that are not part of POSIX. It is valid if so

Re: [Pythonmac-SIG] MacOS X _POSIX_C_SOURCES and stuff

2006-02-08 Thread Bill Northcott
On 09/02/2006, at 5:45 AM, Ronald Oussoren wrote: >> #define _POSIX_C_SOURCE 200112L >> #include >> int main () >> { >> } > > Is that a valid POSIX program? Don't define _POSIX_C_SOURCE if you use > system libraries that are not part of POSIX. It is valid if somewhat minimal program in both

Re: [Pythonmac-SIG] MacOS X _POSIX_C_SOURCES and stuff

2006-02-08 Thread Ronald Oussoren
On 8-feb-2006, at 13:18, Bill Northcott wrote: Not happy with the replies I received, I have ground this very small and think I now understand what is going on. Try the following test program: #define _POSIX_C_SOURCE 200112L #include int main () { } Is that a valid POSIX program? Don't defi

[Pythonmac-SIG] MacOS X _POSIX_C_SOURCES and stuff

2006-02-08 Thread Bill Northcott
Not happy with the replies I received, I have ground this very small and think I now understand what is going on. Try the following test program: #define _POSIX_C_SOURCE 200112L #include int main () { } Save it once as posix_test.c and again as posix_test.cpp. Try to compile them: [PM-G5BN