• 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: Weird compiler issue
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Weird compiler issue


  • Subject: Re: Weird compiler issue
  • From: j o a r <email@hidden>
  • Date: Tue, 15 Mar 2005 17:26:33 +0100


On 2005-03-15, at 17.17, Ian was here wrote:

Therefor, I changed it like this:

Class A: #import "ClassB.h"
Class B: @class ClassA

Class B methods used by Class A are OK, but Class A
methods used by Class B give a warning stating that
"Class A may not repond to method X".


Does anyone know how to resolve this issue?

Yes. Only include what you *really* need in the .h files - most of the time that would be just Cocoa. Use @class forward declarations for every other custom class found in the interface, and finally import the corresponding headers in your .m files.


j o a r

Attachment: smime.p7s
Description: S/MIME cryptographic signature

 _______________________________________________
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: 
 >Weird compiler issue (From: Ian was here <email@hidden>)

  • Prev by Date: Re: Weird compiler issue
  • Next by Date: Re: multidimensional arrays
  • Previous by thread: Re: Weird compiler issue
  • Next by thread: Obj-c and c++ in same file
  • Index(es):
    • Date
    • Thread