Re: [Oorexx-devel] Stashing Rexx class objects in an external native library

2009-09-10 Thread Rick McGuire
Not necessary. The global references tables are cleared when the interpreter environment is shutdown. An uninit method is not really needed, because once the uninit method is called, you can't reach those classes any more, so there's no chance of using a stale reference. Rick On Thu, Sep 10, 20

Re: [Oorexx-devel] Stashing Rexx class objects in an external native library

2009-09-10 Thread Mark Miesfeld
On Tue, Sep 8, 2009 at 4:42 PM, Rick McGuire wrote: > Yes, this is safecurrently.  However, the success of this depends > entirely on the characteristics of the garbage collector.  You > shouldn't assume that the reference passed directly to your method is > necessarily a direct reference to

Re: [Oorexx-devel] Stashing Rexx class objects in an external native library

2009-09-08 Thread Mark Miesfeld
Okay. Well yeah, I shouldn't assume the garbage collector will never be rewritten. -- Mark Miesfeld On Tue, Sep 8, 2009 at 4:42 PM, Rick McGuire wrote: > Yes, this is safecurrently.  However, the success of this depends > entirely on the characteristics of the garbage collector.  You > shoul

Re: [Oorexx-devel] Stashing Rexx class objects in an external native library

2009-09-08 Thread Rick McGuire
Yes, this is safecurrently. However, the success of this depends entirely on the characteristics of the garbage collector. You shouldn't assume that the reference passed directly to your method is necessarily a direct reference to the object, so good practice dictates you should request a glo