• 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: 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: "Andy O'Meara" <email@hidden>
  • Date: Fri, 20 Jan 2006 15:48:57 -0500
  • Thread-topic: deprecated FOUR_CHAR_CODE and macintel

If you can reproduce it in a sample project (which it sounds like you can
pretty easily), you should submit this as a bug.  I believe it was Confucius
that once said, "if you don't submit an Apple bug report, it was never
said."

Andy



On 1/20/06 1:55 PM, "Lawrence Gold" <email@hidden> wrote:

> On Jan 20, 2006, at 11:40 AM, Lawrence Gold wrote:
>
>> On Jan 12, 2006, at 4:46 PM, Andy O'Meara wrote:
>>
>>> Yeah, every compiler I've ever seen, even back into the Win16 days,
>>> multi-char literals are just a convenience representation for for hex
>>> literals (left to right denotes most sig to least sig).  Lawrence,
>>> perhaps
>>> you're just misspeaking?   ( 'APPL' >> 24 ) will get you 'A' no
>>> matter if
>>> you're on MSVC, CW, gcc, or you name it.  The only exception I've
>>> ever heard
>>> of is that Borland used to have a compiler option where char
>>> literals are
>>> understood to read from least to most sig.
>>
>> Well I'll be damned, it seems to be working correctly now, at least
>> for a little test I put together. I'll have to look into this
>> further, because I swear the byte order was reversed when I first
>> look at it. It'd be really nice to get rid of the ugly macros. :-)
>
> And to follow up, it turns out there is a problem, but only for a
> special case. One of our constants is
>
> '\0\0\e\0'
>
> which ends up being stored in the wrong order. Regular constants with
> characters in all the positions work fine.
>
>
>  _______________________________________________
> 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
>
>


 _______________________________________________
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: Lawrence Gold <email@hidden>)

  • Prev by Date: Re: GCC for i386 allows 'invalid suffix "f" on integer constant'
  • Next by Date: Re: "Build succeded (2 errors)"
  • Previous by thread: Re: deprecated FOUR_CHAR_CODE and macintel
  • Next by thread: Re: deprecated FOUR_CHAR_CODE and macintel
  • Index(es):
    • Date
    • Thread