On Wed, 10 Jan 2001, Dave Thomas wrote:
> In the logging case, you could write a logging mixin which intercepted
> calls to every method in classes that used it, printing their
> parameters.

Dave - do you have an implementation in mind for this?  I've toyed with
such things, but in fairly messy ways, like hooking into method_added to
alias each method as it's defined, and then creating a wrapper
method with class_eval to replace it.  If you have a cleaner way I'd
love to see it.

My university does a lot of research into AOP, and I've gotten rather
intrigued by the idea; Ruby seems like a very good candidate for a strong
AOP package.