• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: cross inclusion with fully qualified types in interface
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: cross inclusion with fully qualified types in interface


  • Subject: Re: cross inclusion with fully qualified types in interface
  • From: mmalcolm crawford <email@hidden>
  • Date: Wed, 5 Apr 2006 19:39:28 -0700


On Apr 5, 2006, at 7:29 PM, Greg Hoover wrote:

It is my understanding the #import prevents multiple inclusion, however I have run into the following situation that I have been unable to discern. Given two cocoa objects with header files:
// File a.h
#import "b.h"
@interface a : NSObject {
b *foo;
}
@end
// File b.h
#import "a.h"

Use @class instead of importing in the header:
<http://developer.apple.com/documentation/Cocoa/Conceptual/ ObjectiveC/Articles/chapter_4_section_5.html>
"Referring to Other Classes"


mmalc

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >cross inclusion with fully qualified types in interface (From: Greg Hoover <email@hidden>)

  • Prev by Date: cross inclusion with fully qualified types in interface
  • Next by Date: NSTreeController, NSOutlineView + Core Data
  • Previous by thread: cross inclusion with fully qualified types in interface
  • Next by thread: NSTreeController, NSOutlineView + Core Data
  • Index(es):
    • Date
    • Thread