On 27/06/2009, at 8:58 PM, WT wrote:
I don't think they are hard to understand, or even apply, at all. I
just extrapolated - and, admittedly, did so without having the
benefit of experience - that on very large problems, they would
almost always cause a maintenance nightmare. Your 500+-class,
millions-of-lines project shows that I was wrong in making that
assumption. Not the first time that I make a fool of myself in
public. :)
Not at all.
I'm not saying using retain/release doesn't require care - it does.
Probably more so than GC. My point is that a bad design is a bad
design (and we all make them - I just spent a day rewriting some stuff
I threw together a few months ago that sucks so hard it was just as
well it was in my private stuff and not on my public washing-line!)
and using GC to help cover up the effects of a bad design (e.g. retain
cycles, which arise because ownership wasn't clearly established by
the design) is not a good thing. GC can't turn a bad design into a
good one - but I do have a suspicion that it sometimes gets used that
way.
Just my 2ยข worth, and I'm sure that's all it's worth... ;-)
--Graham
_______________________________________________
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 arch...@mail-archive.com
