[Chicken-users] Explicit renaming macros behavior during interpretation and compilation

2010-04-15 Thread Jeronimo Pellegrini
Hello, I understand syntax-rules and Common Lisp's defmacro, but I'm still getting acquainted with Chicken's implementation of explicitly renaming macros. So far I have had success in writing simple macros, but there's one thing I don't understand. This program seems to work fine when loaded from

Re: [Chicken-users] Explicit renaming macros behavior during interpretation and compilation

2010-04-15 Thread Thomas Chust
2010/4/15 Jeronimo Pellegrini : > [...] > This program seems to work fine when loaded from csi, but csc > complains that a procedure used inside the renaming procedure > is unbound (even though it was defined shortly before the > macro definition): > [...] Hello Jeronimo, the environment in which

Re: [Chicken-users] Explicit renaming macros behavior during interpretation and compilation

2010-04-15 Thread Jeronimo Pellegrini
On Thu, Apr 15, 2010 at 03:40:01PM +0200, Thomas Chust wrote: > Hello Jeronimo, Hi Thomas! > the environment in which syntax transformers are run is distinct from > the one in which the compiled code is eventually run. You probably > want to use define-for-syntax instead of define to introduce yo