Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!wuarchive!udel!haven!adm!smoke!gwyn
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.lang.c
Subject: Re: question about an array of enum
Message-ID: <14456@smoke.brl.mil>
Date: 14 Nov 90 15:11:47 GMT
References: <1990Nov8.000847.16340@athena.mit.edu> <14401@smoke.brl.mil> <1990Nov13.041806.10991@zoo.toronto.edu>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 11

In article <1990Nov13.041806.10991@zoo.toronto.edu> henry@zoo.toronto.edu (Henry Spencer) writes:
>Out of curiosity, Doug, can you find anywhere where the standard promises
>that the integer type *is* large enough to hold all those values?  I can't.
>That's "obviously" the intent, but it doesn't seem to have made it into
>the final document!

I recall somebody on X3J11 commenting on this at the last meeting.
It's the sort of thing that could use a firm interpretation ruling.
(I'm not sure that an implementation could make enums work according
to the spec if they were incapable of holding distinct representations
for all their members, but I don't have a proof ready.)