Re: [Pharo-users] UFFI and autoRelease

On 26 April 2018 at 18:09, Serge Stinckwich wrote: > > You don't reply to my original question, Ben :-) I didn't know the answer :P and I wasn't near an Image where I could poke around and speculate. Having a poke around now, but my thoughts are speculative - the few times I've used FFI I've mudd

Re: [Pharo-users] UFFI and autoRelease

> On 26 Apr 2018, at 12:09, Serge Stinckwich wrote: > > > > On Wed, Apr 25, 2018 at 11:07 PM, Ben Coman > wrote: > > > On 25 April 2018 at 23:08, Serge Stinckwich > wrote: > I don't understand the default > > finalizeResour

Re: [Pharo-users] UFFI and autoRelease

On Wed, Apr 25, 2018 at 11:07 PM, Ben Coman wrote: > > > On 25 April 2018 at 23:08, Serge Stinckwich > wrote: > >> I don't understand the default >> >> finalizeResourceData: handle >> handle isNull ifTrue: [ ^ self ]. >> handle free. >> handle beNull >> >> >> when handle is an Extern

Re: [Pharo-users] UFFI and autoRelease

On 25 April 2018 at 23:08, Serge Stinckwich wrote: > I don't understand the default > > finalizeResourceData: handle > handle isNull ifTrue: [ ^ self ]. > handle free. > handle beNull > > > when handle is an ExternaData, free is defined as in ExternalStructure > class as: > > free >

Re: [Pharo-users] UFFI and autoRelease

I don't understand the default finalizeResourceData: handle handle isNull ifTrue: [ ^ self ]. handle free. handle beNull when handle is an ExternaData, free is defined as in ExternalStructure class as: free "Free the handle pointed to by the receiver" (handle ~~ nil and:[han

Re: [Pharo-users] UFFI and autoRelease

hi, there is nothing like that and I do not recommend messing with the registry in general. but… you can always extend the classes for your use, is around FFIExternalResourceManager. cheers, Esteban > On 24 Apr 2018, at 14:48, Serge Stinckwich wrote: > > > I'm using autoRelease on some FFI