diff options
| author | Kaz Kylheku <kaz@kylheku.com> | 2015-11-17 21:12:33 -0800 |
|---|---|---|
| committer | Kaz Kylheku <kaz@kylheku.com> | 2015-11-20 16:17:19 -0800 |
| commit | ec5daf6385b68f08e82c106a925a758cf2b2bf14 (patch) | |
| tree | a0023de2d03fcbe7a03e1ee72f1b9192980cb9ef /txr.1 | |
| parent | 49b863afbd7e78dcc07d20df6652a969d919921e (diff) | |
| download | txr-ec5daf6385b68f08e82c106a925a758cf2b2bf14.tar.gz txr-ec5daf6385b68f08e82c106a925a758cf2b2bf14.tar.bz2 txr-ec5daf6385b68f08e82c106a925a758cf2b2bf14.zip | |
@(next) takes Lisp expression as source now.
* match.c (v_next): Evaluate the source expression as TXR Lisp,
unless it is meta-expression or meta-variable, or
the compatibility option is set to 124 or lower.
In those cases treat it as an expression of the TXR Pattern
* txr.1: Updated documentation of @(next) and all
relevant examples of @(next) everywhere.
Added compatibility notes.
Diffstat (limited to 'txr.1')
| -rw-r--r-- | txr.1 | 24 |
1 files changed, 22 insertions, 2 deletions
@@ -3071,7 +3071,7 @@ to \*(TX on the command line. If .meta source -is given, it must be string-valued expression which denotes an +is given, it must be string-valued Lisp expression which denotes an input source; it may be a string literal, quasiliteral or a string-valued variable. For instance, if variable .code A @@ -32444,7 +32444,7 @@ Collect lines from all files that are given as arguments on the command line. If there are no files, then read from standard input: .cblk - @(next @(open-files *args* *stdin*)) + @(next (open-files *args* *stdin*)) @(collect) @line @(end) @@ -37770,6 +37770,26 @@ of these version values, the described behaviors are provided if is given an argument which is equal or lower. For instance .code -C 103 selects the behaviors described below for version 105, but not those for 102. +.IP 124 +In \*(TX 124 and earlier versions, the +.code @(next) +directive didn't evaluate the +.meta source +argument as a Lisp expression, but as a \*(TX Pattern Language +expression. Lisp expressions thus had to be delimited by +.codn @ . +The current behavior is that the argument is treated as Lisp. +If the compatibility option is set to 124 or lower, the old behavior +is restored. However, even without the presence of the compatibility option, +if the +.meta source +argument is a meta-expression or meta-variable (denotes by the +.code @ +prefix in front of a compound expression or symbol, respectively) +it is also treated in the old way. This latter behavior is obsolescent +and will eventually disappear, and the compatibility option will be +the only way to get the old behavior. + .IP 123 In \*(TX 123 and earlier, the variable initialization forms of a .code for |