Lists

Open Menu Close Menu

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: Bill Bumgarner <email@hidden>
Date: Thu, 17 Apr 2008 23:47:04 -0500

On Apr 17, 2008, at 11:20 PM, Adam P Jenkins wrote:

Exactly. And now that the convention of methods returning self no longer exists, it seems like there's no longer any advantage to this behavior.

There are 10s of thousands invocations of methods on nil objects during the normal, non-error-path, execution of your average Cocoa application that indicate that this behavior is still, very much, used to the advantage (where 'advantage == convenience') of Cocoa programmers.

b.bum

_______________________________________________

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


Follow-Ups:

Re: Why is [nil aMessage] a no-op?
From: Adam P Jenkins <email@hidden>


References:  
  >Why is [nil aMessage] a no-op? (From: Adam P Jenkins <email@hidden>)
  >Re: Why is [nil aMessage] a no-op? (From: Bill Bumgarner <email@hidden>)
  >Re: Why is [nil aMessage] a no-op? (From: Adam P Jenkins <email@hidden>)




Prev by Date:
Re: Determining which sheet closed with panels in separate nibs

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

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