@ is implied, and I missed @TURN and @POS there. Mea culpa, I’ll update it.
I can’t speak strongly to the sensibility of the names of those operators. Both ways can make sense to me.
I can’t simultaneously have @HOME X Y and allow @HOME to be the command operator to return home. It’s a limitation of the language.
@POS X Y is a jump to a location which does not currently set HOME.
Imagine running towards a wall, and you bounce back and fall down, but are still facing the wall. The faster you run, the more you bounce back. That was my original (albeit somewhat useless) design.
No, this was already discussed in the thread. UP/DOWN, etc. is being replaced with N/S, etc. They are also being updated to move a fixed number of cells, so if you’re at 0,0 and you move SE 1, you’ll be at 1,1.
As long as I’m tracking arbitrary degrees, I’m not going to round the angle off at any point. I don’t think that will be sensical.
STEP makes no sense without an internal speed. Are you suggesting we drop STEP entirely?
GOSCRIPT only makes sense with GO, causing a script to be called whenever the cell position changes due to automatic movement (not implemented yet).