Like yoob, yoob.js:
- provides a set of components for implementing visual interpreters for esoteric programming languages (esolangs).
- is written amateurishly.
- has an API that is not particularly good, finalized, or stable.
- will ship with some public-domain implementations of some esolangs (but the approach is different from yoob's; see below.)
Unlike yoob, yoob.js:
- extends the idea of "a component to help implement an esolang" to encompass esolang implementations themselves. So, for example, yoob.js might include an implementation of brainfuck, but this would not be provided solely as an "end implementation" but also as a component for implementing other brainfuck-derived esolangs, and other mashups.
- is not limited to providing support for esolang interpreters; it might be better described as a set of components for implementing esolangs "and other bizarre things".
- does not support unbounded integer values (yet; see "Planned", below).
- will provide components which are meant to be used as starting points for
further modification. (It's all public domain, so build on it!) For
yoob.Parseris meant to be adapted to your specific grammar.
Other things you should know about yoob.js are that it:
- requires features from HTML5 and related "modern" web standards. It does not try to do any feature detection or polyfilling. If it doesn't work in your browser, it doesn't work in your browser. Try another browser.
- does not rely on jQuery (yet) (possibly to its detriment.)
- does not come minified or agglomerated or anything. I mean, this isn't
production web development, we're not trying to optimize page load time
here, we just want to run us some esolangs, right? You're free to do
this yourself. May we suggest
cat yoob/*.js > yoob.js? (Note: there will probably one day be a small script to do this sort of thing for you, more intelligently, respecting dependencies and whatnot.)
Each yoob.js class is defined in its own
.js file, and each
inserts the class it defines into the
yoob namespace (which it will create
as a new, empty, global namespace if it has not already been defined.)
The classes are currently:
A two-dimensional Cartesian grid of values which dynamically expands as needed. It can be associated with a
<canvas>element, on which it will be depicted, which will also dynamically expand as needed. Objects of this class should be suitable for representing programs in two-dimensional esolangs such as Befunge, as well as cellular automata.
A pointer (position vector) into two-dimensional Cartesian space (typically a
yoob.Playfield) which also has a delta (direction vector) which need not necessarily be used.
A crude simulation of a text-based addressable console on a
<canvas>element. Not recommended for serious use; mainly intended to provide a sort of retro feel to input and ouput.
A crude simulation of a buffer into which the user can type a line of text. Typically it is associated with a
yoob.TextConsoleobject, on which the text is displayed as the user types it.
A (theoretically) unbounded tape, like you'd find on a Turing machine, optionally associated with a
<canvas>on which it is depicted.
An object representing a position on a Tape.
An object implementing a push-down, first-in-first-out stack of values, optionally associated with a
<canvas>on which it is depicted.
A simple, inefficient lexical analyzer, parameterized with a table of regexps (TODO). Can also serve as a starting point for writing your own simple, inefficient lexical analyzer.
A recursive-descent parser, using
yoob.Scanner, intended to be copied and adapted for your specific needs. TODO: put these sort of classes in someplace other than
egdoesn't seem quite right, as that's for examples of using yoob.js. Maybe
An AST (Abstract Syntax Tree) is a type identifier (String), an optional value (of any type), and an array of zero or more children ASTs.
A List is either an atom (String) or a pair of a List and a List.
A Term is either an atom (String) or a variable (String in a special namespace), plus an array of zero or more children Terms. Should include facilities for matching and unification.
For Turtle Graphics.
unbounded integer support