3 ms·
Honestly, when I'm writing assembly code, my "IDE" is a notebook and pencil. Narrowly ruled paper, so that I can squeeze a lot of lines in, with a line drawn d
by groovy2shoes 10y ago
Honestly, when I'm writing assembly code, my "IDE" is a notebook and pencil. Narrowly ruled paper, so that I can squeeze a lot of lines in, with a line drawn down the middle so that I get two columns: the left column has my code, and the right column holds commentary.
I first started writing code in notebooks due to necessity (I grew up in a poor family, and though I had access to many outdated programming books at my local library, I rarely had access to a computer), but I keep doing it nowadays because it's utterly distraction-free, and being able to scribble notes and diagrams in the code is often convenient.
For assembly language especially, I find the two-column format indispensable. Even when I got to university and took an assembly language class, I would write all my assignments in vim with soft tabstops set to the middle of the screen[1], so that after each instruction, I could hit tab and my cursor would instantly be at the second column for commentary. I know emacs can do something similar, because I managed to get it stuck on in lisp-mode before, and couldn't figure out how to turn it off! :)
[1]:
au FileType asm setlocal sts=38 et " GNU as
au FileType nasm setlocal sts=38 et " nasm
Vim has syntax files for a whole bunch of assembly instruction sets and syntaxes, which I've found handy.