When do Enumerations break down?
To support a new feature in an existing system, I was just considering implementing some form of discriminator to an entity ta
Those Enumeration Classes look neat, I've often looked jealously at Java's enums.
I think the usual rules apply: do the Simplest Thing That Could Possibly Work. If you find yourself with more than one switch
on the enum, then that's a smell, and time to consider the pattern you've found.
Otherwise, why burden yourself with something you don't need?
Today enums are evil, tomorrow OOP might be evil and AOP will be fine.
Just use the right tool for the job. Remember, Keep It Simple...
If the enum is just for the sake of telling the type of an object - don't bother, use it.
If it has some business logic in it, then it is probably another class.