Trying to analyze runtime behaviours using a rexxtry.rex session in which BSF objects get created,
some of which do not get assigned to Rexx variables (and hence turning to garbage after the
respective statement got executed).
Creating over and over BSF-ooRexx objects that do not get referenced
A garbage collection is triggered any time an allocation request fails. At
that time, all of the unreferenced objects are swept up and repooled and
the allocation request is retried. The uninits on objects that have been
identified as unreferenced will get run at the next "safe" boundary, which
is
On 24.04.2022 19:57, Rick McGuire wrote:
A garbage collection is triggered any time an allocation request fails. At that time, all of the
unreferenced objects are swept up and repooled and the allocation request is retried. The uninits
on objects that have been identified as unreferenced will ge
