The Racket repository
Go to file
Sam Tobin-Hochstadt 865a2cdcbd Support definitions of keyword functions in Typed Racket.
Caveats:
 - keyword function definitions do not define static
   bindings, thus limiting optimization opportunities
 - can't use `define:`, `lambda:`, etc with keywords
 - error messages sometimes expose the implementation
 - the optimizer skips most of the generated code for
   keyword functions definitions (user-level code is
   optimized)
2012-06-02 18:22:07 -04:00
collects Support definitions of keyword functions in Typed Racket. 2012-06-02 18:22:07 -04:00
doc disable nested `#lang' 2012-05-29 11:01:52 -06:00
man/man1 2011 -> 2012 2011-12-31 15:16:59 -05:00
src Solaris 5.10 has poll(), so set try_poll_syscall="yes" in configure 2012-06-03 04:50:06 +08: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.