On 27 May 2008, at 21:24, Adam R. Maxwell wrote:
In general, I think you're supposed to add NSError** parameters to
pass it back up to some class that knows how to present an error,
but I find that's not always practical, and it tends to be messy.
In such cases I typically take the easy
On Tuesday, May 27, 2008, at 12:40PM, "Paul Sargent" <[EMAIL PROTECTED]> wrote:
>My question is what is accepted practice when I get an NSError back?
>Reading the Error Handling Programming Guide I get the idea that
>errors can be passed up the responder chain so that the user can be
>aler
Hi,
I'm writing a model class that uses (in order to access on on disk
database) NSFileManager to read directory contents, and so I'm using
the method:
- (NSArray *)contentsOfDirectoryAtPath:(NSString *)path error:(NSError
**)error
(directoryContentsAtPath is depreciated in 10.5, and th
