Talk:Opcode

From Esolang
Jump to navigation Jump to search

Suggestion on language definition

Currently the language definition says that it converts the original code to a brainfuck equivalent and then runs it. This is because I found defining Opcode 6 and Opcode 7 very hard. For example, Opcode 1 can just refer to print the ascii value of current memory pointer value. But same cannot be done with the last 2 opcodes as easily as you can define [ and ] for bf. -- pptx704 (talk) 23:11, 22 March 2022 (UTC)

Figured out the definition. Removed BF dependencies by adding the existence of a 2D command array -- pptx704 (talk) 10:42, 23 March 2022 (UTC)