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

Re: compiler bug??


  • Subject: Re: compiler bug??
  • From: Cameron Hayne <email@hidden>
  • Date: Thu, 8 Sep 2005 14:08:26 -0400

Chris Espinosa wrote:


This implies that there is some client of the public interface of class
that isn't getting recompiled and re-linked when you change the class'
formal definition. It's then using invalid offsets into the class at
runtime, and "all hell" would indeed break loose.



On 8-Sep-05, at 11:07 AM, Philip Lukidis wrote:


I've done that. And if that were the case (assuming I understand your
point), moving the member to another location after the issue has occurred
would not "solve" the issue.



Moving the member to a different location would mean that only access to those member variables after that location would be affected. I.e. the offsets of earlier member variables would not be affected by the presence of the ifdef'd variable.
Thus your experience is still consistent with Chris' theory. Check again that all clients of the class are getting recompiled with the correct #define's.


--
Cameron Hayne
email@hidden



_______________________________________________
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


References: 
 >RE: compiler bug?? (From: Philip Lukidis <email@hidden>)

  • Prev by Date: Re: Xcode UI questions
  • Next by Date: Re: XCode Rules!
  • Previous by thread: RE: compiler bug??
  • Next by thread: Re: compiler bug??
  • Index(es):
    • Date
    • Thread