Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watmath!clyde!cbosgd!ihnp4!ptsfa!ames!think!husc6!uwvax!uwmacc!uwmcsd1!leah!itsgw!alyce From: alyce@itsgw.UUCP Newsgroups: comp.lang.c Subject: Re: Defining TRUE and FALSE Message-ID: <632@itsgw.RPI.EDU> Date: Thu, 9-Jul-87 13:20:22 EDT Article-I.D.: itsgw.632 Posted: Thu Jul 9 13:20:22 1987 Date-Received: Sun, 12-Jul-87 01:38:33 EDT References: <13851@watmath.UUCP> Organization: RPI Info Tech Services - Troy, NY Lines: 12 Keywords: boolean, true, false Summary: define TRUE, FALSE, & boolean type For years I worked on projects that defined typedef enum {FALSE, TRUE} bool; in a project-wide header file. FALSE & TRUE were only used (by most programmers) in assignments; "if (first_time)" and "if ( !found )" were the style used for comparisons. We could define variables and functions to be of type bool, and we always had this dream that someday we would have a version of lint that would warn against setting or comparing bool variables to non-bool values. Even now that I'm back in school, where standards & conventions are unheard of, I still use the bool type because I find it useful, readable, & maintainable.