• 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: == nil vs. isEqual:nil
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: == nil vs. isEqual:nil

  • Subject: Re: == nil vs. isEqual:nil
  • From: Luc Heinrich <email@hidden>
  • Date: Thu, 16 Aug 2001 21:33:09 +0200
On Thursday, August 16, 2001, at 07:49 , Jonathan Hendry wrote:

On the other hand, if you accidentally type "if (anObject = nil)" then
you get no compiler warning and anObject gets set to nil.

Not true. Some (good) compilers *do* issue a 'possible unwanted assignment' warning in this kind of situation. Metrowerks CodeWarrior does, for example, and GCC does not, as another example.

Take your conclusions... :-)

--
Luc - email@hidden

  • Follow-Ups:
    • Re: == nil vs. isEqual:nil
      • From: Luc Heinrich <email@hidden>
References: 
 >Re: == nil vs. isEqual:nil (From: Jonathan Hendry <email@hidden>)

  • Prev by Date: Re: Interleaved (interwoven) raw images
  • Next by Date: Re: Category vs Subclass
  • Previous by thread: Re: == nil vs. isEqual:nil
  • Next by thread: Re: == nil vs. isEqual:nil
  • Index(es):
    • Date
    • Thread