From: Florian Weber <csshsh@...>
Date: 2004-07-22T19:18:50+09:00
Subject: Re: aop in ruby

>> is there any other possibility to solve this in ruby? amy i overseeing
>> something?
>>
>
> mh.. two things.
> First: did you already looked at AspectR, the prior[] hack from (IIRC)
> Robert Feldt, and the defadvice from mauricio fernandez [3]

yes. i checked out aspectr. its quite great. there are a couple of 
things
which i dont like about it. but it definatelly helps a lot.

however it has the same issues. its not possible to pass the a
advice-free object to the advices.

> Second:
> what your #2 problem mean?
> I'm not an AOP expert at all, but why you'd need to call the base
> method without any aspects? I thought that every pre and post thingy
> should be forced to work with the other, am I wrong?

because it will cause a endless loop..

if the current method is named 'foo', within this method i apply a 
advice,
to which i pass the current object itself.. and within the advice i 
again
call the foo method of the object... bang! loop..

however i wonder if this is just a normal thing and should be taken
care of by the user itself..