• 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: Proper switching and casing.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Proper switching and casing.


  • Subject: Re: Proper switching and casing.
  • From: Alex Zavatone <email@hidden>
  • Date: Thu, 09 Apr 2015 17:15:58 -0400

On Apr 9, 2015, at 5:10 PM, Sean McBride wrote:

> On Thu, 9 Apr 2015 17:05:57 -0400, Alex Zavatone said:
>
>> Sorry that I sent this before the main observation.
>>
>> Considering the implications of this, should Xcode's compiler flag these
>> "unbreak-ed case statements" with a warning?   Currently, it doesn't do that.
>
> -Wimplict-fallthrough

Could you go into a little more detail for how I add this option to the build process to generate warnings on a build?  It's the end of the day and my caffeine levels are dangerously low.

Thanks much.
_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden


References: 
 >Proper switching and casing. (From: Alex Zavatone <email@hidden>)
 >Re: Proper switching and casing. (From: Alex Zavatone <email@hidden>)
 >Re: Proper switching and casing. (From: Sean McBride <email@hidden>)

  • Prev by Date: Re: Proper switching and casing.
  • Next by Date: Re: Finder Sync extension menu limitations
  • Previous by thread: Re: Proper switching and casing.
  • Next by thread: Re: Proper switching and casing.
  • Index(es):
    • Date
    • Thread