crc/retroforth
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

retro.forth: clarify that non-zero is now true

Browse source 
FossilOrigin-Name: 38c07e9ce04eaf86d51a91a6d80acd991bfcf892f97934f4b77375743203a56f
This commit is contained in:
crc 2020-12-22 03:42:29 +00:00
parent 6f6584401a
commit e3287b1ffa
1 changed files with 2 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
image/retro.forth
View file

@ -462,9 +462,8 @@ to:
Taking a break from combinators for a bit, I turn to some words
for comparing things. First, constants for TRUE and FALSE.
Due to the way the conditional execution works, only these
values can be used. This is different than in a traditional
Forth, where non-zero values are true.
I define `TRUE` as -1 and `FALSE` as zero, but any non-zero
value will be treated as TRUE by the conditional words.
~~~
:TRUE (-n) #-1 ;