> Mike Jackson <email@hidden> wrote:
> All this memory management code is really just
> cluttering up my source files...
> In the year and half that I have been doing Obj-C
> and C++ I have had to spend countless hours
> tracking down memory leaks...
> I want to work on my own problems not try to get
> right how to retain/release or malloc/delete.
I've written dynamic memory management into applications
for several decades, and it's always "cluttered up my
source code" and felt a bit like trying to play volleyball
in a mine-field, so I'll second what Mike wrote... except.
The problem I have with the way it is now is that it's
half-way.
The documented "guidelines" help, but there are still too
many exceptions to the exceptions, and there are dark
niches of ambiguity that should be documented with those
guidelines, along with the material on scope and the event
loop. The thoroughly consistent adoption of the function
naming convention will make things better and still give
the programmer the power to optimize. I can't, offhand,
remember the rules related to working with collections, for
instance.
In some ways, I liked working with handles (relocatable,
resizeable blocks) in 9, and doing my own reference
counting... until I discovered someone had layered on a
reference counting garbage collection scheme between "me"
and the Apple API in such a way that it was difficult to
tell which allocations and deallocations were being handled
by what and thus which dance to dance.
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
_______________________________________________
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
This email sent to email@hidden
