-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/22/2013 08:02 AM, Moritz Heidkamp wrote:
> I think this kind of mechanism is something we should have in order to > provide proper support for custom read syntax and to make SRFI 10 syntax > behave as expected. Let me know if you have any suggestions for > improving the API (not sure if quasiquote-handler is the best name for > this kind of thing) or implementation (I don't know whether we need to > pass the `n' argument to handlers or if we can hide it in a closure, for > example). Also I'm not sure about where to put the code (maybe > define-quasiquote-handler should not live in expand.scm). What might a handler use the `n' argument for? If it's always just plumbed through to walk unchanged, I'd say put it in a closure. If it might be useful to do something with it, leave it exposed. Also: If this gets accepted, I've offered to write an SRFI documenting its final form - it's a natural fit with SRFI-10 or any other reader extension mechanism! > > Thanks! > Moritz > ABS - -- Alaric Snell-Pym http://www.snell-pym.org.uk/alaric/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlEnNTEACgkQRgz/WHNxCGrP3wCcCRyvxYCy4fxEL6MFUO5iUUqJ W4wAnRFkT8zlQSFid1DPdsyQ6i1BPNUH =GQj9 -----END PGP SIGNATURE----- _______________________________________________ Chicken-hackers mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/chicken-hackers
