More than the next few I suspect. END is very invasive and requires a lot more changes before it will work suitably.

For those with a morbid fascination, there is a TODO-END file which contains things Marcus and I know we've got to do, address and fix. How often this file is updated remains to be seen :-) Also, ignore the one DONE item -- that is being reimplemented a different way.

In program mode, the complete memory is available but as soon as a program is running or single stepped, END serves as a boundary. The detection of labels 00 to 99 and A to D is confined to the program the program counter is currently in.

I've made some updates to the latest release so that END should now be working (hopefully). END statements define boundaries for local label search. This includes the hot keys A to D. The program counter needs to be in the program that defines the hot keys to make them active.

GTO.. in program mode goes to the last statement in program memory and adds an END if it isn't already there. In run mode, GTO.. simply goes to step 000. As a short cut, you don't need to press h shift. XEQ. is treated the same as GTO.

GTO.down and GTO.up take you to the next or previous program respectively. This is intended for program mode but may work in run mode, too. I tested it in also library space. All libraries are updated to contain END statements where appropriate. I have not tested this thoroughly, though.

We don't have holes in program space. The 41 does some magic to improve performance in editing and running a program. We just tackle the same issues with brute (processor) force. Moving memory back and forth doesn't cause the same delays it would on a 41 Nut processor. So no packing necessary.

No need to remind me on your HHC presence. I'm still remembering almost every little bit of these few days. :-)