b2piet is an optimising Brainfuck to Piet
transpiler written in Ocaml.
Currently one painting style is supported:
The following program prints a Sierpinski triangle to depth 5 (converted from Daniel Cristofani's program):
You can test it online using npiet.
You can also check out this animation of running Towers of Hanoi (converted from Clifford Wolf's code).
(I can't share the generated program as Imgur won't let me upload a 131080x44 image, even though it is only 80 kB in size. If you do generate it locally, it might be fun to test which image viewers you can crash with it. For me, GIMP and Shotwell worked fine whereas Pinta and Eye of Gnome crashed.)
This will mimic Piet Mondrian's tableau. The colouring part is not yet ready, so I don't have anything to show here...
Thanks to all the developers of our dependencies, and folks answering questions on StackOverflow, IRC and Reddit. Special thanks to the authors of Cmdliner and Qcheck for having especially nice documentation 😄, @aantron for helping me out with Lwt, and to the authors of Merlin, which makes programming in Ocaml a pleasure 😍.
Lastly, thanks to the authors of Real World Ocaml for distributing their book freely online.
Pick your favourite tagline:
Fast, correct and beautiful - pick 3.
Postmodern multifunctional cybergraffiti.
Unattractive Turing completeness considered harmful. (sorry)
The program has only been tested on Ubuntu 16.04 and 17.04. Ideally, it should work on other GNU/Linux distributions, *BSD and macOS as is. It will probably not work on Windows.
See Issues if you want support added for your platform.
By default, b2piet will only be able to produce .ppm and .bmp images.
For very large images, the file size will quickly become large if you use .ppm
files.
So it is strongly suggested that you install an external library to be able to
save images as .png files. The appropriate dependency name can be found
in the camlimages's installation instructions here.
This dependency is currently listed as libpng, which you can install through
your distribution's package manager.
You will need a working installation of Ocaml version
v ≥ 4.03.0.
Instructions for installing Ocaml can be found on ocaml.org.
Now clone this repository and run make depends:
# Install libpng using your package manager
git clone https://github.com/theindigamer/b2piet.git
cd b2piet
make depends
make depends uses OPAM (OCaml Package Manager) to install packages.
OPAM itself should have been installed when you installed OCaml.
This takes care of the OCaml dependencies.
You will also need fpiet if you want to run tests (see Testing output).
The fpiet binary should be placed in the project's root directory.
Just run make while inside the b2piet directory.
This will create a file b2piet.byte which you can use.
If you want a native file too (runs much faster but slower to compile),
run make all instead of make.
Run ./b2piet.byte --help or ./b2piet.native --help to see full descriptions
for the commandline flags.
Usage examples are given near the end; you might want to read those first and
get back to the flag descriptions later in case you need them.
For simple programs, you can test the Piet output online using Erik Schoenfelder's interpreter npiet.
Larger programs will need a lot more steps than the website supports,
so it is suggested that you have a Piet interpreter locally and run it in the
terminal.
Matthias Ernst's fpiet works well; it is much faster then npiet.
Once you have a binary for fpiet, you can check the output using
./fpiet a.png (similarly for npiet).
Note: fpiet does not work with the .ppm files generated by b2piet
as the former accepts ASCII ppm (P3) whereas the latter emits binary ppm (P6).
If you insist on using .ppm files, you can use npiet
(either online or offline) which accepts binary ppm,
or you can add a conversion step (note: requires imagemagick)
before running fpiet:
./b2piet.byte --output=foo.ppm foo.b
convert foo.ppm foo.png
./fpiet foo.png # works
# ./fpiet foo.ppm # doesn't work
# ./npiet foo.ppm # works
NOTE: Before opening an issue, please search if the same issue was reported earlier. By default, Github only searches through open issues. However, you should double-check closed issues as well before submitting a new one.
→ Open an issue on the issue tracker.
→ Open an issue on the issue tracker.
→ Open an issue on the issue tracker.
→ Submit a bug report on the issue tracker.
If it makes sense to use the --stack-auto flag (see ./b2piet.byte --help),
then try doing that and check the output.
If it still doesn't work,
try using larger stack sizes manually up to the limit of 30000.
If it still doesn't work, or runs way longer than is expected
(this is likely to happen when the stack size is very large,
and especially when the codel size in pixels is larger than 1),
please submit a bug report on the issue tracker.
→ Submit a bug report on the issue tracker.
++++++++[>+++++++>+++++++++++++>+++++++++++++++<<<-]>++.>--.>---.<<.<.
No worries, the issue tracker can handle meta-issues as well.
Fill out the issue template -- you will see this when you create a new issue -- as appropriate.
See Contributing.
- design.md gives a rough description of the internals.
- tableau.md describes the overall layout for tableau.
- loops.org shows how arbitrary loops are constructed.
- See comments in the source code or generate documentation from documentation
comments using
make docand openingb2piet.docdir/index.htmlin your browser.
- I found a small
bug
in the
batteries-includedstandard library while working on this project. Yay!
Um, didn't you learn the following in school?
Cain is for Charlie, and Delta is for Cain,
and BravoFoxtrot is for Befunge, and Bravo is for Brainfuck.
Possible passive use cases include but are not restricted to:
- Your device wallpaper, to remind yourself how nerdy you are.
- A poster inside your house to wow your imaginary guests.
- A fancy nameplate outside your house to throw off your real postman.
Possible active use cases include:
- Smart wallpaper that records conversations.
- Beautiful Skynet.
- Anything you can think of! After all, Brainfuck is Turing complete 😄.
_____________________
< Thanks for reading! >
---------------------
\ ^__^
\ (oo)\_______
(__)\ )\/\
n ||----w |
|| ||