• 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: Incorrect warning
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Incorrect warning


  • Subject: Re: Incorrect warning
  • From: Steve Mills <email@hidden>
  • Date: Mon, 15 Nov 2004 14:22:05 -0600

On Nov 15, 2004, at 13:23, Chris Espinosa <email@hidden> wrote:

Because a) DescType is defined as unsigned; b) your enum is implicitly
signed; and c) your enumerators are all negative.  They can never be
equal to an unsigned (i.e. always positive) value.

The warning message makes it sound worse than it really is. The actual compiled machine instruction; does it really care about signed/unsigned when doing equality comparisons on 4-byte integers? I don't see why it would when it should just be comparing all 32 bits.


Is there a way I've forgotten about or just aren't familiar with to make all the constants in an enum {} be unsigned? They're all defined as 4-char codes, which I thought were naturally unsigned to begin with.

Steve Mills
Drummer, Mac geek
http://sjmills5.home.mchsi.com/

_______________________________________________
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: Incorrect warning
      • From: Chris Espinosa <email@hidden>
    • Re: Incorrect warning
      • From: Markian Hlynka <email@hidden>
  • Prev by Date: Re: How do I set OTHER_CFLAGS to -DCONFIGDIR=\"/gnome_wave_cleaner/config/\"?
  • Next by Date: FYI - AppKiDo
  • Previous by thread: Re: Incorrect warning
  • Next by thread: Re: Incorrect warning
  • Index(es):
    • Date
    • Thread