From 2cef97a924e7fadd1c41e542f93fa7ad4b14959a Mon Sep 17 00:00:00 2001 From: Kaz Kylheku Date: Tue, 16 Jul 2024 14:38:12 -0700 Subject: doc: misleading info about macro param lists. * txr.1: In the "Comparison to Macro Parameter Lists" section, which compares structural pattern matching to macro parameter lists, we remove the outdated claim that all positions in a macro parameter pattern must bind a variable. This has not been true since t has been supported as a way to support binding variables. --- txr.1 | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/txr.1 b/txr.1 index c47d5fc6..746d5932 100644 --- a/txr.1 +++ b/txr.1 @@ -46703,11 +46703,10 @@ cannot express the idea of matching a list whose first element is the symbol and whose third element is .codn 42 . Moreover, every position in the tree pattern much specify a variable -which captures the corresponding element of the structure. For instance, -a pattern which matches a three-element list must specify three variables, -one for each list position. This is because macro-style parameter lists are -oriented toward writing macros, and macros usually make use of every parameter -position. +which captures the corresponding element of the structure or else the symbol +.code t +to indicate that no variable is to be captured. There are no other +pattern matching operators. .NP* User-Defined Patterns -- cgit v1.2.3