The Racket repository
Go to file
Matthew Flatt 09eab9c3eb fix JIT problem that can break futures
A recent (weeks-old) JIT change set one of a function's code
 pointers to NULL to indicate that JIT-compilation of the
 function is in progress, but that breaks futures. Set the
 code pointer to a different not-yet-ready function, instead.

 Merge to 5.1.2

 Closes PR 12037
2011-07-11 07:01:41 -06:00
collects Fixed some more error messages. 2011-07-11 07:25:46 -04:00
doc add `port-set-next-location!'; make prompt read handler use it 2011-07-10 08:36:47 -06:00
man/man1 removed drscheme man page 2011-04-21 19:38:30 -05:00
src fix JIT problem that can break futures 2011-07-11 07:01:41 -06:00
.gitattributes Don't include git files in archives. 2010-05-12 01:46:05 -04:00
.gitignore Add TAGS files to .gitignore. 2011-01-24 17:00:56 -05:00
.mailmap Two more names to the pile 2011-06-23 05:49:22 -04:00
README Switch the license text from LGPLv2 to LGPLv2.1. 2011-05-27 18:09:55 -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-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.