From: <hp...@we...> - 2022-06-21 08:00:06
|
Hello Leslie! Am 20.06.2022 um 23:29 schrieb J Leslie Turriff: > On 2022-06-19 04:40:13 ((I)) wrote: >> [...] > You're quite right. I changed these to > | change /\u000A\u0022/ /\u000A\u201C/ | > | change /\u0020\u0022/ /\u0020\u201C/ | > | change /\u0022\u000A/ /\u201D\u000A/ | > etc., which should be safe. It looks somehow more transparent now. But -- "It is an error to use this escape if the character encoding for the implementation requires fewer than four hexadecimal digits." (NetREXX Language Reference, chapter 6.3 Tokens, table 1, p. 18) So "the implementation" is in any case a double-byte system? As an additional substantiation an example of a troublesome case. To avoid the detour of using a temp disk file just to get a list of file names, see commented line 1, I tried to use the cmd stage... > -- '' 'DIR "' || rawdir || '\*.RAW" /B /ON > $T$E$M$P.F$I$L$E$' > address '' ripe '"(MkR_3 sep ! end ?) cons', > 'spec /DIR \"/ 1 *-* n ,\\*.RAW\" /B /ON, n!cmd! ...', > with input using (rawdir) output stem prgm. Since 'rawdir' may contain blanks I do have to bracket it with double quotes -- alas, unlucky so far. Seems I must resort to spec with hex values. BTW, 'ripe' is > ripe = '@java -cp "', /* NRP */ > || value("NETREXX_HOME", , "ENVIRONMENT"), > || '\lib\NetRexxF.jar;', > || value("CLASSPATH", , "ENVIRONMENT"), > || '"' 'org.netrexx.njpipes.pipes.runner' ----- >>> loop while execOptions.words > 0 >>> parse execOptions execOption execOptions >>> select >>> when 'help'.abbrev(execOptions.lower,1) then >> >> [...] > implies, the following parse command, > | parse execOptions execOptions execOptions > takes the first word (maybe the only word) ... Understood, this parse sips off the first word of execOptions. What me wonders is, the condition for When depends on the /remaining/ words in 'execOptions' (the variable with plural-'s'). I rather expected a check of the single option in question, just obtained (or split off) by parse two lines before. Best, M. |