Re: Using SystemConfiguration API inside KEXT
Re: Using SystemConfiguration API inside KEXT
- Subject: Re: Using SystemConfiguration API inside KEXT
- From: Jens Alfke <email@hidden>
- Date: Tue, 11 May 2010 15:00:40 -0700
On May 11, 2010, at 2:45 PM, John B Brown wrote:
What you are describing does not appear to be either ANSI or
traditional C, unless I misunderstand Harbison and Steele.
K&R and ANSI C ran on plenty of operating systems that had no /usr/
include directory and didn't even use forward slashes as directory
separators, including VMS, CP/M, DOS, MS Windows and the 'classic' Mac
OS. So I really don't think you have any ground to claim that the
traditional Unix include path is somehow baked into any C standard.
In any case, not that it makes any difference to this argument, but
it's true that the ISO spec Jamison was quoting from is newer than
ANSI C. You might want to invest in a newer copy of H&S. Things have
moved on a bit since the original ANSI C standard was ratified in 1989
— C99 has some very useful features, not to mention the (!!
nonstandard!!) extensions found in GCC. ;-)
—Jens _______________________________________________
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