It is to my understanding that one should use a forward-class declaration in the event ClassA needs to include a ClassB header, and ClassB needs to include a ClassA header to avoid any circular inclusions. I also understand that an #import is a simple ifndef so that an include only happens once.
My inquiry is this: When does one use #import and when does one use @class? Sometimes if I use a @class declaration, I see a common compiler warning such as the following:
warning: receiver 'FooController' is a forward class and corresponding @interface may not exist.
Would really love to understand this, versus just removing the @class forward-declaration and throwing an #import in to silence the warnings the compiler is giving me.
Anonymous User
02-Sep-2015If you see this warning:
warning: receiver 'myCoolClass' is a forward class and corresponding @interface may not exist
you need to #import the file, but you can do that in your implementation file (.m), and use the @class declaration in your header file.
@class does not (usually) remove the need to #import files, it just moves the requirement down closer to where the information is useful.
For Example
If you say @class myCoolClass, the compiler knows that it may see something like:
myCoolClass *myObject;
It doesn't have to worry about anything other than myCoolClass is a valid class, and it should reserve room for a pointer to it (really, just a pointer). Thus, in your header, @class suffices 90% of the time.
However, if you ever need to create or access myObject's members, you'll need to let the compiler know what those methods are. At this point (presumably in your implementation file), you'll need to #import "myCoolClass.h", to tell the compiler additional information beyond just "this is a class".