Quick one: could the compiler enforce that enum values in order of appearance are sorted?
It could neatly guarantee no surprises with case ranges, like this one: enum Weird { One=1, Two=4, Three=3 } Now, case Weird.One: .. case Weird.Three: won't match Weird.Two. I'd agree that you don't see enums like Weird often. Then again, why rely on a coding convention? This guarantee looks cheap to implement. Any reason against? Tomek