The Racket repository
db7f2b4542
requiring itself into the entered namespace. This makes it useful in some cases where this require leads to a dependency cycle, eg (enter! racket/list). It's obviously not useful for use as-is, since you will not have a bound `enter!' to get out of the namespace (and possibly no `require' to get it) -- but it is useful for meta-tools like xrepl. This is why the flag is verbose. `xrepl' now uses this flag. Also, the check for valid keywords for the form is now done at runtime rather than in the macro. This doesn't matter in this case, since the form is intended for interactive use anyway. Also, separate the two parts of `enter-load/use-compiled' (it was defined curried, but didn't use it). |
||
|---|---|---|
| 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-2011 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.