Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Re: deprecated FOUR_CHAR_CODE and macintel

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: deprecated FOUR_CHAR_CODE and macintel

Subject: Re: deprecated FOUR_CHAR_CODE and macintel
From: Markus Hitter <email@hidden>
Date: Fri, 20 Jan 2006 23:23:36 +0100


Am 20.01.2006 um 20:35 schrieb Howard Rodstein:

So the question is, how can one use two-, three- and four-character codes on Mac and Windows without getting warnings or wrong byte order?

You can't, because on Intel, 'APPL' compares with a different order than "APPL". (Nobody ever claimed i386 would be an elegant architecture, right?)

So, to get it right, make sure to always compare Intel bits against Intel bits and PPC bits against PPC bits. Adjust your codes where you pass them externally (file, pipe, stream, whatever). See htonl(3) etc.


Markus

- - - - - - - - - - - - - - - - - - -
Dipl. Ing. Markus Hitter
http://www.jump-ing.de/


_______________________________________________
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: deprecated FOUR_CHAR_CODE and macintel (From: Howard Rodstein <email@hidden>)




Prev by Date:
Re: GCC for i386 allows 'invalid suffix "f" on integer constant'

Next by Date:
Re: GCC for i386 allows 'invalid suffix "f" on integer constant'

Previous by thread:
Re: deprecated FOUR_CHAR_CODE and macintel

Next by thread:
__builtin_constant_p fails for Intel compilation?

Index(es):

Date
Thread