Brainease is a scripting language that has many similar concepts with brainf*ck, sharing some principal concepts, like memory and instructions. It was created to be a simple and faster language to create, but also to be a language that is easy to read and understand.

  • One instruction per line, long files but shorter width.
  • Syntax highlighting for every IDE that supports highlighting for the R language.
  • Memory management done with a simple, fast and linear memory allocation system.
  • Python-like indentation system - Just two spaces.


brainease is free and open source. You can find the source code on Github and issues and feature requests can be posted on the Github issue tracker. Brainease relies on the community to fix bugs and add features.


The brainease compiler source and his documentation are released under the GPLv3.


Download binary

You can download the brainz binary from the latest release.

There are 4 different OSes available:

To install on other OSes, you can install from cargo or download the source code and compile it yourself.

After, just unzip and use the brainz or brainz.eze file to run your programs. You can also move the binary downloaded into your bin directory.

Then, you can just check your installation:

# Check your installation.
./brainz --version # Or ./brainz.exe if you are on windows

# If you put the binary in your bin directory
brainz --version

Install from cargo

If you have cargo (and rust), you can install brainease for your operating system with:

# Cargo is the Rust package manager.
cargo install brainease

# Check your installation
brainz --version

Install from source

As the brainease interpreter and compiler are written in Rust, to install them from source you need to also have Rust and Cargo installed.

Then, you can just follow these steps:

# Clone the repository
git clone ~/.brainease

# Cd into the repository
cd ~/.brainease

# Build the binary
cargo build --release

# Copy the binary to your bin directory
cp ./target/release/brainz /usr/local/bin/brainz

# Apply the executable permissions
sudo chmod +x /usr/local/bin/brainz

# Check your installation
brainz --version


The syntax of brainease code is similar to batch, because each instruction is in his line of code.

instruction 1
instruction 2
instruction 3
# and so on...

Indentation System

Some instructions may requires his owns inner code, like loop or if. In this case, you can indent them with 2 spaces. No more, no less.

instruction 1
  # This instruction belongs to the instruction 1 above.
  # And may, or may not be executed
  instruction 2

    # And this to the instruction 2.
    instruction 3

  # This still belongs to the instruction 1
  instruction 4

# And this one is outside the instruction 1 indentation scope.
instruction 5

Identifying Pointers, Cells, Numbers and Chars.

Brainease syntactically identifies pointers, cells and values by the following rules:

  • *@ is a raw pointer. It starts at 0 and can be incremented or decremented by the goto instruction.

  • *<number> represents a memory cell. Ex: *2 refers to the cell at the index 2.

  • '<char>' is a character. It supports the \ escape sequence and internally is converted to a number by getting his ASCII code. Ex: 'a' is converted to 97, if needed.

  • <number> is a raw number. Depending on the instruction, it can be used to increment a value, decrement or be a condition.

Learn by example

There are plenty examples at the examples folder. But this simpler one may help you to get started:

# This is a comment
# Empty lines are ignored
# This is also a multi-line comment

# Increments 123 in the current cell
inc 123 in *2

# If the cell 2 is bigger or equal to 120, then print the char 'H' to stdout.
if *2 >= 120
  print 'H'

# This will move the pointer to the right until the pointer
# reaches a cell with a value of 0
loop *@
  goto right

# this is a instruction
inc 123 in *2 # 123 is a raw number and *2 is a memory index

IDE Support

There is a plan to add support for VSCode with an official extension. But until then, you can enable syntax highlighting for your favorite IDE by aliasing all .brain files to the R Programming Language.

Here's an example of brainease code highlighted with R syntax:

print 'A'

inc 1 in *2

# Multi
# Line
# comment

loop *@
  if *2 >= 17 # Some comment

  # Pointer
  save 'a' at *@
  goto left by 3


Brainease has a memory system identical to the brainf*ck language. It simply a two dimensional array of 8 bit integers.

The memory array can have any length, but the default is 30 000, identical to the BF standard. You can change the size of the array before running the program with the -m flag.

This is the exemplified memory for a program run with --memory 5

