In case this helps, here is the output from the macro stepper for a sample
macro invocation:
(named-query
(name-line (offset 0) (name-type "name") "always-true")
(level)
(line (offset 0) (type (default "default")) (test (truetest "x"))))
->
(define:24 always-true
(lambda:24 ()
(query:24
(line (offset 0) (type (default "default")) (test (truetest
"x")))
(level)
(line (offset 0) (type (default "default")) (test (truetest
"x"))))))
->
(define:25 always-true
(lambda:25 ()
(query:24
(line (offset 0) (type (default "default")) (test (truetest
"x")))
(level)
(line (offset 0) (type (default "default")) (test (truetest
"x"))))))
->
(define-values:26 (always-true)
(lambda:25 ()
(query:24
(line (offset 0) (type (default "default")) (test (truetest
"x")))
(level)
(line (offset 0) (type (default "default")) (test (truetest
"x"))))))
'query' is another macro, but hopefully not relevant to my problem.
This is using the version of my code where I added the call to
datum->syntax after converting the string to a symbol. With this output,
should 'always-true' be visible to other code in the same module?
-- Jonathan
--
You received this message because you are subscribed to the Google Groups
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to racket-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/racket-users/0e11245e-f1f9-4df1-8d3e-be5cb48c421c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
