• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: GC pros and cons
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GC pros and cons


  • Subject: Re: GC pros and cons
  • From: WT <email@hidden>
  • Date: Sat, 27 Jun 2009 03:37:35 +0200

On Jun 27, 2009, at 3:30 AM, Andy Lee wrote:

On Friday, June 26, 2009, at 09:20PM, "WT" <email@hidden> wrote:
It seems
to me that micro-managing memory can get out-of-hand rather easily on
large projects. By adopting a GC approach, I'd be relinquishing some
control, yes, but I'd be gaining the peace of mind of not having to
debug a potential monster.

Actually the pre-GC way (retain-release) boils down to some simple rules that don't seem like micro-management at all to most Cocoa developers who have internalized them. It's true things can get hairy, but not as often as you might think.

I was referring specifically to complex retain cycles in a large object graph.


you do whatever floats your boat. I'll do what floats mine.

I think my boat sunk, 'cause I was using integers rather than floats.

No, no, it was the memory leaks!

Or a buffer overflow, perhaps ?

_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:
This email sent to email@hidden


References: 
 >Re: GC pros and cons (From: Andy Lee <email@hidden>)

  • Prev by Date: Re: GC pros and cons
  • Next by Date: Re: GC pros and cons
  • Previous by thread: Re: GC pros and cons
  • Next by thread: Re: GC pros and cons
  • Index(es):
    • Date
    • Thread