Re: Annoying 'parse error before' messages
Re: Annoying 'parse error before' messages
- Subject: Re: Annoying 'parse error before' messages
- From: Adam Radestock <email@hidden>
- Date: Sat, 13 Jan 2007 17:09:16 +0000
I created this project by choosing Cocoa CoreData App in Xcode, and
it has been working for about 6 months with only one incident of this
before, and as I say, I can't remember how I fixed it then...
On 11 Jan 2007, at 8:57 am, Philip Q wrote:
On 11/01/07, Adam Radestock <email@hidden> wrote:
Hi, I'm having a nightmare trying to find out what is causing these
parse errors... What am I doing wrong?
In file included from /Development/Current Projects/ScreenRunner VJ/
ScreenRunner_VJ_AppDelegate.m:9:
/Development/Current Projects/ScreenRunner VJ/
ScreenRunner_VJ_AppDelegate.h:54: error: parse error before
'NSPersistentStoreCoordinator'
/Development/Current Projects/ScreenRunner VJ/
ScreenRunner_VJ_AppDelegate.h:59: error: parse error before
'NSPersistentStoreCoordinator'
/Development/Current Projects/ScreenRunner VJ/
ScreenRunner_VJ_AppDelegate.h:60: error: parse error before
'NSManagedObjectModel'
/Development/Current Projects/ScreenRunner VJ/
ScreenRunner_VJ_AppDelegate.h:61: error: parse error before
'NSManagedObjectContext'
/Development/Current Projects/ScreenRunner VJ/
ScreenRunner_VJ_AppDelegate.h:62: fatal error: method definition not
in @implementation context
compilation terminated.
{standard input}:12:FATAL:.abort detected. Assembly stopping.
The errors are complaining about Core Data classes. Are you linking
with the Core Data framework, and have you included the appropriate
headers?
(Unfortunately, Xcode/gcc doesn't tell you when it can't find the
definition of a class, and just calls it a "parse error")
-Phil
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden