summaryrefslogtreecommitdiffstats
path: root/tests/common.tl
diff options
context:
space:
mode:
authorKaz Kylheku <kaz@kylheku.com>2022-01-18 07:33:07 -0800
committerKaz Kylheku <kaz@kylheku.com>2022-01-18 07:33:07 -0800
commitfbe8228a05d169c539cd36218b466e5d298923ba (patch)
tree851ac538e6b5adab5349bbad5cdba5f3baf6f87b /tests/common.tl
parenta756991b21d35c2b72d521ed0a9ae69eac0105a9 (diff)
downloadtxr-fbe8228a05d169c539cd36218b466e5d298923ba.tar.gz
txr-fbe8228a05d169c539cd36218b466e5d298923ba.tar.bz2
txr-fbe8228a05d169c539cd36218b466e5d298923ba.zip
quasiquote: support @,expr hack.
For better or worse, TXR Lisp has a dichotomy of representation that @<atom> produces sys:var syntax, whereas @<compound> produces sys:expr. This can cause an issue in backquoting. Suppose you want to use backquote to generate sytax like (a @b) where the b comes from a variable. The problem is that (let ((x 'b)) ^(a @,x)) doesn't do what you might expect: it produces (sys:expr b) rather than (sys:var b). This patch adds a hack into the quasiquote expander which causes it to generate code to do what you expect. Old behavior: 1> (expand '^(a @,x)) (list 'a (list 'sys:expr x)) New behavior: 1> (expand '^(a @,x)) (list 'a (let ((#:g0012 x)) (if (atom #:g0012) (list 'sys:var #:g0012) (list 'sys:expr #:g0012)))) In other words, x will be evaluted, and the based on the type of the object which emerges, either sys:var or sys:expr syntax is generated. * eval.c (expand_qquote_rec): Implement the above hack. We are careful to only do this when this exact shape occurs in the syntax: (sys:expr (sys:unquote item)). * tests/010/qquote.tl: New file. * txr.1: Documented.
Diffstat (limited to 'tests/common.tl')
0 files changed, 0 insertions, 0 deletions