The Racket repository
c8f4ac6ae4
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. |
||
|---|---|---|
| collects | ||
| doc | ||
| man/man1 | ||
| src | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| README | ||
The Racket programming language =============================== Important executables: * DrRacket: Racket's integrated development environment (start here!). * Racket: the main command-line entry point for running racket programs and scripts. * GRacket: the GUI-mode Racket executable. * raco: Racket's command-line toolset. More Information ---------------- Racket comes with extensive documentation: use DrRacket's `Help' menu, or run `raco docs'. Also, visit us at http://racket-lang.org/ for more Racket resources. Instructions for building Racket from source are in src/README. License ------- Racket Copyright (c) 2010-2012 PLT Scheme Inc. Racket is distributed under the GNU Lesser General Public License (LGPL). This means that you can link Racket into proprietary applications, provided you follow the rules stated in the LGPL. You can also modify Racket; if you distribute a modified version, you must distribute it under the terms of the LGPL, which in particular means that you must release the source code for the modified software. See doc/release-notes/COPYING.txt for more information.