On Thu, 24 Apr 2014 14:45:58 -0700, Quincey Morris said: >> I still don't see how >> >> foo = [@"Something" fallbackIfNil:foo]; >> >> has any advantage over >> >> foo = foo ?: @"Something"; > >I don’t see how the latter has any advantage over your earlier >suggestion [more or less]: > > if (!foo) > foo = @“Something”; > >Admittedly, it takes two lines instead of one. OTOH, as I said in >another recent thread, it seems to me that for a *reader* of the code, >the latter form is far more accessible than code with the “?…:” >operator, which tends to force the reader to figure out if the code is >correct or not.
The 'if form' is arguably better for testing too. Many code coverage tools are line-based, and with this form it's easier to see if your test cases cover going in the branch and not. Cheers, -- ____________________________________________________________ Sean McBride, B. Eng s...@rogue-research.com Rogue Research www.rogue-research.com Mac Software Developer Montréal, Québec, Canada _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
