From: Eric Mahurin <eric_mahurin@...>
Date: 2005-10-21T04:40:31+09:00
Subject: Re: module-based AOP (was Re: [RCR] Cut-based AOP)

--- Trans <transfire@gmail.com> wrote:
> Eric Mahurin wrote:
> 
> > What does a "cut" do that "preclude" doesn't?  It seems
> like
> > you still can manage the AOP methods through modules
> instead of
> > cuts.  And you can stack these.  Can you give a scenario
> where
> > "preclude" doesn't "cut" it :)

[...]

> Note, the Dynamic Module Problem is an ackowledged issue with
> Ruby and
> has nothing to do with cuts themselves. From what I
> understand, it is
> not a simple problem to solve and would take a great deal of
> effort and
> a good bit of alteration to Ruby --if it is even efficenty
> possible.
> 
> Other then that I'm not sure if there is anything *undoable*.

So, let's start with the simple preclude/wrap module concept. 
Make that the basis instead of "cut".  Implementation-wise it
may be very similar to what's needed for "cut".  If possible,
management of these precluded/wrapped modules could be
provided.




__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com