On Mon, 25 Feb 2013 07:12:03 -0800, Ethan Furman <ethan at stoneleaf.us> wrote: > I must admit I find it mildly amusing (but a lot frustrating) that we > are talk about /enumerations/ not needing to be based on ints. > Checking out Merrian-Webster gives this: > > Definition of ENUMERATE > 1 > : to ascertain the number of : count > 2 > : to specify one after another : list I believe they are taking the second definition. Which would mean that, at a minimum, if it is called an Enum the components should be orderable according to the order of definition. Also having an integer value would decrease the surprise factor. Either that, or name them something other than "enum". If they aren't ints and they aren't orderable, it seems to me they are just a set of names. Which if we had labeled values, could be implemented as...a set of names. --David
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4