Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!linus!genrad!decvax!harpo!floyd!vax135!cornell!uw-beaver!tektronix!ucbcad!ucbmonet.arnold From: ucbmonet.arnold@ucbcad.UUCP Newsgroups: net.lang.c Subject: Re: lint problem - (nf) Message-ID: <154@ucbcad.UUCP> Date: Sat, 25-Jun-83 22:48:08 EDT Article-I.D.: ucbcad.154 Posted: Sat Jun 25 22:48:08 1983 Date-Received: Mon, 27-Jun-83 19:41:50 EDT Lines: 14 #R:ucbesvax:4800014:ucbmonet:19200001:000:589 ucbmonet!arnold Jun 23 15:41:00 1983 You may be able to assign enums to ints without complaint, but you cannot initialize ints with enums, nor can you compare an int to an enum (on 4bsd vax unix, anyway) without a error messages galore. Can anyone tell me why they enums aren't considered just like they were consecutive #defines of constants? The only thing this doesn't catch I can think of that I would care about is the assigning of one enum variable the value of an enum member from a different enumeration. I would vote to lose this without a moment's hesitation if it meant being able to use enums like ints. Ken