Re: Error codes
Re: Error codes
- Subject: Re: Error codes
- From: Jens Alfke <email@hidden>
- Date: Mon, 21 Jul 2008 08:44:23 -0700
On 20 Jul '08, at 10:09 PM, Michael wrote:
I guess what I am referring to are the "message bubbles" that appear
during the compilation of my command line exercises ( from K&R). My
thought was that these messages must be generated from some program/
s ( as you pointed out)
The underlying C compiler that Xcode uses is GCC. (That's a very handy
keyword to use in web searches about compiler errors.)
But the errors you get should have textual messages, like "'foo'
undeclared; first use in this function", not numbers.
vertilab email wrote:
As of Leopard, MacErrors.h is no longer informative. Instead, you
have to use the
new Core Foundation Error functions to retrieve a descriptive string
for a
particular error code associated with an error domain.
No; where did you get that idea from? MacErrors.h still defines the
error numbers in the Carbon error domain. Nothing's changed about
that. The documentation you linked to just documents the new CFError
API, which is equivalent to NSError but now available with a
CoreFoundation API. This provides a way to return more detailed error
information, but it in no way obsoletes any particular error domain or
its error codes.
—Jens
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden