Would be like a cookbook including instructions on how to operate an
oven and use a knife to cut vegetables in every single recipe. I
think most would find that pretty redundant and diluting, especially
when the preface covers these topics in detail.
On May 21, 2008, at 8:37 PM, Jens Alfke wrote:
On 21 May '08, at 11:35 AM, Johnny Lundy wrote:
See? Not a word about autoreleasing anything, or having to retain
the returned array. Nada.
It also didn't spell out that:
the return value is a pointer,
pointers are 4 or 8 bytes large,
the pointer value zero is special and is named "nil",
messaging nil is a no-op,
you can assign a pointer variable to another variable of the same
type,
the type "id" is a generic object pointer type,
the character "*" is suffixed to a type to denote a pointer to that
type,
...
Those are all generic behaviors, and they are well documented in the
core reference and tutorial materials. Complaining because you
turned to a random method in the reference and all of those generic
behaviors were not described *right there in that one place where
your eyes happened to fall*, of all the thousands of methods in the
API that they apply to, is kind of, well, 'egotistical' is the
kindest word I can think of.
I see you repeating the above argument over and over. You might want
to try a different argument that actually makes sense, because this
one isn't winning you any fans.
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
