Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • This is along the line of what I started to think about once I realized enum wasn't the best idea. This is similar to the Typesafe Enum pattern that Rory mentioned in the question comments. I've marked this as the answer because it provided some other good notes as well. I'm now looking into what all I will need to do for this to be serializable. Commented Jan 30, 2014 at 16:35
  • @Ethan: "Typesafe Enum" is only the "hardcoded" version of my suggestion, with some mechanics prohibiting the creation of new objects after initialization. Commented Jan 30, 2014 at 16:41
  • gotcha, that makes sense. I see the distinction now. I'm planning to dynamically read in the valid combinations as you suggest, and expose them through a static property there on the Combination class. Commented Jan 30, 2014 at 16:44