El 08/08/2006, a las 15:52, Mike Jackson escribió:
This is the 21rst century.. In my little utopian world memory
management is a solved problem. I want to work on my own problems
not try to get right how to retain/release or malloc/delete.
I am very comfortable with Objective-C's current retain/release model
and I tend not to have too many problems crop up, BUT if garbage
collection can make my job even easier (and my code clearer) then
I'll embrace it whole-heartedly. Even if there is a slight
performance penalty (and I doubt there will be, it may even be
faster) it's probably worth it because if it enables you to write
code faster you can spend more time coming up with efficient designs
and optimizing away performance problems.
I will be watching this development with interest to see how Apple's
garbage collection implementation impacts on legacy code, legacy code
which may use a blend of manual memory management (alloc/init/
release), autorelease pools, and explicit retain/releases. Just think
about the number of retain/releases in a typical accessor...
In other words, will this be a thing for new code only, or will it be
something that can be applied to existing code without too many
changes? I think this will be very interesting to watch.
Greg
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xcode-users/email@hidden
