Re: XCode 2.0 warning with @class?
Re: XCode 2.0 warning with @class?
- Subject: Re: XCode 2.0 warning with @class?
- From: Marc Respass <email@hidden>
- Date: Wed, 28 Sep 2005 17:32:41 -0400
On Sep 28, 2005, at 5:22 PM, Piers Uso Walter wrote:
On 28.09.2005, at 16:45, Marc Respass wrote:
So what's the deal with @class then? In the past, I have used it
and not gotten that error.
@class comes in handy in header files when you want to declare
instance variables of a certain class without importing the header
file of this class.
Importing as little as possible into a header file is desirable
because this helps reduce compiler dependencies. (A change in the
imported class header would not only force a recompile of the
importing header file, but also of all other files that import the
importing header file).
Importing a class header into an implementation file, as in your
case, is perfectly fine because it does not cause such a multi-
level compiler dependency issue.
Thanks Piers. That's exactly what I thought. I just don't like the
warning I'm getting
Controller.m:29: warning: `PersonNameOnlyTransformer' may not respond
to `+alloc'
But it sounds like I either import the header or live with the warning.
Marc
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden