Laurent Sansonetti
lsans****@apple*****
Sat Jan 6 02:20:35 JST 2007
On Jan 5, 2007, at 1:29 AM, jeanp****@gmail***** wrote: > RubyCocoa maintains the Objective-C objects for you. > > However it shouldn't segfault, IIRC on the stable branch retain/ > release/autorelease messages were simply ignored, we should do the > same there. > > very interesting, i wasn't sure how rubycocoa would handle memory > management. so ObjC code should still carry on as per usual retain/ > release/autorelease but when instrumenting from rubycocoa, one does > not need to be concerned with it? Yep, RubyCocoa will take care of this for you. You can create objects using both the traditional alloc/init way or get autoreleased objects, and use them without having to retain/release them. > does it just use an autorelease pool or some sort of ruby garbage > collection? The objects are guarded by the Ruby garbage collector. Laurent
