A scripting language.

To learn about the language, visit pyret.org.

To read an introduction of the language, visit the tour.

To read the documentation, visit pyret.org/docs/.

There are two main ways to use Pyret:

1. If all you want to do is program in Pyret, there is a web-based environment at code.pyret.org that lets you run and save programs that should be all you need. If you're a student using Pyret, this is probably where you will do your assignments, for example.

2. If you want to develop Pyret, or install it for use at the command line, the README starting below is for you.

The use of vocabulary from http://reservationsbvi.com/thisoldpirate/glossary.html is recommended when commenting and reporting issues.

Installing

First, make sure you've installed Node >= 0.10. Then run:

$ make install && make && make test

It'll build the Pyret compiler and run the tests.

Running Pyret

If you just want to run Pyret, visit the online environment and work from there. If you're interested in Pyret development, read on:

The easiest way to run a Pyret program from the command-line is:

$ node build/phaseX/main-wrapper.js <path-to-pyret-program-here>

Where X is a number from 0-3, indicating a phase (described below).

Phases

Pyret is a self-hosted compiler, which means that building requires some thought. If you're going to get into the guts of the compiler, a brief overview is worth reading. The build directory is separated into four distinct phases.

1. Phase 0 is a standalone JavaScript file that contains an entire compiled Pyret compiler and runtime. This large blob gets committed into version control whenever we add a nontrivial feature to the language. It is large and somewhat slow to load, but whatever is in build/phase0/pyret.js is currently the canonical new-world implementation of Pyret.

2. Phase 1 is set up to be populated with built versions of all the files for the compiler, built by the phase 0 compiler. Phase 1 is what most of the testing scripts run against, since it is the easiest to create, and after it is built it is your development snapshot of the compiler you're working on. However, just building phase1 is not enough to fully re-boostrap the compiler, because it contains a mix of old-compiler output and any new changes that were made to runtime files.

3. Phase 2 is set up to be populated with built versions of all the files for the compiler, built by the phase 1 compiler. This version does represent a fully-bootstrapped compiler. If you run make standalone2, you get a new standalone compiler in the same format as build/phase0/pyret.js.

4. Phase 3 builds from phase 2. One major use of phase 3 is to check the bootstrapped compiler from phase 2. Before committing a new standalone in phase 0, build both standalone2 and standalone3, and check:

   $ diff build/phase2/pyret.js build/phase3/pyret.js
   

   And it should be empty, which indicates that the bootstrapped compiler is at least correct enough to recompile itself without error.

   To rebuild the compiler and get a new phase0, run

   $ make new-bootstrap
   

   which will build the phase2 and phase3 standalones, check the diff, and copy to phase0 if the diff is empty.