On Tue, May 26, 2009 at 10:38 AM, Simon Chiang <simon.a.chiang / gmail.com> wrote:
> I sometimes use nested classes to avoid namespace clutter.  ¨Βθε οξμω
> downsides I found are related to inheritance, in particular when you
> split out classes into different files.
>
>  ¨Βα®ςβ>  ¨Βερυιςε §α―β>  ¨Βμασσ ΣυπεςΓμασσ
>  ¨Βξδ
>
>  ¨Βα―β®ςβ>  ¨Βμασσ ΣυπεςΓμασσ
>  ¨Βμασσ >  ¨Βξδ
>  ¨Βξδ
>
> In both files you have to have the correct superclass (which can be
> hard during refactoring).  ¨Βθεςε αςδιζζεςεξχαωσ το γοξστςυγτθισ> however:
>
>  ¨Βα®ςβ>  ¨Βμασσ ΣυπεςΓμασσ
>  ¨Βερυιςε §α―β>  ¨Βξδ
>
>  ¨Βα―β®ςβ>  ¨Βμασσ ΑΊΊΒ
>  ¨Βξδ
>
> The downside of this is that 'a/b.rb' can't be required on it's own.


Sounds like a job for Ruby's not-well-enough-known Module#autoload

http://talklikeaduck.denhaven2.com/2009/04/06/all-that-you-might-require


-- 
Rick DeNatale

Blog: http://talklikeaduck.denhaven2.com/
Twitter: http://twitter.com/RickDeNatale
WWR: http://www.workingwithrails.com/person/9021-rick-denatale
LinkedIn: http://www.linkedin.com/in/rickdenatale