Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!uakari.primate.wisc.edu!uflorida!ziggy!screamer!tscs!tct!chip From: chip@tct.uucp (Chip Salzenberg) Newsgroups: comp.lang.c Subject: Re: TRUE and FALSE (or true and false) Message-ID: <26E52568.1EF@tct.uucp> Date: 5 Sep 90 16:18:48 GMT References: <26280@mimsy.umd.edu> <708.26dd1bf9@iccgcc.decnet.ab.com> <1000@gistdev.gist.com> Organization: Teltronics/TCT, Sarasota, FL Lines: 14 According to flint@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 ,