> Thanks Jeroen and David for your answer and explanations. It's true that > OOP with deep hierarchy is not the only possible approach. For instance, > there is also the paradigm of component aggregation, see e.g. > http://cowboyprogramming.com/2007/01/05/evolve-your-heirachy/ > Maybe the latter is closer (at least in spirit) to the category framework > in Sage. > > I don't quite think so as we still have a hierarchy setup through the category framework, and we are just adding that hierarchy into the class MRO at runtime. Although the axiom approach does have this sort of flavor to it. (BTW, that was an interesting article.)
However, I'm +1 for flatting things down to Element as it would probably solve #15160 <http://trac.sagemath.org/ticket/15160> and #15947 <http://trac.sagemath.org/ticket/15947>. Best, Travis -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
