initial stubs related to error handling device
split configuration options out of Makefiles
nga-c: add internal "interactive" flag to VM state information (#94)
d8888b. d88888b d888888b d8888b. .d88b. 88 `8D 88' `~~88~~' 88 `8D .8P Y8. 88oobY' 88ooooo 88 88oobY' 88 88 88`8b 88~~~~~ 88 88`8b 88 88 88 `88. 88. 88 88 `88. `8b d8' 88 YD Y88888P YP 88 YD `Y88P'
Retro is a modern, pragmatic Forth drawing influences from many sources. It's clean, elegant, tiny, easy to grasp, and adaptable to many tasks.
For most systems (FreeBSD, NetBSD, OpenBSD, macOS, Linux):
You will need a standard C compiler and
Binaries will be placed in the
The primary executable is
retro. This is used for running the
examples and the Atua (gopher) & Casket (http) servers that
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, files, floating point, and more.
retro executable can handle a variety of command line
arguments which are covered in the manpage, but the most common
Starts the listener, a basic REPL for interactive use.
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
retro -i -f filename
This will run the code in the specified file, then start the listener.
Source files for use with
retro are written with code in
commentary here ~~~ code here ~~~
Anything outside the fenced blocks will be ignored.
The primary documentation is in RETRO-Book.md (and the formatted
epub.) Additional notes can be found in the
Visit http(s)://retroforth.org to learn more and follow along with development.
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: