Anton Ertl <[EMAIL PROTECTED]> writes: > You can find the latest snapshot at > http://www.complang.tuwien.ac.at/forth/gforth/Snapshots/gforth-0.5.9-20030201.tar.gz
First of all many thanks to the developpers of Gforth for all this work being done! > The main thing missing before the release is an update to the > documentation. I hope you are right here. I do have some strange difficulties running my 'brew' program on this snapshot. Let's assume it's brews fault, but I'd like to find that out, to be sure... So I try to debug and found some changes in the behaviour of BREAK: (and maybe of SEE) instead. I can imagine that this is a tribute to a better compiler (which could render BREAK: and SEE impossible to behave like before), but it smells a bit buggy to me. GForth 0.5.9-20030201 : test BREAK: 1 2 3 . . . ; ok see test : test 1075364680 (break:) 1 2 3 . . . ; ok test Scanning code... Nesting debugger ready! [ 0 ] 4018C360 405D0171 1 -> 3 2 1 ok So after the first <RETURN> the debugger executes the word without stepping through. BTW: now 'SEE' does not work any more: see test : test ok Let's see GForth 0.5.0: : test BREAK: 1 2 3 . . . ; ok test Scanning code... -327324696 199 Nesting debugger ready! [ 0 ] 40182734 804A5B2 1 -> [ 1 ] 00001 4018273C 804A5B2 2 -> [ 2 ] 00001 00002 40182744 804A5B2 3 -> [ 3 ] 00001 00002 00003 4018274C 40161F50 . -> 3 [ 2 ] 00001 00002 40182750 40161F50 . -> 2 [ 1 ] 00001 40182754 40161F50 . -> 1 [ 0 ] 40182758 804C280 ; -> ok My main concern is not the word BREAK: but I hoped BREAK: would help me to find out what is going wrong with brew by using it... Robert Epprecht --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
