Retro is a modern, pragmatic Forth drawing influences from many sources. It's clean, elegant, small, easy to grasp, and adaptable to many tasks.
Find a file
crc a1311ef299 examples: add retro.retro (for issue #7)
FossilOrigin-Name: baae765aef43bc284e824b2490ca0c62bf819dd664a5ba899ca1cd1d2513e911
2020-10-01 17:15:32 +00:00
doc toolchain: move generate-epub.retro to tools/, fix make-book.retro 2020-10-01 16:53:52 +00:00
example examples: add retro.retro (for issue #7) 2020-10-01 17:15:32 +00:00
image add an example for the new words in retro-unix 2020-09-11 14:55:23 +00:00
interface docs: add missing entries to glossary 2020-10-01 13:45:20 +00:00
man update retro-unu manpage to add a note on the code & test block syntax 2020-06-09 12:57:32 +00:00
package fix more uses of deprecated names 2020-10-01 13:28:46 +00:00
security update signing keys for next releases 2020-09-03 19:16:10 +00:00
tests fix remaining uses of deprecated names as reported 2020-09-30 23:48:03 +00:00
tools toolchain: move generate-epub.retro to tools/, fix make-book.retro 2020-10-01 16:53:52 +00:00
vm docs: add missing entries to glossary 2020-10-01 13:45:20 +00:00
LICENSE copyright year = 2020 2020-02-14 21:36:21 +00:00
Makefile housekeeping: rename some files in tools; remove an unused toolchain item 2020-09-21 17:51:59 +00:00
ngaImage add an example for the new words in retro-unix 2020-09-11 14:55:23 +00:00
README retro.py: fix bug in i_fe() that was misreporting the stack depth (fixes dump-stack, as reported by Scott McCallum) 2020-09-18 12:03:40 +00:00
RELEASE-NOTES examples: add retro.retro (for issue #7) 2020-10-01 17:15:32 +00:00

## RETRO FORTH

RETRO is a modern, pragmatic Forth drawing influences from many
sources. It's clean, elegant, tiny, and easy to grasp and adapt
to various uses.

Features:

- Open Source (ISC License)
- Portable (runs on a MISC-style virtual machine)
- Small source & binaries
- Builds into a single, self contained binary for easy deployment
- Sources in literate format, using a Markdown variant

## Quick Start

For most systems (FreeBSD, NetBSD, OpenBSD, macOS, Linux):

    make

You will need a standard C compiler and `make`.

## Executables

Binaries will be placed in the `bin` directory.

The primary executable is `retro`. This is used for running the
examples and the Atua (gopher) & Casket (http) servers that
power forthworks.com.

The `retro` executable embeds the image into the binary, making
it trivial to copy and deploy.

This interface layer also extends the language with many new
words and vocabularies, adds scripting, file i/o, gopher, and
floating point math support.

The `retro` executable can handle a variety of command line
arguments:

    retro -i

Starts the *listener*, a basic REPL for interactive use.

    retro filename

This will run the code in the specified file, then exit. This
is also used to run programs as shell-type scripts using a
header line like `#!/usr/bin/env retro`.

    retro -i -f filename

This will run the code in the specified file, then start the
listener.

    retro -h

Displays a summary of the command line arguments.

Source files for use with `retro` are written with code in
fenced blocks:

    commentary here
     
    ~~~
    code here
    ~~~

Anything outside the fenced blocks will be ignored.

## Documentation

The primary documentation is in RETRO-Book.md (and the formatted
RETRO-Book.html.) Additional notes can be found in the `doc`
directory.

## Commercial Versions

I provide versions of RETRO for iOS and macOS via the Apple app
stores. These use a custom, dual pane editor-based environment
and some platform specific words and extensions. They do use the
same image and virtual machine as `retro`, `retro-repl`, etc.

iOS:   https://itunes.apple.com/us/app/retro-forth-12/id1170943580?ls=1&mt=8

macOS: https://itunes.apple.com/us/app/retro-forth/id1317494014?ls=1&mt=12

## Alternative Implementations

This source tree includes additional implementations in C#,
JavaScript, Pascal, and Python. These are not officially
supported, but are provided for your use if the C
implementations will not suffice.

## Patreon

I have a Patreon at https://www.patreon.com/_crc for those that
want to financially support development. All funds raised via
Pateron are put into development related expenses (server expenses,
app store fees, hardware).

Thanks go out to my current and past patrons:

- Kiyoshi YONEDA
- Krinkleneck
- Rick
- Scott MCCallum