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 5fe2d7b591 examples: html export now recognizes floating point numbers
FossilOrigin-Name: c9e73034a106b924ac68f01e86e11180b3a87522ae94414f9e2afbe6c32035cb
2019-12-30 15:11:08 +00:00
doc glossary: mark as{ and }as as deprecated 2019-12-11 18:27:26 +00:00
example examples: html export now recognizes floating point numbers 2019-12-30 15:11:08 +00:00
image retro.forth: remove use of a variable in a:contains? and a:contains-string? 2019-12-23 15:52:19 +00:00
interface interfaces: various updates 2019-12-09 19:37:26 +00:00
man retro-describe: update man page 2019-12-18 13:52:22 +00:00
package rename package/list to package/list.forth 2019-11-21 18:57:55 +00:00
security initial preparations for 2020 releases 2019-11-18 20:38:40 +00:00
tests add a few more tests 2019-10-14 20:12:56 +00:00
tools retro-document: final result of performance work: reduced the glossary generation for 106 examples from 31m52s to 13m22s (a 58% decrease) 2019-12-16 21:14:08 +00:00
vm vm/nga-c-no-libc: drop WIP support for OpenBSD as future OpenBSD releases will require syscalls to be routed through libc. Ref thread: https://www.mail-archive.com/tech@openbsd.org/msg54429.html 2019-12-27 13:58:31 +00:00
LICENSE begin use of .retro instead of .forth 2019-06-28 14:17:50 +00:00
Makefile fixes to Makefile 2019-12-13 19:43:00 +00:00
ngaImage retro.forth: remove use of a variable in a:contains? and a:contains-string? 2019-12-23 15:52:19 +00:00
README begin use of .retro instead of .forth 2019-06-28 14:17:50 +00:00
RELEASE-NOTES update the native image source; lcm example 2019-12-24 16:03:42 +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 proprietary versions of RETRO for iOS and macOS.
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

The macOS application is also availble for free, though the
source is not published.

Proceeds from these are used to pay for various project related
expenses (servers, domains, hardware upgrades, and an
occasional cup of tea).

## 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.