While that's always an option, it's not exactly the answer I was
hoping to hear :D
The good news is I was able to recreate the file in a considerably
smaller scale and have uploaded the source here: http://junk.isnot.tv/test.zip
As you can see, i've got two classes which include each others headers
(since they need to call each others methods directly)
I may be breaking some design patterns by doing this, and if so,
please point them out - cause they could be the cause of the problem :D
There's obviously something basic i'm doing wrong, otherwise we'd be
hearing about this issue all the time.
Cheers
On 22/02/2009, at 11:59 AM, David Blanton wrote:
don't use 'em as I am on Tiger but deploy to both
On Feb 21, 2009, at 5:43 PM, Aaron Wallis wrote:
If you've used @class, how have you overcome the errors caused by
the objc2 property style?
On 22/02/2009, at 11:20 AM, David Blanton wrote:
I have fought this as well with the only solution being the
@class as you describe.
I don not believe #import works properly.
Just my 2 cents.
On Feb 21, 2009, at 4:27 PM, Aaron Wallis wrote:
Hi all,
I'm working on a project which is much larger than what i'm used
to, and i've come up to a bit of a brick wall.
When I compile my application, I start getting build errors
caused by recursive imports.
I'm sure there's an easy way to get around it, but it currently
alludes me.
Here's a screen shot of my error:
http://www.quicksnapper.com/d2kagw/image/untitled-0011
if I remove the #import "TMPSTManagedFile.h" from the header of
the class and change it to @class TMPSTManagedFile the error goes
away, and the application *would* run fine, if I didn't start
getting errors caused from the ObjC 2.0 style property accessors
like:
TMPSTManagedFile *tFile = [blah blah];
NSLog(@"%@", tFile.name);
In which case I start getting errors like:
Error: request for member 'name' in something not a structure or
union
Any ideas?
Cheers
Aaron.
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please 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:
http://lists.apple.com/mailman/options/cocoa-dev/airedale%40tularosa.net
This email sent to aired...@tularosa.net
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please 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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
