The reason I'm interested is to be able to use the Mix-in pattern of class inheritance. It exactly BECAUSE I would rather write more but simpler Classes, that we need to be able to easily compose these implementations together.
I had good luck with it in Python (see my reference example), where I was able to factor out behaviors into independent classes and incorporate them by simply inheriting from them, w/o a lot of excess glue code. On Jan 24, 4:36 pm, RobG <[email protected]> wrote: > On Jan 25, 5:59 am, mckoss <[email protected]> wrote: > > > I've been doing a lot of Python programming, and have found the > > implementation of multiple-inheritance there to be quite useful and > > expressive. Python has a concept of Method Resolution Order (MRO, or > > more specifically, C3 MRO) - you can read more about it here: > > >http://www.python.org/download/releases/2.3/mro/ > > I'd be interested to know why you think you need it. It has often been > said that complex class inheritance schemes are more trouble than they > are worth and that, for javascript, it is better[1] to write a larger > number of simple objects than a smaller number of complex objects. > > 1. Where "better" means simpler to understand and therefore easier to > write and maintain. > > -- > Rob -- To view archived discussions from the original JSMentors Mailman list: http://www.mail-archive.com/[email protected]/ To search via a non-Google archive, visit here: http://www.mail-archive.com/[email protected]/ To unsubscribe from this group, send email to [email protected]
