Thanks. As I noted, not only `match' but quite some expressions (most
just sit inside some of my own macro(s) that expands to `begin' don't
expand inside a package. I would assume they are all caused by the same
reason.
Chongkai
Ryan Culpepper wrote:
On Mar 11, 2009, at 12:28 AM, Chongkai Zhu wrote:
Macro step on the following code with standard hiding (or as long as
mzscheme syntax is hidden):
(require scheme/package)
(define-syntax-rule (d t)
t)
(match (d 1)
(x x))
(define-package p #:all-defined
(match (d 1)
(x x)))
The (d 1) in the top-level match expression gets expended, but the
same macro in the package stay unexpanded. Is this a bug?
I think 'define-package' is doing some renames in a way that escapes
the macro stepper. I'll have an idea of what's happening and how I can
fix it, but I haven't had time to test my hypothesis yet.
Ryan
_________________________________________________
For list-related administrative tasks:
http://list.cs.brown.edu/mailman/listinfo/plt-dev
_________________________________________________
For list-related administrative tasks:
http://list.cs.brown.edu/mailman/listinfo/plt-dev
