From: Christian Leskowsky <christian.leskowsky@...>
Date: 2005-11-29T02:23:43+09:00
Subject: Re: AOP in Ruby ...

------=_Part_35464_24842215.1133198616979
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

I like the Sydney stuff a little more too...  Seems cleaner somehow.

The RCR sounded neat up until I got to:  "A way to specify alternate
method-to-advice mappings" where it started to break down for me.  An
interesting read though.

-
Chris


On 11/28/05, Daniel Berger <Daniel.Berger@qwest.com> wrote:
>
> Ed Howland wrote:
> > On 11/28/05, Mark Collins-Cope <markcollinscope@gmail.com> wrote:
> >
> >>Hi  there,
> >>
> >>I was wondering if there is any support (in the form of frameworks or
> >>whatever) for AOP in Ruby?
> >
> >
> > There is Cut, as defined in RCR 321
> http://www.rcrchive.net/rcr/show/321%22
> >
> > I've tried this out and it seems to work fairly well in my limited
> > exposure. Cuts are
> > transparent subclasses. While the technique in Christian'a reply
> > works, Cut is more broad based. You can reuse aspects by enclosing
> > them in modules, and apply the Cut class across ObjectSpace to have
> > system-wide aspects.
> >
> > Ed
> >
> >
> >>Ciao,
> >>Mark.
>
> I think I prefer the Sydney approach to AOP, which uses Behaviors:
>
> http://hoshi.fallingsnow.net/svn/sydney/trunk/lib/behavior/aop.rb
>
> Regards,
>
> Dan
>
>
>
>
>
>

------=_Part_35464_24842215.1133198616979--