• 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 Flags for Code Porting
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: compiler Flags for Code Porting


  • Subject: Re: compiler Flags for Code Porting
  • From: Greg Guerin <email@hidden>
  • Date: Sat, 04 Jun 2011 10:55:38 -0700

koko wrote:

I went ahead and did:

if ((__uint32_t)m_handle != INVALID_HANDLE_VALUE)

which sees OK. Any comments?


I don't think it's 64-bit compatible. If the code is ever compiled as 64-bit, it may not do the right thing.

You may not care about 64-bitness now, but neglecting compatibility is kinda why the current code has a problem, so you're just replacing one kind of compatibility problem with a different one.

  -- GG
_______________________________________________
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: compiler Flags for Code Porting
      • From: koko <email@hidden>
  • Prev by Date: Re: Methods with the same name but different return types
  • Next by Date: Re: compiler Flags for Code Porting
  • Previous by thread: Re: compiler Flags for Code Porting
  • Next by thread: Re: compiler Flags for Code Porting
  • Index(es):
    • Date
    • Thread