Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!rochester!rutgers!husc6!cmcl2!brl-adm!adm!C03601DM%WUVMD.BITNET@wiscvm.wisc.EDU From: C03601DM%WUVMD.BITNET@wiscvm.wisc.EDU (Derek Morgan) Newsgroups: comp.lang.c Subject: TRUE, FALSE and writing readable code... Message-ID: <8507@brl-adm.ARPA> Date: Mon, 27-Jul-87 16:38:51 EDT Article-I.D.: brl-adm.8507 Posted: Mon Jul 27 16:38:51 1987 Date-Received: Wed, 29-Jul-87 06:08:46 EDT Sender: news@brl-adm.ARPA Lines: 14 I'm a C and a net novice, so please keep your flames low. Anyway, I've been reading about the TRUE/FALSE controversy, and I'm confused. With a background in BASIC, FORTRAN, and ALGOL (yes, D. Goodenough, there's somebody else!), I was used to boolean operations. To tailor *my* C environment, I naively used #define TRUE 1 #define FALSE 0 in one of my header files. This makes it very easy for me to understand the assignments to variables when they are made (e.g., stasis = TRUE;). In this program (system),"stasis" functions as a boolean variable. When testing the value of stasis, I use the form "if (stasis) or if (!stasis)". What pitfalls have I left myself open to by using something which I consider mnemonic? Derek Morgan (What am I doing in this language? It's efficient.) BITNET: C03601DM@WUVMD