• 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: Casting anonymous Objects leads to different values on getter functions (while getting no warnings at compile time)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Casting anonymous Objects leads to different values on getter functions (while getting no warnings at compile time)


  • Subject: Re: Casting anonymous Objects leads to different values on getter functions (while getting no warnings at compile time)
  • From: Pontus Ilbring <email@hidden>
  • Date: Tue, 8 Nov 2005 21:19:29 +0100

On 11/8/05, Martin Wilz <email@hidden> wrote:
> Concerning the warning issue, I was not able to locate a switch in the
> preferences to enable these in XCode 2.1. I also opened the project on
> an freshly installed version, so the switch (if it exists) is  off by
> default or already encoded into the project that was also created
> without touching the project preferences.

I remember older versions of gcc warning, and as I suspected, if you
compile your project with gcc 4.0 then you won't get any warnings, but
if you use gcc 3.3 or 3.1 then you will. A clear regression.

I haven't found any useful warning flags in the gcc documentation
either. There's Wselector, but it is a bit overzealous.
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >Casting anonymous Objects leads to different values on getter functions (while getting no warnings at compile time) (From: Martin Wilz <email@hidden>)
 >Re: Casting anonymous Objects leads to different values on getter functions (while getting no warnings at compile time) (From: Hauke Klein <email@hidden>)
 >Re: Casting anonymous Objects leads to different values on getter functions (while getting no warnings at compile time) (From: Martin Wilz <email@hidden>)

  • Prev by Date: Re: NSButton with a delayed popup-menu?
  • Next by Date: Understanding [NSTextview setInsertionPointColor:]
  • Previous by thread: Re: Casting anonymous Objects leads to different values on getter functions (while getting no warnings at compile time)
  • Next by thread: Re: Casting anonymous Objects leads to different values on getter functions (while getting no warnings at compile time)
  • Index(es):
    • Date
    • Thread