In a recent note, "Shmuel Metz (Seymour J.)" said:
> Date: Mon, 18 Sep 2006 18:35:47 -0300
>
> The caller of the subroutine, not the caller of the REXX. I know of no
> problem in changing the REXX's environment, just in changing the
> REXX's caller's environment. I don't know whether It's an option for
> Larry to do his mainline processing in REXX instead of shell.
>
Indeed. The Last Resort is the eval kludge, as used by tset(1):
while read NAME VALUE; do
case "$NAME" in
LIST | OF | VALID | NAMES )
eval $NAME='$VALUE';;
*) echo "invalid assignment to $NAME of $VALUE" >&2;;
esac
done <<end-of-env
` REXXEXEC arg1 ...
`
end-of-env
Where REXXEXEC writes a list of name/value pairs to stdout.
A recent thread in TSO-REXX discussed the hazards of INTERPRET.
"eval" has similar hazards, but I claim the above is quite safe.
-- gil
--
StorageTek
INFORMATION made POWERFUL
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
