to finish tidying up a piece of art and hence is starting something else instead.

now onto a diversion from the previous diversion!

AD(H)D-like behaviour.

stack overflow in crawlout.

[jargon jargon] in [jargon]?

popped one level back up the stack already.

it’s ancient computer jargon. When calling a subroutine, you push current context information and calling parameters onto a “stack” and when the routine returns, you pop the result and your context info back off the stack. This allows the subroutine to use resources such as registers without interfering with the caller’s context.

however there’s only a limited amount of stack space, and if it runs out, then it’s called a stack overflow. That can easily happen for example in the case of recursive subroutines.

crawlout was a signal passing mechanism for exception handling on Prime computers. Getting a stack overflow while handling a crawlout was like two things going wrong at once, and meant that the computer had got its knickers in a twist.