I find the example too abstract to understand why the computation
happens at the wrong phase when you adjust the code with
`begin-for-syntax'. Can you explain a little more, maybe with a more
concrete example?
Just in case, here's the code that I think you have in mind for wrong
phase:
#lang
On Fri, Jul 6, 2012 at 11:00 AM, Matthew Flatt mfl...@cs.utah.edu wrote:
I find the example too abstract to understand why the computation
happens at the wrong phase when you adjust the code with
`begin-for-syntax'. Can you explain a little more, maybe with a more
concrete example?
Just in
At Fri, 6 Jul 2012 11:13:44 -0400, Sam Tobin-Hochstadt wrote:
I had not realized that I could sensibly wrap a module in a
`begin-for-syntax`. What is the semantic difference between that and
a plain submodule (other than my example working)?
For `(module* _name #f )', `begin-for-syntax'
I'd like to write a program basically like this:
#lang racket/load
(module m1 racket
(define l (list #'l))
(provide l))
(module m2 racket
(require (for-syntax 'm1))
(define-syntax (mac stx)
#`(module* sub #f
(length (list #,(car l)
(provide mac))
(module m3 racket
4 matches
Mail list logo