Jeroen Demeyer <jdeme...@cage.ugent.be> writes: > You forget to address one very important point: *why* should we do this? > Which problem will it solve?
Would you accept "the current way is ugly" as a problem it will solve? Mainly, it's cleaner to separate development code from production code than to have code repositories mixed in with the installation. Our ability to put code in a hierarchy that makes sense for development becomes limited when we must simultaneously make the same hierarchy make sense for execution. Also, I don't think anyone will disagree that the fewer repositories we have, the better. See also various lengthy discussions between me, Robert Bradshaw, and others in the recent "log messages" thread. Really, "which problem will it solve?" is a bit of a difficult question, but I think it can equally apply to any proposal for refactoring. Do you deny the benifits of code refactoring in general? If not, then I guess that is my answer. -Keshav ---- Join us in #sagemath on irc.freenode.net ! -- 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
