Don't shoot me, I know it must have been asked a thousand times ...
I don't like the lack of good documentation in Objective-C's memory. I understand alloc, dealloc, save, release and all this, but there is confusion in my head.
Is it just lazy programming or is Objective-C doing some backstage automatic activity regarding memory allocation?
Based on background C (centuries ago), I know that pointers are just pointers ... you also need to reserve a place to point to a pointer, or you will start stomping on your own program and other variables.
The code samples that I find (and which are in the books I read - all of which are sadly outdated with the current version of Xcode and Interface Builder) never allocate storage space for some objects, such as NSString. They declare a pointer (for example, NSString * aString;), and then begin to assign text to the line. No memory allocation for the string is called!?!? So, all these examples are just lazy code looking for a place to crash?
In addition, books talk about declaring pool memory and that it is automatically inserted into your code. When I create projects, classes and objects, such code is not found anywhere. Is Apple done with this auto-insertion, or is it something that happens at compile time?
Is there a penultimate guide or website that will explain all this once and for all?