Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!husc6!mit-eddie!genrad!decvax!decwrl!pyramid!prls!philabs!micomvax!musocs!mcgill-vision!mouse
From: mouse@mcgill-vision.UUCP (der Mouse)
Newsgroups: comp.lang.c
Subject: Re: enum - enum ?
Message-ID: <818@mcgill-vision.UUCP>
Date: Mon, 22-Jun-87 22:56:03 EDT
Article-I.D.: mcgill-v.818
Posted: Mon Jun 22 22:56:03 1987
Date-Received: Sat, 27-Jun-87 04:47:46 EDT
References: <139@starfire.UUCP> <516@haddock.UUCP> <20540@sun.uucp> <525@haddock.UUCP>
Organization: McGill University, Montreal
Lines: 26

In article <525@haddock.UUCP>, karl@haddock.UUCP (Karl Heuer) writes:
> [quotes stuff about enums]

> Perhaps you're right; the May86 dpANS lists under Common Warnings: "A
> value is given to an object of an enumeration type other than by
> assignment of an enumeration constant that is a member of that type."

For example,

enum foo { RED, GREEN, BLUE };
enum foo x;
enum foo y;
...
 x = RED;  /* this is OK */
 y = x;	   /* but this generates a Common Warning; x is not constant */

Good heavens.

> (Which seems unusually strict, as it would produce a warning for some
> perfectly valid code written under the "strong enum" model.)

I certainly see what you mean.  I hope they come to their senses.

					der Mouse

				(mouse@mcgill-vision.uucp)