Lists

Open Menu Close Menu

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

Re: Checking for nil-return

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

Re: Checking for nil-return

Subject: Re: Checking for nil-return
From: Remco Poelstra <email@hidden>
Date: Tue, 05 Oct 2010 16:27:37 +0200

Op 5-10-2010 16:23, Matt Gough schreef:


On 5 Oct 2010, at 15:18:06, Remco Poelstra wrote:

Op 5-10-2010 16:11, Dave DeLong schreef:

Then you have much bigger problems.


I already thought so :). But I noticed that [NSArray arrayWithCapacity] also never returns nil. But I can create a very large array, and I can make it bigger with addObjects:atIndexes: and that function returns void, so always succeeds. How is that possible?


Because it throws exceptions if anything bad happens at runtime (i.e out of memory, invalid parameters etc)

Google for NSException


Ah, I see. I thought exceptions were meant for programming errors.
This definitely helps in make sure my code behaves nice.

Regards,

Remco Poelstra
_______________________________________________

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:  
  >Checking for nil-return (From: Remco Poelstra <email@hidden>)
  >Re: Checking for nil-return (From: Dave DeLong <email@hidden>)
  >Re: Checking for nil-return (From: Remco Poelstra <email@hidden>)
  >Re: Checking for nil-return (From: Matt Gough <email@hidden>)




Prev by Date:
Re: Checking for nil-return

Next by Date:
Re: How to get selected text in a WebView

Previous by thread:
Re: Checking for nil-return

Next by thread:
Re: Checking for nil-return

Index(es):

Date
Thread