The Racket repository
Go to file
Stephen Bloch ba8684cb63 provide provide, so it's possible to use provide and require in
student languages.  This will be a problem if somebody writes a
function in BSL or BSLLA, provides it, requires it in a non-student
language, and uses it as an argument to a higher-order function
that isn't declared as a "higher order primitive".  That is,
not very often.  Even if so, just re-open the BSL or BSLLA source
file, switch languages to ISL, save it, and the problem goes away.
2012-04-24 06:37:51 -04:00
collects provide provide, so it's possible to use provide and require in 2012-04-24 06:37:51 -04:00
doc updated release notes, please add to 5.3 release 2012-04-19 16:26:43 -07:00
man/man1 2011 -> 2012 2011-12-31 15:16:59 -05:00
src New Racket version 5.3.0.2. 2012-04-20 03:40:48 -04:00
.gitattributes Don't include git files in archives. 2010-05-12 01:46:05 -04:00
.gitignore Remove erroneous file, and add an ignore rule for it. 2012-02-17 09:09:21 -05:00
.mailmap Mailmap mapping for dvanhorn. 2012-02-29 00:33:07 -05:00
README 2011 -> 2012 2011-12-31 15:16:59 -05: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-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.