Ok, the unsyntax-72 code cannot be cleanly done I think. You really need to use a reader macro. I leave the code base modding the reader char #. as before and will simple wait for a a possibility of per port reader option to be configured via a library.
/Stefan On Tue, Jan 22, 2013 at 5:38 PM, Andy Wingo <wi...@pobox.com> wrote: > On Tue 22 Jan 2013 17:19, Stefan Israelsson Tampe <stefan.ita...@gmail.com> > writes: > >>> > (read-hash-extend #\_ syntax-closure-reader) >>> >>> Have you tried having your srfi-72 module export a binding for unsyntax? >> >> I would like to use that of cause, but does it mix well with other >> already written code? > > It should work in a modular fashion. #,foo reads as (unsyntax foo), and > the meaning of that depends on the binding of unsyntax that is current. > > Andy > -- > http://wingolog.org/
