(John, not sure if you got this.)
As we know, to embed a value that could include any character we use “…
x”c2x(UserInput)”…”.
If the value could also be an null string, it’s a bit harder.
*PipStr: if arg(1) == “” then return “//” else return “x”c2x(arg(1))*
My suggestion has some possible solutions:
· Support null hex strings:
* x/1234ff/*, where / is limited to special characters (perhaps), and
which could also allow REXX style blanks: *x/12 34 ff/*
and/or *x1234ff[x]*, where the trailing x is optional unless the
string is null,
or just allow *x* by itself to be a null string.
· Support a var string specification:
* “locate var Fred [tracking]”*, which avoids converting something to
hex, just to convert it back, and, with *tracking*, allows, the
value to vary as records are processed.
Avoiding the redundant conversion may be more compelling, if harder.
I think any of these could be fit into the existing syntax without conflict.
Just my two cents.
--
OREXXMan
