Re: Garbage collected and non-garbage collected
Re: Garbage collected and non-garbage collected
- Subject: Re: Garbage collected and non-garbage collected
- From: Bill Bumgarner <email@hidden>
- Date: Tue, 10 Mar 2009 12:56:44 -0700
On Mar 10, 2009, at 12:21 PM, I. Savant wrote:
On Tue, Mar 10, 2009 at 3:07 PM, Robert Mullen <email@hidden>
wrote:
I also have the option of abandoning the framework and functionality
although that is not an appealing option. I am enjoying the process
of
determining the course to rectify GC in this framework (in a
perverse sort
of way) but I am not sure how long that will last. Every time I run
into a
persistent problem it is an opportunity to learn Cocoa, X-Code, and
Objective-C a little better and that is fun in a challenging way. I
know
from experience though that this can turn from an enjoyably
challenging
diversion into a frustratingly endless cycle of refactoring. Wish
me luck...
Luck!
Consider also, though, that learning the Retain / Release memory
management approach is just as much an opportunity to learn. For your
project, it sounds like the odds tip in favor of getting everything
GC-compliant, but as you said, time and (bad) experience may change
that view ... ;-)
So... is the framework open source? Got a pointer? Any kind of test
case? Can you post more information about the crash? What does the
stack trace look like? Got an address? What does malloc_history
say? Can..? Got..? Have you tried..?
Let's pull this post back to a technical analysis of the OP's
problem. More likely than not, we can fix his framework and,
hopefully, that'll be one less barrier to entry for everyone.
b.bum
_______________________________________________
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