And you can manipulate with some of the following commands:

# Increments cell 2 by 187
inc 187 in *2

# Moves the pointer to left by 4 cells
goto left by 4


An important and basic concept inherited from the brainf*ck language is the pointer.

A pointer is a special value that can point to a cell in the memory. But, when you change the pointer's value, it will only change to what cell is being pointed to.

Read more about pointer movement.

# Moves the pointer 3 cells to the right
goto right by 3

Cell Overflow

Each cell has the range of 0-255, if you try to increment a cell that overflows the maximum value, the resulting sum will wrapped and the resulting value will be modulo of 256.

# Increments the 3rd cell by 2
inc 3 in *3

Explanation: 254 (+1) -> 255 (+1) -> 0 (+1) -> 1

The same occurs when you try to decrement a cell:

# Decrements the 5th cell by 5
dec 5 in *3

Explanation: 2 (-1) -> 1 (-1) -> 0 (-1) -> 255 (-1) -> 254 (-1) -> 253

Assignment Operators

In brainease, you can assign and change the value of a specific cell with 4 main instructions: inc, dec, save and read.

Incrementing and Decrementing

You can increment or decrement a cell with the inc and dec instructions. They are a 1:1 mapping to brainf*ck with the + and - operators. The only catch is that you can increment or decrement a cell multiple times in a row.

The syntax is pretty simple:

# Syntax:
(inc|dec) <value> in *<cell>
# Increments the cell 2 by 1
inc 1 in *2

# Decrements the pointer cell by 84
dec 84 in *@

You need to be careful, because with these two instructions is pretty easy to overflow a cell. Read more about cell overflow.

Getting ASCII values

To prevent you from programming with a ASCII table on the second monitor, there's a "special" instruction that allows you to save the ASCII value of a character in a specific cell.

This improves the readability of your code when interacting with characters. Because instead of inc 97 in *5, you can just write save 'a' in *5.

# Syntax:
save '<char>' at *<cell>
# Saves the ASCII value of 'a' in the cell 3
save 'a' at *3
# the same as `inc 97 in *3`, but more readable

# Saves the new line character in the cell 6
save '\n' at *6
# the same as `inc 10 in *6`...

Getting values from STDIN

With the default Io Handler implementation, you can read a character from STDIN and save his ASCII value in a specific cell.

To understand better the IO concept and how it works, learn how to handle I/O operations.

# Syntax:
read *<cell>
# Reads whatever is written in STDIN and saves it in the cell 7
read *7

# Reads the next character from STDIN to the current pointer
read *@

Pointer Movement

Sometimes, you'll need the flexibility to read and manipulate data cells without knowing their exact position. For example, you may need to save N cells depending in the size of the provided STDIN input.

The pointer value starts at 0.

This can be managed by the @ (A.K.A pointer) cell index. Anywhere that a cell can be referenced, inc 1 in *1 for example, you can also use the @ pointer. inc 1 in *@ in this example.

You can also move the pointer around with the goto operator.

The goto operator

There are 2 sides to move the pointer and 2 ways for each side.

You can see the dedicated goto instruction page for more details.

# Moves to left by one cell
goto left

# Moves the pointer to the left by 5 cells
goto left by 5

# Moves to right by one cell
goto right

# Moves the pointer to the right by 5 cells
goto right by 5

Pointer overflow

If the pointer is current at a edge cell (i.e. 0 or 29 999), and you move it in the opposite direction, you'll have the pointer overflow effect. It is pretty simple and easy to understand.

Look at this code example:

# This example is using --memory=10 to allocate only 10 cells

write *@ # Pointer is now at the first cell (0)

# Pointer: *0 --- *(Max Memory Size)
# Pointer: *0 -> *9 (Because 0 to 9 is 10 cells)
goto left

write *@ # Pointer is now at the last cell (9)

Loops and Flow Control

⚠️ Documentation in progress. Open an issue if you need help with this topic. See #31

Handling IO

⚠️ Documentation in progress. Open an issue if you need help with this topic. See #31

Increment and Decrement

⚠️ Documentation in progress. Open an issue if you need help with this topic. See #31

