On Apr 30, 2015, at 11:13 PM, [email protected] wrote:

> The right thing to do is move your header import to the .m file as well as 
> your ivar

Simply moving the #import from the .h file into the .m file resolved this error 
and allowed the app to build.


Can anyone tell me why?









> You can use 
> @class SomeClassName; 
> Before the @interface in your .h to do a forward decl of an Objective-C 
> class, if you need to have an ivar or property of SomeClassName in your .h 
> file. 
> 
> If you have a lot of stuff, make a framework. Add target framework to the 
> project. It will auto setup to link to it and embed it. 
> (Xcode 6 and for iOS 8+)
> Then you can import the framework in your .h and everything gets more 
> magical. 
> 
> Sent from my iPhone
> 
> On 2015/05/01, at 11:37, Quincey Morris <[email protected]> 
> wrote:
> 
>> On Apr 30, 2015, at 18:44 , William Squires <[email protected]> wrote:
>>> 
>>> * The compiler then sees that B.h #imports "A.h", but realizes that A.h is 
>>> already in use, and skips it.
>> 
>> Indeed, but the gotcha is that only the portion of A.h up till #import “B.h” 
>> has been processed. (Because this is C, lexical analysis is linear and 
>> textual, so it would have been illegal to proceed further in A.h until after 
>> B.h has been processed.) Thus, although the author of B.h might have been 
>> intending to have all of A.h available at this point, the circularity 
>> partially violates the intention. This is presumably what happened to Alex.
>> 
>> One solution is to use forward references rather than circular definitions.
>> 
>> Another is to put the #import “B.h” at the end of A.h instead of earlier. 
>> That way, when the rest of A.h gets skipped, nothing important is missed.
>> 
>> The correct choice of solutions depends on what else is being defined in the 
>> two header files. There’s no boilerplate solution.
>> 
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Xcode-users mailing list      ([email protected])
>> Help/Unsubscribe/Update your Subscription:
>> https://lists.apple.com/mailman/options/xcode-users/dangerwillrobinsondanger%40gmail.com
>> 
>> This email sent to [email protected]
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Xcode-users mailing list      ([email protected])
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/xcode-users/zav%40mac.com
> 
> This email sent to [email protected]

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to