On 26.05.2012 16:11, Rick McGuire wrote:
> It should work for any object, assuming you're not passing a NULL
> value as the object.
No, I am not passing a NULL value (the Rexx string object is processed in a loop and at the end of
the loop the API gets invoked for it).
As currently I still have the version that causes that behaviour (on ooRexx 4.1.1, 32-bit, Windows
XP9, I will create an archive out of it and file it with a bug report.
> On Sat, May 26, 2012 at 9:57 AM, Rony G. Flatscher
> <Rony.Flatscher@...> wrote:
>> While working on BSF4ooRexx I added a ReleaseLocalReference() in an external Rexx function for Rexx
>> (String) objects retrieved (using ArrayAt()) from the passed array (using ARGLIST to get the
>> argument array in the external function).
>> This seems to work for many Rexx programs that invoke that external Rexx function in BSF4ooRexx,
>> however, if running a certain Rexx application, unexplainably ooRexx abends (Window popup, title:
>> "Open Object Rexx Interface", message - translated from German to English - "Open Object Rexx
>> Interface found a problem and needs to be ended").
>> This occurs while calling the ReleaseLocalReference()-API on a Rexx string object retrieved from the
>> aforementioned array. This is also the only place in the entire program that applies
>> Before filing a bug I would like to know whether this usage of ReleaseLocalReference() is valid at
>> all (working on Rexx objects passedn in the ARGLIST array)?