@neauoire the good stuff
Conversation
Notices
-
minute (mntmn@mastodon.social)'s status on Saturday, 22-Apr-2023 06:10:52 JST minute -
Devine Lu Ator (neauoire@merveilles.town)'s status on Saturday, 22-Apr-2023 06:10:55 JST Devine Lu Ator Assigning a type to a label(just a suffix extension in this case) allows me to display its content in whichever way I need(as opcodes, as letters, as hex bytes, or ..)
-
Devine Lu Ator (neauoire@merveilles.town)'s status on Saturday, 22-Apr-2023 06:10:59 JST Devine Lu Ator (the code formatting in the video is all messed up, it's the first time that I manage to connect all 3 parts of together and I was too excited to bother fixing up the syntax parser)
The two hexadecimal editors are:
- left: a rom file(binary blob with the bytecode)
- right: a symbols file(label names and comments) -
Devine Lu Ator (neauoire@merveilles.town)'s status on Saturday, 22-Apr-2023 06:11:03 JST Devine Lu Ator So a few days I've realized that I very much liked working using structured editing.
Structured editing means that your editor is aware of the program's functioning enough that it handles how it should be presented, so you're not editing text as much as the underlying structure of the program.
It's just a fancy way of saying that it's basically just a symbols aware disassembler.
I've spent the past 2 days improving the UX so I could run the reassembler without going through the terminal.
-
Devine Lu Ator (neauoire@merveilles.town)'s status on Saturday, 22-Apr-2023 06:11:07 JST Devine Lu Ator I've been changing my workflow these past few days from working with textual sources, to using something called structured editing.
Normally you'd think of a program as source code made of text, but in structure programming, you edit the symbols of the program, in this case the bytecode, labels and comments.
I use the textual representation when saving my work, so it can be versioned, but while working anything that is not a bytecode, a symbol or a comment is not recorded.
-