hexad

hexad is an esolang designed and published by User:Yayimhere, to be unreliable when trying to store and modify data. it is as such propably not Turing complete, however Yayimhere would be interested in a counter proof of such. hexad uses sextuplets of commands, and as such, it is called hexad.

Syntax

Every command in hexad is a single character, however each program is put into divisions of sextuplets, as mentioned before. If the program cannot properly be divided into sextuplets, the program goes into Undefined behaviour(ie. dont do that).

Commands

hexad uses the below commands, all of which affect the program. for these definitions, the sextuplet a specific command is located in is called the local sextuplet:
.

Within a sextuplet, this is considered "unfilled space", so it functionally is a NOP.

f

Locate any unfilled commands within the local sextuplet, and fill them with the commands of the sextuplet following this one(for example the string f._.d. followed by abcabc would result in the sextuplet fb_adc).

d

Deletes the last command of the local sextuplet. This will cause "flow" from other sextuplets into this one, which as such requires a . be added to the end of the program(and this command does that).

=

Moves the local sextuplet to the end of the command list, without copying it.

c

Copies the sextuplet following the local one to the end of the command list.

_

Add a ? to the end of the program, and then next add the local sextuplet, with the first command removed(which preserves the sextuplet division).

Examples

Sextuplet looping counter:

c.....c.....