Print and Write

⚠️ Documentation in progress. Open an issue if you need help with this topic. See #31

Read and Save

⚠️ Documentation in progress. Open an issue if you need help with this topic. See #31

Move and Swap

⚠️ Documentation in progress. Open an issue if you need help with this topic. See #31


⚠️ Documentation in progress. Open an issue if you need help with this topic. See #31


⚠️ Documentation in progress. Open an issue if you need help with this topic. See #31


⚠️ Documentation in progress. Open an issue if you need help with this topic. See #31


⚠️ Documentation in progress. Open an issue if you need help with this topic. See #31

Programmatically Usage

⚠️ Documentation in progress. Open an issue if you need help with this topic. See #31

Brainf*ck transpiler

⚠️ Documentation in progress. Open an issue if you need help with this topic. See #31

Brainease CLI

⚠️ Documentation in progress. Open an issue if you need help with this topic. See #31


⚠️ Documentation in progress. Open an issue if you need help with this topic. See #31


⚠️ Documentation in progress. Open an issue if you need help with this topic. See #31


⚠️ Documentation in progress. Open an issue if you need help with this topic. See #31


All notable changes to this project will be documented in this file.

[1.0.8] - 2023-06-20


  • Changelog
  • Documentation overhaul
  • Changelog


  • Format first


  • V1.0.8

[1.0.7] - 2023-06-20

Bug Fixes

  • Include correct binary name on releasing
  • Remove deprecated warnings
  • Flush output before reading any input
  • Added break all type
  • Fixed ci


  • Changelog
  • Fixed cname
  • Added pointer movement page
  • Updated documentation page
  • Assignment operators page
  • Updated docs site url
  • Fixed link url
  • Removed margin top
  • Learning section
  • Added install page
  • Updated readme png
  • Formatted license and readme
  • Updated docs sketch
  • Updated readme example
  • Added web server example


  • Tag v1.0.7
  • Added arm version
  • Updated dependencies
  • [breaking] Rename binary into brainz
  • Exit, break and continue
  • Return and exit instructions
  • Allow if with chars
  • Interpret escape characters in print, write and save
  • Allow direct print without saving it in memory

