Open ruv opened 1 year ago
An ambiguous condition is missed for ALSO
, when the search order is empty.
Probably, it's better to specify a throw code for this case (see the issue Eliminating of some ambiguous conditions).
[update] this issue was already discussed in comp.lang.forth in 2008. m_l_g3 wrote on 2008-12-16:
I change my mind and propose to declare it an ambiguous condition in all affected words (FORTH ALSO DEFINITIONS).
[update] see also: 16.4.1.2 Ambiguous conditions — only PREVIOUS
is mentioned with "search order empty".
An ambiguous condition is missed for
MARKER
, which is declared forFORGET
.Something like: an ambiguous condition exists if definitions or data required for correct execution of the program are removed during execution of name.
See also a comment.
An ambiguous condition is missed for 17.6.1.0245
/STRING
when n is negative and the resulting character string goes beyond the data space.