On Fri, Apr 27, 2018 at 11:04 AM, Rony G. Flatscher <[email protected]
> wrote:
> The default environment that address sends the command to can be set with
> "address nameOfEnvironment" or "address value (expression-yielding-name)".
>
> Seeing the examples in the testGroup files is it correct to assume that
> supplying an empty string as the second argument of the address keyword
> statement will use the currently defined default environment (the one with
> the name the address() built-in-function would return) ?
>
Not totally sure what you are asking, but I'm going to go with "no".
> There is a "test" environment being excercised: is this environment part
> of ooRexx? If not, where does it get defined?
>
That was just a scaffolding command handler I wrote so that I could test
all of the infrastructure of the redirection while I waited for the actual
trapping code in the system command handler to get implemented. Erich
adapted all of the tests I had written to a live environment and the
scaffold has been removed.
Lastly: is it somehow possible to have the environment name dynamically
> evaluated right with the command to send it to?
>
No.
> ... cut ...
> opSys='w' -- windows
> address (getEnvironmnetNameToUse(opSys)) (getCommandToExecute(opSys,'
> dir'))"
> ... cut ...
>
> ---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
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
>
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
