On Tue, May 19, 2009 at 11:36 PM, Glenn Knickerbocker <[email protected]> wrote:
> That has its own gotchas. If you don't do anything to control the > timing of VAR relative to the other input, you'll wind up juxtaposed > with either the variable's value or nothing, unpredictably. I guess that's the problem with the proposed "var" approach. We need exactly all those controls to make sure the pipes don't leak and behavior is deterministic. The only thing that could very remotely make sense to me is a shorthand for a "protected REXX substitution" where the variable is defined during the scanning of the pipeline already. GDDM/REXX is gone that route with the variables prefixed by the period. I have never liked that, but the flood of quotes is not elegant either. Such a substituted variable would be implicitly a delimited string, so you could have something like this: cmd = 'EXEC SENDFILE' ; uid = 'PRINCE AT LARGE' 'PIPE < listof files | spec .cmd 1 w1.3 nw .uid nw | command | cons' Rob -- Rob van der Heij Velocity Software http://www.velocitysoftware.com/
