TRUE and FALSE (or true and false)
Chip Salzenberg
chip at tct.uucp
Thu Sep 6 02:18:48 AEST 1990
According to flint at gistdev.gist.com (Flint Pellett):
>Truth values may only be stored away in some database that is read by a
>different program. If the different program is C right now, you'll
>define TRUE=1 and FALSE=0. Next year, you may rewrite the different
>program in some other language where TRUE is 0, and FALSE is 1 ...
In such a case, the values stored in the database should best be named
DB_TRUE and DB_FALSE, with assignment such:
db_boolean = boolean ? DB_TRUE : DB_FALSE;
External data representation is irrelevant to the TRUE/FALSE issue.
--
Chip Salzenberg at Teltronics/TCT <chip at tct.uucp>, <uunet!pdn!tct!chip>
More information about the Comp.lang.c
mailing list