Re: THROW codes and ambiguous conditions

Tried to load LIT's Roman code into FigForth for CP/M only to find it
used
non-Fig words NIP 2DROP TUCK 1- .  I also needed something akin to S" to
pass
the numeric string to the routine.  All edits had to done externally as
no
editor was present.  After fixing all that the routine still didn't work
properly.  It appears LIT's code relies on a non-symmetric DO LOOP -
which is
not FigForth standard.  Let's just say I won't be returning to FigForth
any
time soon.  Once in a decade is enough to remind me 'Never again' :)

You may want to try this one:
 https://www.forth.org/fig86new.zip
This is the one I'm tinkering with (just presently
I already heavily modified it) and its loops are
pretty standard, I believe (it's from 1982).
It started few years ago, when I was curious could
I make it assemble using MASM (it didn't want to...),
because it was prepared using some 'exotic' one, no
more available.
--