On Sun, May 24, 2015 at 09:09:54AM -0700, Nathann Cohen wrote:
> - Define the poset category in the posets/ folder. Having some poset
> code in combinat/ and some other in categories/ when there is no clear
> way to know what belongs where is not a good idea.
So far we have been aiming at the following rule of thumb, for posets
and elsewhere:
- Where parent/elements/categories are relevant, abstract code that
does not depend on the data structure shall go in sage.categories.
- Concrete code that depends on a specific implementation of xxx shall
go in the folder holding the implementation of
xxx. E.g. sage.combinat.posets is about FinitePoset, a specific
implementation of finite posets.
There can be debates about this rule, and how far we are from having
implemented it everywhere; but the rule is clear and simple.
Cheers,
Nicolas
--
Nicolas M. Thiéry "Isil" <nthi...@users.sf.net>
http://Nicolas.Thiery.name/
--
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.
