[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Core Data
From: |
Gregory Casamento |
Subject: |
Re: Core Data |
Date: |
Sun, 29 May 2011 15:42:20 -0400 |
It would lead to linker issues. I believe using id should suffice.
On Sun, May 29, 2011 at 3:31 PM, Fred Kiefer <fredkiefer@gmx.de> wrote:
> On 29.05.2011 21:23, Gregory Casamento wrote:
>>
>> I believe that the reason was that NSObjectController needs to point
>> to an implementation of NSManagedObjectContext since it lives in
>> AppKit, so I implemented a dummy version. This was likely before
>> GSCoreData was even started or before it was completed.
>>
>> Nevertheless I don't think NSManagedObjectContext even belongs in
>> AppKit, so there needs to be a way to reference it in
>> NSObjectController (since NSObjectController is in AppKit) without
>> putting NSManagedObjectContext there.
>
> Shouldn't a line like
> @class NSManagedObjectContext
> in the header do the trick? Or will this lead to problems with the linker
> later on? In that case we should just change the interface to use id instead
> of that class.
>
> _______________________________________________
> Discuss-gnustep mailing list
> Discuss-gnustep@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnustep
>
--
Gregory Casamento - GNUstep Lead/Principal Consultant, OLC, Inc.
yahoo/skype: greg_casamento, aol: gjcasa
(240)274-9630 (Cell)
- Core Data, Ivan Vučica, 2011/05/29
- Re: Core Data, Gregory Casamento, 2011/05/29
- Re: Core Data, Fred Kiefer, 2011/05/29
- Re: Core Data,
Gregory Casamento <=
- Re: Core Data, David Chisnall, 2011/05/29
- Re: Core Data, Gregory Casamento, 2011/05/29
Re: Core Data, Dr. H. Nikolaus Schaller, 2011/05/29