"While doing that, we're embracing some already established conventions from other languages in order not to re-invent everything."
With that quote I want to reiterate that MooTools already has Inheritance. Its inheritance mechanism was also developed from Dean Edwards' Base class. MooTools has its roots in Prototype. They share many of the same methods and extensions. MooTools even uses 'parent()' to reference the super class's respective methods, as Andrew expressed his inkling to do. Why re-invent this when MooTools has already been down that road. MooTools has used a lot of Prototypes functionality, as Prototype has used some of Ext's and so on down the line. If we base Prototype's inheritance mechanism off of MooTools then we only have to worry about the few different magic methods we should include. I don't have a problem with any of the magic methods. I have never used those names (superclass, superclasse) and doubt that others have, unless implementing a similar inheritance mechanism. I am not a MooTools fanboy. I have never used the framework, but I can recognize that they have done many things right and have a good solution to inheritance. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Prototype: Core" group. To post to this group, send email to prototype-core@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/prototype-core?hl=en -~----------~----~----~----~------~----~------~--~---
