On Sun, 10 Dec 2006, David Van Horn wrote: > How does one write a procedural macro using SRFI 72 that expands to code > containing unquote or unquote-splicing without these being interpreted > at expansion time as an escape from quasisyntax quotation?
It is possible using the kind of tricks described in the Bawden reference. Unsyntax is a better solution - I only used unquote in this srfi because the #, abbreviation for unsyntax is not r5rs-portable. Andre
