HP Forum Archive 20

[ Return to Index | Top of Index ]

WP 34S: Beware of new builds Message #1 Posted by Marcus von Cube, Germany on 30 Nov 2011, 4:37 a.m. Just to be warned: The next few builds will most probably be badly broken because we are working on a proper implementation of END. The latest revision I can recommend is 1940.

Re: WP 34S: Beware of new builds Message #2 Posted by Paul Dale on 30 Nov 2011, 5:54 a.m., in response to message #1 by Marcus von Cube, Germany 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. - Pauli

Re: WP 34S: Beware of new builds Message #3 Posted by Eddie W. Shore on 30 Nov 2011, 8:38 a.m., in response to message #2 by Paul Dale OK. I am currently at 1782 - got to catch up. Thanks for the updates!

Re: WP 34S: Beware of new builds Message #4 Posted by Marcus von Cube, Germany on 30 Nov 2011, 10:25 a.m., in response to message #2 by Paul Dale It might work now, at least partially. Testers are welcome. 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. Try GTO.up and GTO.down to navigate between programs. Edited: 30 Nov 2011, 10:25 a.m.

WP 34S: Current release starts working :-) Message #5 Posted by Marcus von Cube, Germany on 2 Dec 2011, 6:58 a.m., in response to message #1 by Marcus von Cube, Germany 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.

Re: WP 34S: Current release starts working :-) Message #6 Posted by Gerry Schultz on 2 Dec 2011, 2:18 p.m., in response to message #5 by Marcus von Cube, Germany Hi Marcus. We sat next to each other at the last HHC. In talking about GTO.. how do you handle memory when editing a program? Will GTO.. pack memory like the 41C? Just curious. Gerry

Re: WP 34S: Current release starts working :-) Message #7 Posted by Marcus von Cube, Germany on 2 Dec 2011, 3:54 p.m., in response to message #6 by Gerry Schultz 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. :-)

[ Return to Index | Top of Index ]

Go back to the main exhibit hall