Hello, I understand the wisdom of not having Poset inherit from DiGraph, as you don't want to be bothered with the DiGraph methods and their different terminology.
I also understand that you need to keep a digraph around, possibly integer-labelled. So, as Jori asked, what would be wrong in *not* having a HasseDiagram class at all? A Poset object could carry a _hasse_diagram digraph, and all methods would be poset methods. Right now, there are two classes where a Poset method can be implemented: Poset, and HasseDiagram. And right now, what we often do is implement two functions instead of one. Getting rid of HasseDiagram looks better unless you know how it is actually useful? Nathann -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
