To add to what Jay said...
If you're referring to the "language vs. standard library" distinction:
Racket documents the language(s) and (most of the) library together.
The two most important manuals for this are:
* Guide: http://docs.racket-lang.org/guide/index.html
* Reference: http://docs.racket-lang.org/reference/index.html
If you're referring to`#lang racket/base`: that language is very similar
to the `#lang racket`, and they are documented together in the Guide and
Reference. By default, the documentation applies to both languages.
Occasionally, you'll run across a chapter/section in the Reference that
says something like "The bindings documented in this section are
provided by the racket/port and racket libraries, but not racket/base."
What this means is that you can pull in the `racket/port` module two ways:
#lang racket/base
(require racket/port)
or, if you're making a pretty demonstration of source code, or want to
simplify this for a new programmer:
#lang racket
I always use `#lang racket/base`, since I'm almost always writing
reusable modules, and I'd like for a hypothetical someone reusing the
module in the future to not have to pull in all the `#lang racket`
dependencies.
Neil V.
--
You received this message because you are subscribed to the Google Groups "Racket
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
