Re: [racket-users] [racket] Racket 6.3(.0.7) breaks old code

2015-12-25 Thread WarGrey Gyoudmon Ju
An additional feedback. There was a ghost bug in my code, and it only appeared after compiling. module-path-index-resolve: "self" index has no resolution module path index: # context...: /opt/PLTracket/collects/syntax/private/id-table.rkt:77:2: do-ref /opt/PLTracket/share/pkgs/typed-rack

Re: [racket-users] [racket] Racket 6.3(.0.7) breaks old code

2015-12-02 Thread Matthew Flatt
Thanks for the example! The problem is a bug in `namespace-mapped-symbols` (due to changes related to the new macro expander). I will push a repair later today. At Mon, 30 Nov 2015 20:16:44 +0800, WarGrey Gyoudmon Ju wrote: > Thank you, Matthew. > > The project itself is organized as a multi pac

Re: [racket-users] [racket] Racket 6.3(.0.7) breaks old code

2015-11-30 Thread WarGrey Gyoudmon Ju
Thank you, Matthew. The project itself is organized as a multi package, however there is no need to install it. Debug/DigiGnome ; this subpackage is the base one of the other two. Debug/Kuzuhamon/; this one meets the second problem Debug/sakuyamon/ ; this one meets the first problem

Re: [racket-users] [racket] Racket 6.3(.0.7) breaks old code

2015-11-29 Thread Matthew Flatt
My guess is that you're running into an incompatibility created by the new macro system. Something like lifting code out of an expanded `module` form and dropping it into a different one? A change related to submodule expansion? Or something related to the top-level namespace? It might be an unavoi

[racket-users] [racket] Racket 6.3(.0.7) breaks old code

2015-11-29 Thread WarGrey Gyoudmon Ju
It is compiled by myself with no strange options. Rebuilding the project (without DrRacket) fails due to two strange behaviors. The first one is module-path-index-resolve: "self" index has no resolution. It breaks lots of scripts, I cannot locate where it is exactly occurs. 1. errortrace says mak