Re: Convention for init with error

2013-02-27 Thread Brad O'Hearne
Quincey and John, Thank you both for the replies and opinions. I do like the factory method approach, however there is something about a mandatory process or workflow for using an object that seems like it should naturally be put in an init method. It sometimes strikes me a little weird when I

Re: Convention for init with error

2013-02-27 Thread Quincey Morris
On Feb 27, 2013, at 13:12 , Brad O'Hearne wrote: > - (id)init:(NSError **)error; > { >self = [super init]; > >if (self) >{ >if ([self operationThatMightFail:error]) >{ >*error = nil; >} >else >{ >return nil; >} >

Re: Convention for init with error

2013-02-27 Thread John McCall
On Feb 27, 2013, at 1:12 PM, Brad O'Hearne wrote: > I have a need to construct an object with the possibility of an error taking > place and needing to return that error. While it would be nice to have a > clean init method that returned no errors, in this particular case, the error > belongs w