Miscellaneous Tasks

  • Bump env_logger from 0.9.0 to 0.9.1 (#23)
  • Bump clap from 3.1.18 to 3.2.2 (#22)
  • Gitattributes
  • Bump clap-verbosity-flag from 1.0.0 to 1.0.1 (#21)
  • Bump regex from 1.5.4 to 1.5.6 (#20)
  • Updated sponsors
  • Bump clap from 3.1.17 to 3.1.18 (#19)
  • Bump clap from 3.1.15 to 3.1.17 (#18)
  • Bump clap from 3.1.14 to 3.1.15 (#15)
  • Bump log from 0.4.16 to 0.4.17 (#16)
  • Bump clap from 3.1.12 to 3.1.14 (#14)
  • Bump clap from 3.1.10 to 3.1.12 (#13)
  • Bump clap from 3.1.9 to 3.1.10 (#12)
  • Bump clap from 3.1.8 to 3.1.9 (#11)
  • Bump clap from 3.1.6 to 3.1.8 (#10)
  • Bump log from 0.4.14 to 0.4.16 (#9)
  • Bump clap from 3.1.5 to 3.1.6 (#8)
  • Bump lazy-regex from 2.2.2 to 2.3.0 (#7)
  • Allow print! on tests
  • Gitignore
  • Fixed launch config


  • Removed pub mod tests
  • Clippy and Eq imports
  • Minor things
  • Added cli descriptions


  • Refactored some tests
  • If char tests
  • Added transpiler initial unit tests


  • Updated ci to latests versions
  • Fixed docs ci
  • Updated docs CI

[1.0.6] - 2022-03-05

Bug Fixes

  • Fixed integration tests
  • Exit early when parse_line return error
  • Prevent panic when file is not found
  • Clippy
  • Flush output after every instruction loop
  • Extra chars warns even if its only comments


  • Updated readme symlinks
  • Fixed readme example
  • Added examples

Miscellaneous Tasks

  • Use cargo-make for common tasks
  • Add funding.yml
  • Bump clap from 3.1.3 to 3.1.5 (#6)
  • Bump cli to v1.0.4


  • Dedicated struct for instructions
  • Rename binary to brain
  • Move crates under packages/**
  • Change -f to argument
  • Use None when GotoDirection is 1


  • Fixed Rust CI syntax
  • Groupped CI into 3 per-os jobs
  • Fixed ci and updated changelog


  • Updated autocfg


  • V1.0.6
  • V1.0.5

[1.0.4] - 2022-03-01

Bug Fixes

  • Use 30.000 as default memory length
  • Update pointer every loop check
  • Fixed unknown indentation after double indentation block
  • Goto index out of bounds (#2)
  • Write and print output (#2)
  • Wrap pointer if value is the same as memory length
  • Fixed goto capturing group
  • Use @ for pointer as # is a comment :p
  • Handled pointer overflow
  • Fixed comment detection
  • Fixed exponential line_index bug
  • Fixed match_indentation function
  • Fixed infinite loop after indentation ends
  • Fixed multiple indentations bugs


  • Updated hello world example
  • Fixed changelog
  • Added changelog
  • Fixed site url
  • More documentation
  • Added initial docs
  • badge


  • Removed run option after transpilation
  • Cli using new transpiler
  • Transpile cli and subcommands
  • Transpile from brainfuck code
  • Use .brain as file extension (#2)
  • Accept # as pointer
  • Goto instruction
  • [breaking] Integrated if_cell into if
  • [breaking] Require * for cell reference

Miscellaneous Tasks

  • Bump clap from 3.1.2 to 3.1.3 (#5)
  • Clippy code
  • Bump clap from 3.1.1 to 3.1.2 (#4)
  • Bump clap from 3.1.0 to 3.1.1 (#3)
  • Updated debugger
  • Bump clap from 3.0.14 to 3.1.0 (#1)
  • Added debug config for vscode


  • Smaller and faster transpiler
  • Cli paths normalization and result handling (#2)
  • Idiomatic rust code
  • Trace cli arguments
  • Split io_handler into multiple files
  • IoHandler for different IO modes
  • Runtime supports different IOs
  • Better error messages
  • Clippy
  • Updated cli


  • Added integration tests


  • Attach binaries on latest release
  • Updated ci to test all packages
  • Dependabot.yml
  • Added docs action


  • Bump all brainease crates

[1.0.3] - 2022-02-07


  • Add sleep between publishes


  • V1.0.3

[1.0.2] - 2022-02-07


  • Fix publish steps


  • V1.0.2

[1.0.1] - 2022-02-07


  • Added readme
  • Updated license


  • Cli ready
  • Runtime ready
  • Lexer ready
  • Lexer almost ready
  • Added lexer syntax

Miscellaneous Tasks

  • Updated repo structure
  • Updated cargo.toml version
  • Updated hello example and gitignore
  • Some config files


  • Lexer parser
  • Impl FromStr for IfLogic


  • Fixed tests


  • Fix publish steps
  • Cache target directory
  • Renamed actions
  • Fix publish event
  • Unique CI for all packages and publish action
  • Added github ci


  • Init cargo workspace


  • V1.0.1
                   Version 3, 29 June 2007

Copyright (C) 2007 Free Software Foundation, Inc. Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.


The GNU General Public License is a free, copyleft license for software and other kinds of works.

The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change all versions of a program--to make sure it remains free software for all its users. We, the Free Software Foundation, use the GNU General Public License for most of our software; it applies also to any other work released this way by its authors. You can apply it to your programs, too.

When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things.

To protect your rights, we need to prevent others from denying you these rights or asking you to surrender the rights. Therefore, you have certain responsibilities if you distribute copies of the software, or if you modify it: responsibilities to respect the freedom of others.

For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same freedoms that you received. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.

Developers that use the GNU GPL protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License giving you legal permission to copy, distribute and/or modify it.

For the developers' and authors' protection, the GPL clearly explains that there is no warranty for this free software. For both users' and authors' sake, the GPL requires that modified versions be marked as changed, so that their problems will not be attributed erroneously to authors of previous versions.

Some devices are designed to deny users access to install or run modified versions of the software inside them, although the manufacturer can do so. This is fundamentally incompatible with the aim of protecting users' freedom to change the software. The systematic pattern of such abuse occurs in the area of products for individuals to use, which is precisely where it is most unacceptable. Therefore, we have designed this version of the GPL to prohibit the practice for those products. If such problems arise substantially in other domains, we stand ready to extend this provision to those domains in future versions of the GPL, as needed to protect the freedom of users.

Finally, every program is threatened constantly by software patents. States should not allow patents to restrict development and use of software on general-purpose computers, but in those that do, we wish to avoid the special danger that patents applied to a free program could make it effectively proprietary. To prevent this, the GPL assures that patents cannot be used to render the program non-free.

The precise terms and conditions for copying, distribution and modification follow.

                   TERMS AND CONDITIONS
  1. Definitions.

"This License" refers to version 3 of the GNU General Public License.

"Copyright" also means copyright-like laws that apply to other kinds of works, such as semiconductor masks.

"The Program" refers to any copyrightable work licensed under this License. Each licensee is addressed as "you". "Licensees" and "recipients" may be individuals or organizations.

To "modify" a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a "modified version" of the earlier work or a work "based on" the earlier work.

A "covered work" means either the unmodified Program or a work based on the Program.

To "propagate" a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well.

To "convey" a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying.

An interactive user interface displays "Appropriate Legal Notices" to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion.

  1. Source Code.

The "source code" for a work means the preferred form of the work for making modifications to it. "Object code" means any non-source form of a work.

A "Standard Interface" means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language.

The "System Libraries" of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A "Major Component", in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it.

The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work.

The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source.

The Corresponding Source for a work in source code form is that same work.

  1. Basic Permissions.

All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work. This License acknowledges your rights of fair use or other equivalent, as provided by copyright law.

You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright. Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you.

Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary.

  1. Protecting Users' Legal Rights From Anti-Circumvention Law.

No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures.

When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures.

  1. Conveying Verbatim Copies.

You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program.

You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee.

  1. Conveying Modified Source Versions.

You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions:

a) The work must carry prominent notices stating that you modified
it, and giving a relevant date.

b) The work must carry prominent notices stating that it is
released under this License and any conditions added under section
7.  This requirement modifies the requirement in section 4 to
"keep intact all notices".

c) You must license the entire work, as a whole, under this
License to anyone who comes into possession of a copy.  This
License will therefore apply, along with any applicable section 7
additional terms, to the whole of the work, and all its parts,
regardless of how they are packaged.  This License gives no
permission to license the work in any other way, but it does not
invalidate such permission if you have separately received it.

d) If the work has interactive user interfaces, each must display
Appropriate Legal Notices; however, if the Program has interactive
interfaces that do not display Appropriate Legal Notices, your
work need not make them do so.

A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an "aggregate" if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate.

  1. Conveying Non-Source Forms.

You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways:

a) Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by the
Corresponding Source fixed on a durable physical medium
customarily used for software interchange.

b) Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by a
written offer, valid for at least three years and valid for as
long as you offer spare parts or customer support for that product
model, to give anyone who possesses the object code either (1) a
copy of the Corresponding Source for all the software in the
product that is covered by this License, on a durable physical
medium customarily used for software interchange, for a price no
more than your reasonable cost of physically performing this
conveying of source, or (2) access to copy the
Corresponding Source from a network server at no charge.

c) Convey individual copies of the object code with a copy of the
written offer to provide the Corresponding Source.  This
alternative is allowed only occasionally and noncommercially, and
only if you received the object code with such an offer, in accord
with subsection 6b.

d) Convey the object code by offering access from a designated
place (gratis or for a charge), and offer equivalent access to the
Corresponding Source in the same way through the same place at no
further charge.  You need not require recipients to copy the
Corresponding Source along with the object code.  If the place to
copy the object code is a network server, the Corresponding Source
may be on a different server (operated by you or a third party)
that supports equivalent copying facilities, provided you maintain
clear directions next to the object code saying where to find the
Corresponding Source.  Regardless of what server hosts the
Corresponding Source, you remain obligated to ensure that it is
available for as long as needed to satisfy these requirements.

e) Convey the object code using peer-to-peer transmission, provided
you inform other peers where the object code and Corresponding
Source of the work are being offered to the general public at no
charge under subsection 6d.

A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work.

A "User Product" is either (1) a "consumer product", which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling. In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, "normally used" refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product. A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product.

"Installation Information" for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made.

If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information. But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM).

The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed. Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network.

Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying.

  1. Additional Terms.

"Additional permissions" are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law. If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions.

When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it. (Additional permissions may be written to require their own removal in certain cases when you modify the work.) You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission.

Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms:

a) Disclaiming warranty or limiting liability differently from the
terms of sections 15 and 16 of this License; or

b) Requiring preservation of specified reasonable legal notices or
author attributions in that material or in the Appropriate Legal
Notices displayed by works containing it; or

c) Prohibiting misrepresentation of the origin of that material, or
requiring that modified versions of such material be marked in
reasonable ways as different from the original version; or

d) Limiting the use for publicity purposes of names of licensors or
authors of the material; or

e) Declining to grant rights under trademark law for use of some
trade names, trademarks, or service marks; or

f) Requiring indemnification of licensors and authors of that
material by anyone who conveys the material (or modified versions of
it) with contractual assumptions of liability to the recipient, for
any liability that these contractual assumptions directly impose on
those licensors and authors.

All other non-permissive additional terms are considered "further restrictions" within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying.

If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms.

Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way.

  1. Termination.

You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11).

However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation.

Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice.

Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10.

  1. Acceptance Not Required for Having Copies.

You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so.

  1. Automatic Licensing of Downstream Recipients.

Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License. You are not responsible for enforcing compliance by third parties with this License.

An "entity transaction" is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations. If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts.

You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it.

  1. Patents.

A "contributor" is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. The work thus licensed is called the contributor's "contributor version".

A contributor's "essential patent claims" are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version. For purposes of this definition, "control" includes the right to grant patent sublicenses in a manner consistent with the requirements of this License.

Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version.

In the following three paragraphs, a "patent license" is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement). To "grant" such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party.

If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements of this License, to extend the patent license to downstream recipients. "Knowingly relying" means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipient's use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid.

If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it.

A patent license is "discriminatory" if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007.

Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law.

  1. No Surrender of Others' Freedom.

If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not convey it at all. For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program.

  1. Use with the GNU Affero General Public License.

Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU Affero General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the special requirements of the GNU Affero General Public License, section 13, concerning interaction through a network will apply to the combination as such.

  1. Revised Versions of this License.

The Free Software Foundation may publish revised and/or new versions of the GNU General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.

Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of the GNU General Public License, you may choose any version ever published by the Free Software Foundation.

If the Program specifies that a proxy can decide which future versions of the GNU General Public License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Program.

Later license versions may give you additional or different permissions. However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version.

  1. Disclaimer of Warranty.


  1. Limitation of Liability.


  1. Interpretation of Sections 15 and 16.

If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee.


        How to Apply These Terms to Your New Programs

If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.

To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found.

A brainf*ck-style programming language, but readable
Copyright (C) 2022  Arthur Fiorette

This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with this program.  If not, see <>.

Also add information on how to contact you by electronic and paper mail.

If the program does terminal interaction, make it output a short notice like this when it starts in an interactive mode:

Brainease  Copyright (C) 2022  Arthur Fiorette
This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.

The hypothetical commands show w' and show c' should show the appropriate parts of the General Public License. Of course, your program's commands might be different; for a GUI interface, you would use an "about box".

You should also get your employer (if you work as a programmer) or school, if any, to sign a "copyright disclaimer" for the program, if necessary. For more information on this, and how to apply and follow the GNU GPL, see

The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. But first, please read