News for hackers. Stuff that matters.

A comment on I wrote a Brainfuck to Go compiler.

Re:I wrote a Brainfuck to Go compiler by lifthrasiir on Tuesday June 07, 2022 @02:29AM (#31650545)
Meanwhile, a Go to Brainfuck compiler remains uncharted territory.

(If you are genuinely curious, there is already a BASIC-to-Brainfuck compiler [1] and a C-to-Brainfuck compiler [2].)

[1] https://esolangs.org/wiki/BFBASIC

[2] https://esolangs.org/wiki/C2BF (and I think I've seen at least two more)

[ Parent | on HN ]
Re:I wrote a Brainfuck to Go compiler by selcuka on Tuesday June 07, 2022 @03:01AM (#31650758)
> a Go to Brainfuck compiler remains uncharted territory.

Not at all... Just compile your Go code to WebAssembly [1], then to C [2], and finally to BF [3].

[1] https://binx.io/2022/04/22/golang-webassembly/

[2] https://webassembly.github.io/wabt/doc/wasm2c.1.html

[3] https://esolangs.org/wiki/C2BF

[ Parent | on HN ]
Re:I wrote a Brainfuck to Go compiler by scrame on Tuesday June 07, 2022 @04:39AM (#31651422)
The real brainfuck is in the toolchain.
[ Parent | on HN ]
Re:I wrote a Brainfuck to Go compiler by panda88888 on Tuesday June 07, 2022 @03:32PM (#31659051)
I wonder how the code would look like if we compile the resulting BF code back to Go with the posted compiler.
[ Parent | on HN ]
Re:I wrote a Brainfuck to Go compiler by selcuka on Tuesday June 07, 2022 @09:19PM (#31662140)
You will probably want to go back to BF instead.
[ Parent | on HN ]