Hi Jeroen, On 2016-08-05, Jeroen Demeyer <[email protected]> wrote: > There are parent classes like Ring, Field, ... They are defined in > various files, for example in src/sage/rings/ring.pyx > > However, it is not really clear how they should be used, especially > because there is a lot of overlap with categories.
I think in the case of parent classes it is fair to say that they are already superseded by categories. By the way, concerning element classes, if I recall correctly from your previous posts, you are working on unification of the Element class hierarchy --- which I do believe is a good idea, and I also have a couple of tickets dedicated to that (for example, making it easier to implement algebraic structures using actions). Shall I give you a pointer, or do you take them into account already? In a way, I should modify what I recommended in a previous post: While believe that arithmetics should rely on the cythonized framework currently provided by, say, RingElement, that framework would better be moved to Element. So, for the time being, it makes sense to start with RingElement or ModuleElement depending on the application, but in the long run Element should just be fine. Best regards, Simon -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
