From: Chris Pine Date: 2003-05-22T00:16:18+09:00 Subject: Re: super, aliases, defadvice, AOP, and so on ----- Original Message ----- From: "Hal E. Fulton" It appears from everyone's silence that no one wants to discuss this right now. Eventually I will bring it up again, because it interests me greatly and I think it is important. ---------------------------- I thought it had the potential to be the most interesting thread we've seen in quite a while! However, I personally don't have much to say about it. For one thing, I don't know anything about defadvice or AOP, and what I have seen about AOP was so language specific that it was not at all clear how much of what I was seeing was AOP and how much was just Java scaffolding. Are there any Ruby-centric explanations of AOP? As far as super, prior, etc... I'm not sure that I have ever wanted to access a method that I have redefined in the same class (thus obliterating the original), but I definitely *have* wanted to access methods in base classes which have been shadowed in subclasses (and which obviously still exist in the base classes). You can use `super', but that only works from inside shadowing method, and it only takes you one level up. I still wish I could do something like `Object::inspect' in C++... but I don't know what the Ruby would look like. As I see it, this is strictly a superset of what `super' already does. Chris