On Feb 22, 2009, at 2:12 AM, Aaron Wallis wrote:
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
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.
That error isn't caused by recursive includes (which are solved with
#import anyway). That error means you defined an objective-c method
and it's not in between an @implementation and @end - more than likely
this definition occurs in TMPSTManagedFile.h.
Luke
On Feb 21, 2009, at 3:27 PM,
Yeah, I had a look at that already, it's definitely in the right spot:
http://www.quicksnapper.com/d2kagw/image/untitled-0012
Interestingly enough, if I comment out the entry from the header file,
I don't get the error?
http://www.quicksnapper.com/d2kagw/image/untitled-0012
Aaron
On
On 22/02/2009, at 10:27 AM, Aaron Wallis wrote:
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
Yeah, the header file is being imported in the .m file
I tried moving the static out of the implementation, but I still get
the errors...
strange one 'eh
On 22/02/2009, at 11:11 AM, Kiel Gillard wrote:
On 22/02/2009, at 10:27 AM, Aaron Wallis wrote:
if I remove the #import
On Sat, Feb 21, 2009 at 7:11 PM, Kiel Gillard kiel.gill...@gmail.com wrote:
Towards the start of TMPSTLocalStore.m, you're declaring a static pointer
within the @implementation. I didn't think you could do this, I thought you
could only declare a static variable outside of the @implementation
I think i've found a work around, I altered the method to accept 'id'
instead of 'TMPSTManagedFile' like so:
-(NSString *)saveFileToStore:(id)tFile forDate:(NSDate *)tDate;
I no longer get the error, but it's not an ideal compromise in the
long run...
If anyone has any other suggestions,
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
On Feb 21, 2009, at 17:12, Aaron Wallis wrote:
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
On Feb 21, 2009, at 17:36, Quincey Morris wrote:
Nothing wrong, just failing to use @class for its intended purpose. :)
#import Cocoa/Cocoa.h
@class ControllerB;
@interface ControllerA : NSObject {
ControllerB *myController;
NSArray *fruit;
}
@property (readonly,
Awesome!
Thanks Aaron!
For everyone else, the .h file should contain @class ControllerB and
the .m file imports ControllerB
for the record
On 22/02/2009, at 12:21 PM, Aaron Tuller wrote:
check it...no warnings.
-aaron
At 12:12 PM +1100 2/22/09, Aaron Wallis wrote:
While that's always an
12 matches
Mail list logo
