• 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: GCC 4.0 GetKeys() and BigEndianLong for Intel
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GCC 4.0 GetKeys() and BigEndianLong for Intel


  • Subject: Re: GCC 4.0 GetKeys() and BigEndianLong for Intel
  • From: Jonas Maebe <email@hidden>
  • Date: Thu, 16 Jun 2005 11:09:30 +0200


On 16 jun 2005, at 10:48, MacArthur, Ian (SELEX) (UK) wrote:

I guess it's way to late to get it changed now, but that strikes me as exactly the sort of thing that will be a pain.
There's no real reason *why* it has to be a struct rather than just a long

Well, it prevents you from forgetting to put byteswapping code in place. My guess is that it will save a lot more time in the long run than that it will cost.



Jonas _______________________________________________ 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: 
 >GCC 4.0 GetKeys() and BigEndianLong for Intel (From: "MacArthur, Ian (SELEX) (UK)" <email@hidden>)

  • Prev by Date: GCC 4.0 GetKeys() and BigEndianLong for Intel
  • Next by Date: Re: CopyCStringToPascal
  • Previous by thread: GCC 4.0 GetKeys() and BigEndianLong for Intel
  • Next by thread: Re: GCC 4.0 GetKeys() and BigEndianLong for Intel
  • Index(es):
    • Date
    • Thread