The Friday entry demonstrates how to break hygiene for a macro that defines a generator. Ryan Culpepper, the local macrologist, reminded me that expanding into this macro goes wrong in the syntax-case world:
Run this in Pretty Big [DrScheme] and you get a strange note concerning MrEd's yield or run it in MzScheme [Textual] and you get an error message about 'yield' being unbound. What gives? The 'stx' of
(define-syntax define-that-expands-into-define/y (syntax-rules () ((_ (name arg ...) body ...) (define/y (name arg ...) body ...)))) (define-that-expands-into-define/y (bar) (yield 1) (yield 2) 'finished)
datum->syntax-objectis the syntactic context of the new macro but it doesn't bind yield; it just uses it. So the definition of
define/ymust be a different one according to the hygiene standards. Ergo yield is free at the top-leve [MzScheme] or bound to the yield import from MrEd [Pretty Big]. ;; --- How can we try to fix this? The explanation suggests we use a different macro definition for
define/y, one that uses a context that is guaranteed from the body of an instance of
Run it. You will find that it works as expected. Tomorrow, time permitting, I will tell you what's wrong with it and how you can fix it.
(require (lib "control.ss")) (define-syntax (define/y stx) (syntax-case stx () [(_ (name arg ...) body0 body ...) (with-syntax ((yield-name (datum->syntax-object (syntax body0) 'yield))) (syntax (define (name arg ...) (define (yield-name x) (control resume-here (set! name (lambda () (prompt (resume-here 'dummy)))) x)) (prompt body0 body ...))))])) (define-syntax define-that-expands-into-define/y (syntax-rules () ((_ (name arg ...) body ...) (define/y (name arg ...) body ...)))) ;; --- try it out --- (define-that-expands-into-define/y (bar) (yield 1) (yield 2) 'finished) (list (bar) (bar) (bar) (bar))