Am 2015-01-13 um 23:53 schrieb Simon King: > On 2015-01-13, Daniel Krenn <kr...@aon.at> wrote: >> Am 2015-01-12 um 22:07 schrieb David Roe: >>> I would say that, ideally, the kind of functionality that >>> you're moving from Group to Monoid should go in the categories. Then we >>> don't need an intermediate class in the Python inheritance tree. >> >> Does this also mean, that (ideally) there shouldn't even be a Group class? > > Ideally, there would be a category framework fully implemented in > Cython---which is impossible, since you can't create cdef classes dynamically > and also can not (yet?) create cdef classes inheriting from more than > one base class.
So does this mean the following for one such method: I take this method and insert it in (attach it to) the category of monoids. Therefore it is also available everything that has the category of groups. But since this is not Cython, I also keep this method (with cdef) in the existing group-class? Daniel -- 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.
