Wait, is someone saying they wrote a C compiler in brainfuck, rather than the other way around? As I understand, the normal route when developing a new architecture is to first write an assembler in machine code, then write a C compiler in assembly, and go from there.
Name:
Anonymous2016-06-06 20:53
>>8 I think somebody made a (subset of) C to BF compiler, so in theory shit like compilers can be ported to Brainfuck.
>>1 FUCKING DIE with your BROKEN FUCKING REDDIT links. Why in all the shit didn't you just link to THE GODDAMNED REAL LINK https://speakerdeck.com/nineties/creating-a-language-using-only-assembly-language instead of the FUCKING USELESS reddit page that has ONLY THE FUCKING PAGE TITLE of the actual content included? GODAMNIT PEOPLE LIKE YOU NEED TO BE SHOT IN THE FUCKING FACE
Also, we did shit like this when we were kids in the 80s. You're entirely too easily impressed.
Name:
Anonymous2016-06-06 22:25
>>8 C is deprecated. All new architectures must come with an Oberon compiler.
Name:
Anonymous2016-06-06 22:45
>>10 Is there an Oberon compiler that respects my freedoms?
The dude starts from a hex to binary converter written in raw machine code (well, hex-encoded), then proceeds to add whitespace, comments, one letter labels, forward labels, suddenly a minimal statically compiled forth-like, and two C like languages. He actually skipped the symbolic assembly entirely.