• 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: Avoiding == and = mixup in if statements
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Avoiding == and = mixup in if statements


  • Subject: Re: Avoiding == and = mixup in if statements
  • From: Wade Tregaskis <email@hidden>
  • Date: Fri, 21 May 2004 13:29:50 +1000

Java disallows stuff like

if (myObject=nil) { dosomething }

Is it possible to maybe disallow the same potential error when I'm
writing obj-c programs? Could I do something with the pre-processor
perhaps?

You can display warnings for this by using the flag "-Wparentheses". This will require you to add an extra set of parentheses to avoid the warning, indicating you really do want to perform the assignment. You can convert this to an error using "-Werror", although that will convert all warnings of any sort into errors.

Wade Tregaskis (aim: wadetregaskis)
-- Sed quis custodiet ipsos custodes?
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.


References: 
 >Avoiding == and = mixup in if statements (From: Christoffer Lerno <email@hidden>)

  • Prev by Date: build styles override target settings (was: does not execute on launch)
  • Next by Date: Re: NSMakePoint and such - what about memory allocation?
  • Previous by thread: Re: Avoiding == and = mixup in if statements
  • Next by thread: Re: Avoiding == and = mixup in if statements
  • Index(es):
    • Date
    • Thread