On Sunday 20 January 2008, Christophe Porteneuve wrote:
> Michael Schuerig a écrit :
> >> same method that also fires a custom event.  That's AOP, and in
> >> Prototype you can achieve that with the wrap method.
> >
> > No, it's not. Function#wrap is very convenient, but it is not AOP.
> > If anything, it is method combination[1], a forerunner of AOP that
> > predates it by some 10 or 20 years.
>
> Agreed, but what's with the cavalry charge?  Doesn't sound like your
> usual self, Michael…

Oh, you need an update on my usual self. I've recently been called 
intimidating on ror-talk. In that spirit, I really have to defend my 
new-won reputation. Fear me! Would it help if I grew a beard like 
Ze^H^H Emperor Ming's?

> We certainly have quite a few people on the list pretty keen on AOP
> (including members of Prototype Core), but there's accurate and
> "accurate enough."

First of all, even if I have send the cavalry (yes, admittedly I have), 
it's not stampeding at you or anyone else personally.

> So yes, okay, method wrapping (or combination, as you'll have it) is
> but a part of what AOP can do, and does not defined AOP all by
> itself, to be sure.  Still, it's essential to it.  At any rate, hey,
> relax Michael! I'm not all that sure that this flame added pragmatic
> value for the OP…

Well, if the OP remembers that there's more to AOP than what wrap does, 
I consider myself successful. In the best of all possible worlds, 
someone, possibly even from Prototoype Core, would come forth with a 
full-blown, Prototype-based AOP implementation.

Michael

-- 
Michael Schuerig
mailto:[EMAIL PROTECTED]
http://www.schuerig.de/michael/

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Spinoffs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to