diff options
author | Kaz Kylheku <kaz@kylheku.com> | 2021-01-25 21:57:39 -0800 |
---|---|---|
committer | Kaz Kylheku <kaz@kylheku.com> | 2021-01-25 21:57:39 -0800 |
commit | e0dd147ff4b7a0b915323d637b8f879e06d02a1f (patch) | |
tree | e2b8519aff1e371d3b23f26e5599a8bd71876d92 | |
parent | 6d538cae2993b242484d7d89ede571db45093281 (diff) | |
download | txr-e0dd147ff4b7a0b915323d637b8f879e06d02a1f.tar.gz txr-e0dd147ff4b7a0b915323d637b8f879e06d02a1f.tar.bz2 txr-e0dd147ff4b7a0b915323d637b8f879e06d02a1f.zip |
doc: fix .meti not wrapped in of .mono/.onom.
* checkman.txr (check-meti): New pattern function
which simply diagnoses any .meti. This relies on the fact that
.mono/.onom blocks are matched and consumed by by another rule.
All valid .meti lines are consumed as part of these blocks,
so any .meti that remain must be outside.
* txr.1: Fix numerous occurrences of this.
-rw-r--r-- | checkman.txr | 10 | ||||
-rw-r--r-- | txr.1 | 32 |
2 files changed, 42 insertions, 0 deletions
diff --git a/checkman.txr b/checkman.txr index 48df2606..13bab474 100644 --- a/checkman.txr +++ b/checkman.txr @@ -122,6 +122,14 @@ @ (throw bad ln `dangling @mac`) @(end) @;; +@;; Check for .meti not wrapped in .mono/onom. +@;; macros. +@;; +@(define check-meti ()) +.meti @(skip) +@ (throw bad ln ".meti not in .mono") +@(end) +@;; @;; Main @;; @(bind errors 0) @@ -142,6 +150,8 @@ @ (check-synb) @ (or) @ (check-spurious) +@ (or) +@ (check-meti) @ (end) @ (catch bad (line msg)) @ (do (inc errors) @@ -19192,27 +19192,49 @@ is equivalent to invoking a more specific copying function according to the type of the argument, as follows: .RS .coIP cons +.mono .meti (copy-list << object ) +.onom .coIP str +.mono .meti (copy-str << object ) +.onom .coIP vec +.mono .meti (copy-vec << object ) +.onom .coIP hash +.mono .meti (copy-hash << object ) +.onom .IP "struct type" +.mono .meti (copy-struct << object ) +.onom .coIP fun +.mono .meti (copy-fun << object ) +.onom .coIP buf +.mono .meti (copy-buf << object ) +.onom .coIP carray +.mono .meti (copy-carray << object ) +.onom .coIP random-state +.mono .meti (make-random-state << object ) +.onom .coIP tnode +.mono .meti (copy-tnode << object ) +.onom .coIP tree +.mono .meti (copy-search-tree << object ) +.onom .RE .IP @@ -37402,7 +37424,9 @@ using the comparison function given by the function name .metn cmp-fun . This comparison takes places as if by evaluating the expression +.mono .meti >> ( cmp-fun < value << cmp-val ) +.onom where .meta value denotes the current value of @@ -39357,7 +39381,9 @@ by default is not supported by that is to say, the syntax .meta sym cannot be used in place of the +.mono .meti >> ( sym << init-form ) +.onom syntax when .meta sym is to be initialized to @@ -39669,7 +39695,9 @@ except those parts introduced by the meta prefix This prefix denotes variables like .code @a as well as useful pattern matching operators like +.mono .meti @(all << pattern ) +.onom which matches a list or sublist whose elements all match .metn pattern . @@ -60909,7 +60937,9 @@ semantics as the same-named parameters of The .meta opt-specifier arguments are lists of between two and four elements: +.mono .meti >> ( short-symbol < long-symbol >> [ type <> [ help-text ]]). +.onom The .meta short-symbol and @@ -69474,7 +69504,9 @@ symbol has been assigned the highest possible value of the FFI type, then an error exception is thrown. If +.mono .meti >> ( sym << value ) +.onom is given, then .meta sym is given the specified value. The |