The Racket repository
Go to file
Robby Findler 8ece97219a a hack to work around what appears to be just a wrong way of doing things, but will ask Noel later.
The basic problem is that (with-check-info* '() (lambda () ...whatever...)) can, in some cases,
double the information that is recorded in a failed test case. Probably the right thing is
to use a parameter or something instead of using continuation marks directly.
2010-08-14 21:34:44 -05:00
collects a hack to work around what appears to be just a wrong way of doing things, but will ask Noel later. 2010-08-14 21:34:44 -05:00
doc added note about ->i and ->* changes 2010-08-13 09:33:52 -05:00
man/man1 A lot of "MrEd" -> "GRacket"s. 2010-05-16 23:46:05 -04:00
src try to fix mangled new-style atomic timeout guard 2010-08-14 13:52:09 -06:00
.gitattributes Don't include git files in archives. 2010-05-12 01:46:05 -04:00
.gitignore Added DrDr house-calls directory to git-ignored files. 2010-06-07 23:00:17 -04:00
.mailmap Add a mailmap entry for Vincent 2010-05-21 16:09:31 -04:00
README Add a generic toplevel README file, make the bundle script use it. 2010-05-18 17:28:44 -04:00

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-enabled 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 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.LIB for more information.