On Fri, 09 Feb 2007 16:18:16 -0700, David Harvey <[EMAIL PROTECTED]> wrote:
> BTW that ell_rational_field.py is getting kind of ridiculously big.
Indeed! It desparately needs to be broken up. I think the best way is to do
this:
class EllipticCurve_rationals_0(...): # name may change
lots of not-to-special functions
class EllipticCurve_rationals_bsd(EllipticCurve_rationals_0):
functions related directly to classical bsd
class EllipticCurve_rationals_padic(EllipticCurve_rationals_bsd):
functions related directly to p-adic objects attached to curves
class EllipticCurve_rationals_descent(EllipticCurve_rationals_padic):
functions related directly to descents curves
etc....
then finally
class EllipticCurve_rational_field(EllipticCurve_rationals_descent):
pass
and only objects of type EllipticCurve_rational_field are ever made.
This is precisely the sort of thing I did with matrices and it has worked
out very well. It will also help make the documentation more readable.
William
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~----------~----~----~----~------~----~------~--~---
