The Racket repository
![]() There were many such properties that were leftover from before the big GUI rewrite where the gracket executable was needed, and now there is no longer any need for these things. There are two exceptions: * There is a drdr feature that forces all tests that use gracket to run sequentially, which is used for tests that rely on some actual state of shown windows. I ran all of the files and monitored for windows popping up, and left the test to use gracket in these cases. * There are a few cases where running "racket -f <file>" resulted in an unbound identifier, whereas "gracket -f <file>" does not. These are because of the different global namespace, and I will fix them (props and the files) in a different commit. One of the expected results of this is that a drdr might run faster, because the serial-running hack above should now be applied only where relevant. (And some of the drracket tests are very long.) This commit is pushed by itself to identify possible problems with a drdr run that tests only this change. |
||
---|---|---|
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.