dloscutoff / esolangs

Miscellaneous esoteric programming languages.

DLosc's Esolangs

This repository is home to various esoteric programming languages that weren't big enough to get their own repositories.

Acc!!

A Turing tarpit with a looping construct, integer math, and a single accumulator.

Github | Try It Online | Origins

BitCycle

A 2D language that involves moving bits around a playfield: picture a cross between ><> and Bitwise Cyclic Tag.

Github | Esolangs wiki | Try It Online | JavaScript intepreter

Exceptionally

A language that uses exceptions for control flow, inspired by the ? operator from Whython.

Github | Attempt This Online | Origins

Ouroboros

Each line of code is a loop, which can be shortened or lengthened to achieve control flow.

Github | Esolangs wiki | JavaScript intepreter | Origins

Regenerate

Generate strings using regular expression syntax.

Github | Attempt This Online | Replit

Sisi

A toy language inspired by BASIC.

Github | Try It Online | Origins

tinylisp

A minimalist Lisp dialect with a fairly decent standard library.

Github | Try It Online | Origins

esolangs's Issues

ahmedbboy

Regenerate: the `!` operator is undocumented

In Regenerate's documentation, ! is only listed as a metacharacter that needs to be escaped, but isn't documented any further than that.

In its source code, it is described as Like alternation, but stop trying other options as soon as we find one that works. But what does "one that works" mean? And what is the order of precedence when both | and ! are used?

I found a way to use ! successfully in Print all integers. But I don't quite understand exactly why it works. Why does 0|($2[0-9]!-?[1-9]())+ generate all integers, but neither 0|($2[0-9]|()-?[1-9])+ nor 0|([0-9]$2|-?[1-9]())+ nor 0|($4($3[0-9]![1-9]())!-?()){2,} do?

tinylisp interpreter improvements

This is a list of small improvements for the tinylisp interpreter. This issue will not be closed; instead, new improvements will be edited in and completed ones crossed off. Please use a separate issue for library improvements.

• Suppress output of top-level d calls (but not in repl mode)
• Add version of load that doesn't suppress output (maybe run?)
• Convert REPL commands (help), (restart), and (quit) to builtin macros only available at top level
• Make tail-call elimination work with any alias of i
• Make tail-call elimination work with v (or any alias)
• Experiment with implementing lists as nested 2-tuples instead of Python lists--may improve memory- and time-efficiency

how to print?

how to print? (in tinylisp)

tinylisp: improve library functions

This is a list of library functions whose efficiency or robustness could be improved. This issue will not be closed, at least in the short term; instead, new improvements will be edited in and completed ones crossed off.

• Swap operands of mul2 to make the smaller one govern the loop count
• Rewrite mul2 to use a binary-based algorithm instead of decreasing by 1 each time
• Add type-checking, where this can replace unhelpful error messages with more helpful ones

tinylisp: Optional `else` on the end of `i`?

In this suggestion, something like this will work:

(d x 20)
(i (e x 20) x)

Whereas in the current version of tinylisp, an else statement must be added.