Re: [Oorexx-devel] gc() BIF commiteed (Re: The planned implementation (Re: Again a need for access to some gc() BIF ...

Greetings ooRexx'ers, Rony G. Flatscher wrote: Going through the feature request entries, the very first request was placed with IBM in 2005 and got carried over into the RFE database of open object Rexx as . My my, 20 years. That was th

[Oorexx-devel] gc() BIF commiteed (Re: The planned implementation (Re: Again a need for access to some gc() BIF ...

Going through the feature request entries, the very first request was placed with IBM in 2005 and got carried over into the RFE database of open object Rexx as . After locally the test suite passed, the commits for gc() were excercised: doc

Re: [Oorexx-devel] The planned implementation (Re: Again a need for access to some gc() BIF ...

For the record, running the same speed test on the same machine with the release version makes the gc() call about twenty-five (!) times faster: G:\test\orx\gc>rxenv rexx test_gc_speed.rex test_gc(1) : 00:00:00.037000 -> 00:00:00.03 per call test_reverse(1): 00:00:00.000

[Oorexx-devel] The planned implementation (Re: Again a need for access to some gc() BIF ...

This is the planned implementation of gc() which * always runs in a debug version of ooRexx (.RexxInfo~debug=.true) * does *not* run in a release version of ooRexx (.RexxInfo~debug=.false) to cater for Rick's preoccupation; however, there is an overrule possibility if the argument "force"