From e3287b1ffa2397fa059f792b3ef506bdda243a93 Mon Sep 17 00:00:00 2001 From: crc Date: Tue, 22 Dec 2020 03:42:29 +0000 Subject: [PATCH] retro.forth: clarify that non-zero is now true FossilOrigin-Name: 38c07e9ce04eaf86d51a91a6d80acd991bfcf892f97934f4b77375743203a56f --- image/retro.forth | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/image/retro.forth b/image/retro.forth index c1f1d01..2afb4a9 100644 --- a/image/retro.forth +++ b/image/retro.forth @@ -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 ;