Re: THROW codes and ambiguous conditions

A goal of my Forth system was to only have standard Forth words.

>
You trust the Standard.  Why?

>
  Why not?  This was a learning experience for me, as this is my first
actual Forth implementation [1].  The ANS Forth 2012 standard gave me a
target to aim for.  Guess I shouldn't have bothered then.

And actually why 'yes'? A learning experience for me,
several years ago, was when I realized that without
learning ML and also 'innards' of Forth (I recommend
Brad Rodriguez' paper) I'm not going to get too far.
By just 'sticking to standard' one may end up like
these guys Jeff Fox wrote about, who refused to
create programs in Machine Forth because "they are
paid to write in ANS Forth". And they were unable to
get beyond that.
Using just the standard alone is merely 'first level'.
It may mean one has learned some skill in stack-jugglery
but there's still "long way to Tipperary", shall we say.
--