On 7/6/12 10:02 AM, Birk Eisermann wrote:
> Similar, it is for classes. If one class focuses only one
responsibility,
> the functionality of that class is much easier to understand.
Well, the Graph class is not very complicated. It just has one thousand
methods that apply to graphs. But at least you never wonder in which
file they may be (except for the GenericGraph stuff. except for the
backends stuff....), you can call any function from wherever you are
without worrying of anything.
Having about 10 different graph classes will not kill you, will it?
Because I saw about 30+ .py and .pyx files in the sage/graphs directory!
I think instead of "linking/importing" from graph.py to several other
files is not easier to read either. So separating a few methods could
make the whole easier to understand...
Birk,
Are you proposing a design that is more along the lines of how the
networkx project is organized?
http://networkx.lanl.gov/reference/index.html
http://networkx.lanl.gov/py-modindex.html
https://networkx.lanl.gov/trac/browser/networkx/networkx
Thanks,
Jason
--
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
