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

Re: Compiler glitch


  • Subject: Re: Compiler glitch
  • From: John Mikros <email@hidden>
  • Date: Sat, 4 Mar 2006 14:38:57 -0800

Also, you may have "'char' Type Is Unsigned" checked in your build settings, in which case the warning is absolutely correct.

On Mar 4, 2006, at 2:16 PM, John Mikros wrote:

I believe this is right.

signed char x;
is not the same type as:
char x;

even though they are usually both signed, because whether "char" is signed or unsigned is compiler dependent.

I agree that the warning could be clearer, though.

-john

On Mar 4, 2006, at 10:58 AM, Jan E. Schotsman wrote:

This can't be right:

void foo( SInt8 *x );

char x;
SInt8 y;

foo( &x ); 	//	Warning: pointers differ in signedness
foo( &y );	//	No warning

Jan E.

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40blizzard.com


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: 
 >Compiler glitch (From: "Jan E. Schotsman" <email@hidden>)
 >Re: Compiler glitch (From: John Mikros <email@hidden>)

  • Prev by Date: Re: Compiler glitch
  • Next by Date: Re: Embedding frameworks across projects
  • Previous by thread: Re: Compiler glitch
  • Next by thread: Re: Compiler glitch
  • Index(es):
    • Date
    • Thread