diff options
author | Kaz Kylheku <kaz@kylheku.com> | 2025-04-06 22:23:57 -0700 |
---|---|---|
committer | Kaz Kylheku <kaz@kylheku.com> | 2025-04-06 22:23:57 -0700 |
commit | 6feec15b59de91e753e0ab55e748c2ec6192b80a (patch) | |
tree | c0b1f1dda3a3cb6a84c5d62fd5228e8b51d4cf53 | |
parent | 15824c1a29cf2ee7cf8909eceeb810c77149b29f (diff) | |
download | txr-6feec15b59de91e753e0ab55e748c2ec6192b80a.tar.gz txr-6feec15b59de91e753e0ab55e748c2ec6192b80a.tar.bz2 txr-6feec15b59de91e753e0ab55e748c2ec6192b80a.zip |
doc: mention whitespace issue in infix
* txr.1: Make it clear that whitespace is required between
atoms in infix expressions most of the time, so certain
compact notations from C-like syntax are not achieved.
-rw-r--r-- | txr.1 | 13 |
1 files changed, 13 insertions, 0 deletions
@@ -54120,6 +54120,19 @@ which means that it is notated with parentheses: Informally speaking, the Infix Syntax feature does not eliminate the outer parentheses. +Whitespace is required between atoms in infix expressions, because +they are ordinary Lisp lists. The infix feature does not introduce +any new token-level syntax. The expression +.code "(b + a ++)" +cannot be written +.code "(b+a++)" +or +.codn "(b + a++)" . +In situations where parentheses or braces are adjacent to +each other or to an atom, spaces may be elided, as allowed by +Lisp syntax, exemplified by: +.codn "(log(a[i][j]++))" . + .NP* Operator Table .TS |