typed-racket

Typed Racket

Go to file

Matthew Flatt f549a9e634 submodules: make .zo path stick for consistent independent loading When a module is loaded from bytecode and then the value of `use-compiled-file-paths' changes, an attempt to load a submodule would fail, because source isn't used if the main module is already declared, and the bytecode code is not used according to `use-compiled-file-paths'. Make the bytecode path stick when it is used once, so that submodule loads succeed, and make it work even with `namespace-module-attach'. The module-attach part of this protocol requires a change to the API of a module name resolver: the notification mode gets two arguments, instead of one, where the second argument is an environment. original commit: c8f4ac6ae47023157a337aa5e164b74439e373d6	2012-07-17 09:47:05 -06:00
collects	submodules: make .zo path stick for consistent independent loading	2012-07-17 09:47:05 -06:00
doc/release-notes/typed-racket	Typed Racket HISTORY for 5.2.1.	2012-01-24 10:49:42 -05:00

Matthew Flatt f549a9e634 submodules: make .zo path stick for consistent independent loading

When a module is loaded from bytecode and then the value of
`use-compiled-file-paths' changes, an attempt to load a submodule
would fail, because source isn't used if the main module is
already declared, and the bytecode code is not used according to
`use-compiled-file-paths'. Make the bytecode path stick when it
is used once, so that submodule loads succeed, and make it work
even with `namespace-module-attach'.

The module-attach part of this protocol requires a change to the
API of a module name resolver: the notification mode gets two
arguments, instead of one, where the second argument is an
environment.

original commit: c8f4ac6ae47023157a337aa5e164b74439e373d6

2012-07-17 09:47:05 -06:00

collects

submodules: make .zo path stick for consistent independent loading

2012-07-17 09:47:05 -06:00

doc/release-notes/typed-racket

Typed Racket HISTORY for 5.2.1.

2012-01-24 10:49:42 -05:00