The Racket repository
Go to file
Stephen Bloch 39629e8e99 map-image and map-image/extra now give their function argument x and y
coordinates, or not, depending on the arity of that function.  This
enables one to write a simple function from color -> color and
immediately map it on an image.  For the situation in which the
function is location-dependent, one can still write a function from
x,y,color -> color and map this on the image.
2011-12-02 07:09:37 -05:00
collects map-image and map-image/extra now give their function argument x and y 2011-12-02 07:09:37 -05:00
doc inline map', for-each', andmap', and ormap' 2011-12-01 06:59:27 -07:00
man/man1 removed drscheme man page 2011-04-21 19:38:30 -05:00
src fix bug in cross-module inliner 2011-12-01 14:05:42 -07:00
.gitattributes Don't include git files in archives. 2010-05-12 01:46:05 -04:00
.gitignore Move the lncs ignore into its own directory. 2011-08-06 21:00:53 -04:00
.mailmap Some more bad emails. 2011-08-26 05:26:46 -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.