Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site drux3.UUCP Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!mtuxo!drutx!drux3!pcf From: pcf@drux3.UUCP (FryPC) Newsgroups: net.lang.c Subject: Re: Cryptic C Message-ID: <1349@drux3.UUCP> Date: Tue, 20-Aug-85 15:27:24 EDT Article-I.D.: drux3.1349 Posted: Tue Aug 20 15:27:24 1985 Date-Received: Sat, 24-Aug-85 00:51:21 EDT References: <2913@ncsu.UUCP> <709@brl-tgr.ARPA>, <1056@mtgzz.UUCP> Organization: AT&T Information Systems Laboratories, Denver Lines: 23 > Instead of using #defines for the boolean values, I > would rather see enumerated data types used. In general, > C programmers seem to prefer #defines to defining a data > type that can be checked during compilation. > typedef enum { False , True } Boolean; I have seen programs written with this style of declaration, they also had lines such as: bool = (x