On 16 Nov 2006, at 7:48 PM, Rick Mann wrote: I know, but I honestly can't think of a better list for such questions, except perhaps Darwin-dev. But I think coding standards can reasonably be included in Xcode discussions. I am using Xcode for this project, rather than Makefiles. :-P
By that logic, discussions of planetary climate simulations are on-topic for this list, so long as they are edited or built with Xcode. And you can do make builds from Xcode. A question like "does Mac OS X comply with POSIX?" would seem to be more-than-perhaps within the brief of darwin-dev.
Some of the code I'm trying to port from Solaris uses uchar_t. In the Solaris header file, there's a comment that suggests uchar_t is a POSIX-standard name for the type, but I can't find that type defined anywhere under /usr on my Mac OS X machine. Since Mac OS X is purportedly POSIX-compliant, I was wondering how best to reconcile this?
Comments are sometimes self-serving, and may even be untrue. What, besides a comment in a stranger's header that only _suggests_ uchar_t is a POSIX standard, leads you to believe it is so?
When I Googled "POSIX integer types" and "POSIX uchar_t," I found a description of sys/types.h that didn't include that symbol, and lots of code written by reputable engineers who found it necessary to #define a UCHAR_T, as if they did not find an equivalent type on their various systems. And no, they never #defined UCHAR_T to "uchar_t," as they might do in a POSIXLY_CORRECT configuration f they could.
Perhaps the Google search you performed before you posted turned up something different?
— F
|