From: "Brian Schröder" <ruby.brian@...>
Date: 2005-11-16T18:43:17+09:00
Subject: Re: Nested classes

On 16/11/05, Groleo Marius <groleo@gmail.com> wrote:
> On 11/16/05, Brian Schr�der <ruby.brian@gmail.com> wrote:
> >
> > What problem do you want to solve?
> >
> > Is this maybe nearer to you goals:
> >
> > class A
> >   class B
> >     def fun_b
> >       p "B"
> >     end
> >   end
> > end
> >
> > A::B.new.fun_b
> >
> > cheers,
> >
> > Brian
> >
>
> Consider the case when class B would have more member functions.
> In your example I would have to create a new object for each call to a
> B function.
> OTOH, a solution that I dont like :) could be :
>  class A
>    class B
>      def fun_b
>        p "B"
>      end
>      def other_b
>        p "_B"
>      end
>    end
>  end
> b = A::B.new
> b.fun_b
> b.other_b
>
> By the instantion of a new B object in the code from the first post,
> and refering to it, I was searching to keep a hierarchy inside a
> network protocol.
> I couldn't find any hint on google though :(
>

Maybe you should look at the delegation pattern. That may be
applicable here. But I have not yet understood your use case. Could
you describe it in a bit more detail?

regards,

Brian

--
http://ruby.brian-schroeder.de/

Stringed instrument chords: http://chordlist.brian-schroeder.de/