Re: Cocoa and messages to nil, revisited
Re: Cocoa and messages to nil, revisited
- Subject: Re: Cocoa and messages to nil, revisited
- From: "Raphael Sebbe" <email@hidden>
- Date: Thu, 9 Aug 2007 14:02:27 +0200
Well, nil receivers lead to nil return values, which themselves lead to nil
arguments. arguments can be tested with asserts, where relevant. Contrarily
to your approach, where every message to nil would be logged...
And I guess the main idea is not to write complicated code, but to write
simple code instead.
Raphael
On 8/9/07, Jeff Laing <email@hidden> wrote:
>
> > passing nil arguments may be completely valid, depending on
> > your methods.
>
> Oh ye gods and little fish, did I say nil arguments were invalid?
>
> Its nil *receivers* that are the problem I'm trying to catch.
>
> Sorry about that but sometimes it seems like everyone deliberately tries
> to
> miss the point - I wonder some times how people manage to actually write
> complicated code...
>
_______________________________________________
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