Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Re: Why is [nil aMessage] a no-op?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Why is [nil aMessage] a no-op?

Subject: Re: Why is [nil aMessage] a no-op?
From: Andy Lee <email@hidden>
Date: Fri, 18 Apr 2008 11:18:20 -0400

This has been a great thread.

I wonder whether nil-eats-message makes me *more* sensitive to cases where nil really matters, because it frees me from having to clutter my code with trivial cases where nil doesn't matter. But I might be trying to rationalize a subjective preference.

I also wonder if programmers who have done a lot of SQL are less freaked out by nil-eats-message, given the way NULL behaves in databases.

--Andy

_______________________________________________

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:  
  >Re: Why is [nil aMessage] a no-op? (From: Scott Ribe <email@hidden>)




Prev by Date:
Re: Authenticatiion tool

Next by Date:
setTextContainerInset with different values for left and right

Previous by thread:
Re: Why is [nil aMessage] a no-op?

Next by thread:
Re: Why is [nil aMessage] a no-op?

Index(es):

Date
Thread