You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to suggest the following test for D<: T{ 0 1 1 0 D< -> FALSE }T
While reading lbForth's code, I found this definition: : d< rot > if 2drop -1 else u< then ;
which looked suprisingly concise to me, but it doesn't handle the test correctly. At the moment no other tests seems to expose the bug in lbForth's D<.
The text was updated successfully, but these errors were encountered:
Excellent suggestion, I'll incorporate it into the double number tests later today. I think that anything like this, where an implementation is incorrect but not detected by the test programs, should have a test included to detect the fault (if detectable of course).
Many thanks.
Test added as suggested by Helmut Eller for detection of plausible but faulty definition of D< plus similar test with negative operands. Also added for DU<. See issue #21.
I'd like to suggest the following test for
D<
:T{ 0 1 1 0 D< -> FALSE }T
While reading lbForth's code, I found this definition:
: d< rot > if 2drop -1 else u< then ;
which looked suprisingly concise to me, but it doesn't handle the test correctly. At the moment no other tests seems to expose the bug in lbForth's D<.
The text was updated successfully, but these errors were encountered: