Re: Do we really need "if((self = [super init]))" in Objective-C anymore?
Well, it seems like someone was playing fast and sleazy with terms - something I often equate with Marketing departments.
While we have docs that say things like “it’s a promise that is made between these two objects” (or something to that effect), we are not shown cases where that promise is broken, so in our minds over the years of programming, a promise becomes equated with a guarantee.
While we know in the backs of our heads that promises can be broken, when we don’t see the cases where that can happen, the promise is always true from our observations.
Does that make more sense?
- Alex Zavatone