I\'m trying to implement a Plurk API biding for Scala, but I have a design choice to made.
For example, the gender attribute of a Plurk user could be one of \"male\"
If you don't need to iterate over your objects of Gender or need methods like next and previous, classes and objects is the right solution.
next
previous
If you need the features of the "classes and objects" and of "scala.Enumeration" this and this question could be of interest to you.