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… We're not on an AOP list, and I therefore believe I don't cause much harm nor should expect flames when I simplify and just don't bother prefixing "AOP" with "akin to." 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." 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… Best, -- Christophe Porteneuve aka TDD [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
