Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site fortune.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxl!ihnp4!fortune!phipps
From: phipps@fortune.UUCP (Clay Phipps)
Newsgroups: net.lang.c
Subject: The Standard / Re: Problems With Typechecking Enumerated Types
Message-ID: <3786@fortune.UUCP>
Date: Wed, 11-Jul-84 20:34:50 EDT
Article-I.D.: fortune.3786
Posted: Wed Jul 11 20:34:50 1984
Date-Received: Thu, 12-Jul-84 05:26:25 EDT
References: <109@dspo.UUCP>
Organization: Fortune Systems, Redwood City, CA
Lines: 24

[Beware the jabberwock !]

    These results show the inconsistency in type checking enums - some 
    bizzare operations are allowed without any warning (like enum * enum)
    and some reasonable operations are not allowed (like array indexing).
    Has a standard been developed for what operations should and should not
    be allowed on enums?

Sure it has: ANSI/IEEE 770X3.97-1983: "Programming Language Pascal".  :-)

Quick !  Get me that asbestos suit !  

Don't know why it was (as Ritchie The Revered reportedly said) "a botch"
in C, except that it was such a late addition to the language,
and may have violated some fundamental simplifying assumptions
about how things were done.

-- Clay Phipps
   
   soon to be flamed to a crisp at ...
-- 
            { amd  hplabs!hpda  sri-unix  ucbvax!amd }          
                                                      !fortune!phipps
   { ihnp4  cbosgd  decvax!decwrl!amd  harpo  allegra}