Why people define class, trait, object inside another object in Scala?
- by Zwcat
Ok, I'll explain why I ask this question. I begin to read Lift 2.2 source code these days.
In Lift, I found that, define inner class and inner trait are very heavily used.
object Menu has 2 inner traits and 4 inner classes. object Loc has 18 inner classes, 5 inner traits, 7 inner objects.
There're tons of codes write like this. I wanna to know why the author write it like this.
Is it because it's the author's personal taste or a powerful use of language feature?