On Wed, 23 Oct 2013 14:09:45 -0500, Kirk Wolf wrote:
>
>(*Note*: in the following examples, shell input is bold and follows "> ".
> Also: you need "set -o pipecurrent" when piping jessym output into "read"
>or "." )
>
So, I asked myself, "Why pipecurrent?" Then I saw:
>*> set -o pipecurrent *
>*> jessym A | read -r myvar*
>*> echo $myvar*
>B
>
... but "pipecurrent isn't necessary if you do:
jessym A | ( read -r myvar*; echo $myvar* )
... scope; scope; always scope!
I was unfamiliar with the "-r" option of "read". But it doesn't
work right anyway. Comment sent to MVS-OE.
Of course, I'd be perverse enough to try with as many metacharacters
as possible in the symbol value. 0x15 comes first to mind. Of course,
there's little hope for 0x00.
Would a completely escaped format of output, such as produced by
"export -p" be of value? Example:
user@HOST: ( wombat='foo
> bar' export wombat
> export -p )
...
export wombat="foo
bar"
Of course if there's a NUL in a JES symbol value only a savvy program could
deal with it. (Consider the interaction of "find ... -print0" with "xargs -0
..."
GNU required.)
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
