FROM : Sherm Pendley
DATE : Mon Mar 24 05:44:26 2008
On Mon, Mar 24, 2008 at 12:16 AM, Jack Repenning <<email_removed>>
wrote:
>
> The main thing you'll have to watch for: Objective-C 2.0 has garbage
> collection available, like Java and scripting languages you're
> familiar with, but it's off by default, and earlier Macs don't have
> it. You'll probably have to learn the old way, "retain and release,"
> which is unique to Objective-C.
... and which, IMHO, isn't *that* big a deal. The guidelines are simple, and
you can implement them up in a half-dozen lines in each setter method. So
long as you do that, and consistently use those setter methods instead of
directly assigning to instance variables, then you've taken care of 99% of
your so-called "manual" memory management. And, if you use something like
Accessorizer, or Xcode's built-in scripts, to automagically create your
accessor methods for you, then you've gotten that far without having to
write a single line of MM-related code.
sherm--
DATE : Mon Mar 24 05:44:26 2008
On Mon, Mar 24, 2008 at 12:16 AM, Jack Repenning <<email_removed>>
wrote:
>
> The main thing you'll have to watch for: Objective-C 2.0 has garbage
> collection available, like Java and scripting languages you're
> familiar with, but it's off by default, and earlier Macs don't have
> it. You'll probably have to learn the old way, "retain and release,"
> which is unique to Objective-C.
... and which, IMHO, isn't *that* big a deal. The guidelines are simple, and
you can implement them up in a half-dozen lines in each setter method. So
long as you do that, and consistently use those setter methods instead of
directly assigning to instance variables, then you've taken care of 99% of
your so-called "manual" memory management. And, if you use something like
Accessorizer, or Xcode's built-in scripts, to automagically create your
accessor methods for you, then you've gotten that far without having to
write a single line of MM-related code.
sherm--






Cocoa mail archive

