ansaurus

Question

Objective-C Class Question?

Answer 1

+7 A:

I believe that using the @class directive should solve your issue.

Using @class forward declares your class type in order that the compiler doesn't cough.

Take a look at this question on SO.

Jacob Relkin 2010-03-13 19:03:28

I would add that this is called "forward declararion"

Vladimir 2010-03-13 19:05:41

you keep typing the same thing seconds before I do :/

Brock Woolf 2010-03-13 19:08:54

@Vladimir, edited it, thanks!

Jacob Relkin 2010-03-13 19:09:01

@Brock, who? Me, or @Vladimir?

Jacob Relkin 2010-03-13 19:09:19

You Jacob. but its all good :)

Brock Woolf 2010-03-13 19:10:49

@Brock, I'm creeping up on you in rep points too lol!

Jacob Relkin 2010-03-13 19:18:36

@Jacob Lol. Yeah what a coincidence!

Brock Woolf 2010-03-13 19:52:01

I would add that it's good practice to use #import only in the implementation file and to use the @class otherwise. The exception to this is when you have to import the header for a super class. It's not a hard and fast rule but it is the habit you should get into.

TechZen 2010-03-13 20:10:44

Added the error...

tarnfeld 2010-03-13 20:30:11

@tarnfeld, can you post some more code?

Jacob Relkin 2010-03-14 08:02:20

Answer 2

+3 A:

Use @classto forward declare it as a class. This hints the compiler to know that it is a class, without having to cross include and compile the class multiple times (the reason you are getting your error). ie:

@class myClass;

The #importpreprocessor directive has protection against multiple includes, but the #include directive does not.

Brock Woolf 2010-03-13 19:05:32

ansaurus

tags:

views:

answers:

Objective-C Class Question?

related questions