The below is an off-site archive of all tweets posted by @mjtsai ever

November 27th, 2009

@bbum How about both? Because it's easy to always initialize errors but harder to remember to check all receivers.

via Twitter for iPhone in reply to bbum

@bbum Setting the error to nil is good because that way you avoid a crash if the method returned nil because of an unexpectedly nil receiver

via Twitter for iPhone in reply to bbum