On 11-May-2010, at 19:00, John B Brown wrote:
Dear Folk,
I see that, in addition to screwing up other GNU utilities, Apple
has screwed up the C and GNU compiler system. This is NOT porting, it is
pulling a SUN; call it standard but make it proprietary.
In order to write and compile C code on an Apple you must ignore
the workings of the C and GNU compilers and use a proprietary Apple system.
That is pure BULLSHIT!
The framework-supporting extensions have been part of GCC for, literally,
years. I might be wrong, but I’m pretty sure they were part of the
enhancements which NeXT contributed back to the GCC project as part of
support for Objective-C. It just happens that GCC only enables this
functionality when built for Darwin, but it’s part of the mainline source
(indeed, there have been plenty of people over the years asking if it can be
enabled on other platforms, too).
In this case, looking in framework paths for headers is a pretty
straightforward backwards-compatible enhancement. Not exactly “pure
BULLSHIT”, whichever way you look at it. You don’t ignore the workings of
the C and GNU compilers (which in many cases are one and the same — clang
behaves the same way, though, for obvious reasons); you just RTFM when
developing on the platform and be aware that the compilers do more on Darwin
than they do on other systems.
There are *dozens* of platform-specific aspects to the GNU Compiler System
and Binutils. Are they all bullshit, too?
M.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden