pat
I assume at some point I'll be able to write FORTH without stack annotations after every instruction, but its not today...

(Reminds me of how tricky it was to get used to parentheses in Lisps)
Mar 22 at 5:57pmWeb
Show threadDevine Lu Linvega4d ago
@pat eventually your brain can juggle a lot of stuff mentally, it just takes times :)
Show threadpat4d ago
It seems like there is an element of coding-style involved too? A lot of the FORTH/Uxn code I've seen splits lines up quite deliberately, which I imagine helps the author understand what's going on

There's probably no "one-size-fits-all" style guide though?
Show threadDevine Lu Linvega4d ago

@pat I use a auto-formatter for the uxn code, so it standardize how things look. This is the styleguide I use:
https://wiki.xxiivv.com/site/uxnfor

It helps a LOT with reading what's going on at a glance.

uxnfor

By Devine Lu Linvega

XXIIVV
Show thread∴ esoterik ∴4d ago
@pat there’s no shame in writing out the annotations! i still do this for #uxn after years of writing it. one bonus is that it’s great documentation if i find a bug months/years later