[Openmcl-devel] cocoa bridge memory management changes?

[Ron Garret]

I find myself regularly befuddled by whether or not I'm supposed to do:

(#/instanceWithFoo ...

or

(#/initWithFoo (#/alloc ...

or

(make-instance ...

Can we get some kind of official ruling on this?

rg


On Sep 24, 2010, at 10:46 AM, Raffael Cavallaro wrote:

> 
> On Sep 24, 2010, at 12:05 AM, Raffael Cavallaro wrote:
> 
>> Has the way memory management is done by the cocoa bridge changed significantly in the last week or so? I have some code that was working fine but now leaks quite a bit and I can't figure out why.
> 
> OK, this seems to be similar to a bug introduced then fixed a week or so ago related to make-instance; if I change all of my object creation to use:
> 
> (#/instanceWithSomething: ns:ns-some-class-or-other something)
> 
> instead of:
> 
> (make-instance 'ns:ns-some-class-or-other :with-something something)
> 
> then the memory leak goes away
> 
> warmest regards,
> 
> Ralph
> 
> 
> Raffael Cavallaro
> raffaelcavallaro at me.com
> 
> 
> 
> 
> 
> _______________________________________________
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
> http://clozure.com/mailman/listinfo/openmcl-devel