Re: Core Data entity name issue
Re: Core Data entity name issue
- Subject: Re: Core Data entity name issue
- From: Jens Alfke <email@hidden>
- Date: Mon, 02 Jul 2012 16:36:13 -0700
On Jul 2, 2012, at 3:55 PM, Chuck Soper wrote: Thanks for your response. I understand the fix and the cause, but I'm not
sure if this is a bug or not.
If it's a bug, it's one in the Unix standard library for using overly-generic names, but it's decades too late to fix that. :-p (You could also argue that a case-insensitive file system contributes to it, but let's not open that can of worms.)
At a minimum, it seems like a better error message could be displayed. That would be kind of hard. What happened is that you inadvertently overrode a common Unix header with a different header that has nothing in common with it (and isn't even valid C.) The compiler's going to barf pretty hard at that, and the error's not at a level where it can say something intelligent about it.
—Jens |
_______________________________________________
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