Re: [netrexx-pipelines] Odd examples in the Language Reference manual

[René J. <rvj...@xs...>]

Hi Leslie

Yes, they are - the intention was that the current version of NetRexx was indicated in the example, but then, I should not have told the formatter that the text was literal code.
I’ll correct that for 4.02!

Best regards,

René.

> On 6 Oct 2021, at 06:29, J Leslie Turriff <jlt...@ma...> wrote:
> 
> 	I came across these odd-looking examples on pp 96, 97 of the NetRexx Language Reference, 
> Version 4.01-GA of March 20, 2021:
> 	
> | Example:
> | 
> | parse wordlist word1 wordlist
> | 
> | In this idiomatic example, the first word is removed from wordlist and is as-
> | signed to the variable word1, and the remainder is assigned back to wordlist.
> | 
> | Notes:
> | 
> |   1. The special words ask, source, and version, as described in the section Spe-
> |      cial names and methods(see page 121), allow:
> |
> |      parse ask x        -- parses a line from input stream
> |      parse source x     -- parses 'Java method \emph{filename}'
> | 
> |                                        96
> | 
> |    parse version x -- parses '\nr{} \emph{version} \emph{date}'
> |    These special words may also be used within expressions.
> | 
> | 2. Similarly, it is recommended that the initial (main) method in a stand-alone
> |    application place the command string passed to it in a variable called arg.
> |    53
> |    If this is done, the instruction:
> | 
> |    parse arg template
> | 
> |    will work, in a stand-alone application, in the same way as in REXX (even
> |    though arg is not a keyword in this case). 54
> 
> 	Are the strings "\nr{}" and "\emph{...}" formatting errors?
> 
> Leslie
> 
> Distribution: openSUSE Leap 15.3 x86_64
> NetRexx:      NetRexx 4.01-GA
> -- 
> 
> 
> _______________________________________________
> netrexx-pipelines mailing list
> net...@li...
> https://lists.sourceforge.net/lists/listinfo/netrexx-pipelines