A module ostensibly written for phase 0, can become phase n due to (require (for-syntax a-module)).
There is a module with test code that only makes sense at phase 0, but because it is (required "test-code.rkt") inside of another module which itself is required for syntax, or a higher module is required for syntax, it ends up executing at phase 1 or higher and making a mess. One can not use the simple dodge of a (begin-for-syntax) because that is just phase n+1. I.e. it is a relative construct. We have no idea where phase 0 is. unstable/syntax has a function called "(phase-of-enclosing-module)" is this the right way to do this? .. ah and what does 'unstable' imply here? -- 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. For more options, visit https://groups.google.com/d/optout.
