bluesun212/dijon

An imperative, stack-oriented esoteric programming language with highly non-traditional control flow constructs

Dijon

An imperative, stack-oriented esoteric language with highly non-traditional control flow constructs

Introduction

Dijon is a language that I initially came up with in 2013. The original design goal was to create a language with a unique way to handle control flow; in fact, the original vision was to attempt to create a language without loops, if statements, and GOTOs. The design has gone through many iterations since then, but this is the first completely implemented version. Between 2019 and 2022, 3 Java versions and 2 Python versions of the interpreter were created, each slightly fleshing out the language and its implementation. The heart of Dijon is the way it handles memory using both a stack and variables. However, variables also influence the control flow using a concept called triggers, which are sections of code that execute when the trigger's variable's value is requested. Variables can be declared in these triggers and are scoped inside them. Programs may import and use triggers and variables from other files as well, most importantly the standard library.

Documentation

Please see the following links to view the language reference, code examples, and future plans.

• Reference
• Standard Library
• Examples
• Future features

Implementation

Please see the reference interpreter, PyDijon, which is written in Python.

dijon's Issues

Standard library tests

Once the standard library is finished, a Dijon file as well as a Python file should be created to test each function in the standard library.

Improve REFERENCE.md

The wording in the language reference needs work. In addition, more needs to be written about imports and the builtins.

Finish the standard library

More functions need to be added to the standard library, many of which are documented in the file itself.

Examples improvements

More examples need to be created. In addition, a readme needs to be added to the examples folder.

Create the standard library documentation

The file STD_LIBRARY.md needs to be fully written, which should document the features of std.dij, as well as how to use them.

Tutorial

There needs to be a tutorial, or at least a collection of runnable code snippets that demonstrate how the language works, and individual features that can be used.