Re: [racket-users] Separate compilation vs macros in signatures and compiler stacktraces (crashes?)

(Old thread ...) I only want to add an example of identifier capture. Here the identifier _it_ is not bound at the macro compiling time, but is bound at the final code. Note: Capture is discouraged in Racket. I think that 99% of the times, the unbound identifiers are just typos, like displyaln.

Re: [racket-users] Separate compilation vs macros in signatures and compiler stacktraces (crashes?)

I think there are two issues here: 1. The stack trace in your email is just a result of `raco make` printing its current context when there's a syntax error. If you replace the whole body of the module with just `(lambda)`, you'll see the same stack trace. Probably `raco make` should be changed

Re: [racket-users] Separate compilation vs macros in signatures and compiler stacktraces (crashes?)

Thanks for the prompt answer and the clarifications! But there's a third issue, which unfortunately I've hid when I combined the modules in one file (sorry), and which is more important. Sorry I made this unclear. In the split version

Re: [racket-users] Separate compilation vs macros in signatures and compiler stacktraces (crashes?)

On Tue, Oct 6, 2015 at 7:50 PM, Paolo Giarrusso wrote: > Thanks for the prompt answer and the clarifications! But there's a > third issue, which unfortunately I've hid when I combined the modules > in one file (sorry), and which is more important. Sorry I made this >