💾 Archived View for freeshell.de › gemlog › 2022-05-25_Whitespace__part_2.gmi captured on 2023-07-22 at 16:27:30. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2022-06-03)
-=-=-=-=-=-=-
I said that abstracting away the white space by writing an assembler would make using Whitespace a bit pointless, but I did it any way. I wish it made it easy to use the language, but it only makes it less painful. To abstract away more pain, I gave the assembler a macro system for including common things like printing a literal string, mallocing some heap, etc. and found that I'd kind-of fixed one of my issues with the language: now there's a way to include library code.
Now that it's a bit easier to write code, I can get more done, but it's still very hard to fix it when it's broken. So I'm having a go at a debugger. There's only one place in the interpreter that's affected much. Before executing an instruction, it has to tell the debugger what's going in. If the debugger doesn't return from that callback, it's a breakpoint.
I wondered about writing a compiler for some high level language. I hope I don't try to do that.