On 04.06.2017 18:13, Rick McGuire wrote:
>
> Yes, that is working correctly. The loaded packages are managed on a global
> basis.
Thank you for this clarification!
> btw, you have asked this question in the past.
Ha, I was not aware of this anymore (hence I did not even attempt to search my
archives for this
issue/theme)!
:(
Going thru the mail archives, I found the conversation of April 2009 (I have
been aware of the
.local part only). Will file a documentation RFE to document these important
aspects.
---rony
>
> On Sun, Jun 4, 2017 at 12:05 PM, Rony G. Flatscher <rony.flatsc...@wu.ac.at
> <mailto:rony.flatsc...@wu.ac.at>> wrote:
>
> Not sure whether this is a bug or working as designed (if so, perhaps it
> should get documented).
>
> When using the "::requires" directive, a resolved package will get
> re-used (only at the very first
> "::requires" will a call without arguments be carried out by the
> interpreter).
>
> In an environment where multiple Rexx interpreter instances are employed,
> I would have expected,
> that required Rexx packages get re-created from scratch upon when they
> are required the first time
> in a new interpreter instance (e.g. so class or routine objects are
> distinct per Rexx intepreter
> instance). In essence expecting that this gets "scoped" per interpreter
> instance like ".local"
> (which gets created for each interpreter instance).
>
> Further analysis shows, that the prolog code of required packages gets
> run on each new interpreter
> instance, without re-creating the package separately for each interpreter
> instance. This may
> indicate that this behavior is intended. If so, it should get documented
> with the ::requires
> directive (or with the native RexxCreateInterpreter()-API).
>
> ---rony
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
