• 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: [For what it's worth
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [For what it's worth


  • Subject: Re: [For what it's worth
  • From: Bill Royds <email@hidden>
  • Date: Sat, 26 Jan 2008 11:41:39 -0500


On 26-Jan-08, at 24:47 , Charlie Dickman wrote:

In moving projects from Xcode 2 on Tiger (G4) to Xcode 3 on Leopard (Intel) I have found two cases of code (Objective C) that breaks in Xcode 3 on Leopard (Intel) that works perfectly fine in Xcode 2 on Tiger (G4)...

unsigned u = '\1\0\0\0';
u >>= 8;

results in u equal to '\0\1\0\0' in Xcode 2 on Tiger (G4) but results in '\1\1\0\0' in Xcode 3 on Leopard (Intel).


Both are correct. G4 is a big-endian computer and Intel is a little- Endian. You have the result required by the C standard for both. Shifts are architecture dependent.


Bill Royds



_______________________________________________
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


  • Follow-Ups:
    • Re: [For what it's worth
      • From: "Clark Cox" <email@hidden>
References: 
 >For what it's worth (From: Charlie Dickman <email@hidden>)

  • Prev by Date: Re: Boost Thread Linking error in Xcode 3.0 on OS X 10.5
  • Next by Date: Re: Regex Documentation in Xcode 3.0 ?
  • Previous by thread: Re: For what it's worth
  • Next by thread: Re: [For what it's worth
  • Index(es):
    • Date
    • Thread