Wow Robert, thanks! Talk about real-time recreating the wheel--my code is quite similar, though I was using floats.
Three questions for ya: (1) Is there a reason to use Py_ssize_t instead of int or even unsigned int? If it's for length, I can't imagine we'd have polynomials of that huge a degree...! (2) In my code, I specified an eps which controlled the number of iterations rather than trying to predict that in advance--makes more sense, no? (3) In double_newton_raphson, aren't we eating a lot of overhead with lines like f = list(f) and copying the coefficients from f to coeffs? I tried to get around this myself, but due to my status as a cherub SAGE programmer, I couldn't ascertain the right data types to use... Yours, John Voight Assistant Professor of Mathematics University of Vermont [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.cems.uvm.edu/~voight/ --~--~---------~--~----~------------~-------~--~----~ 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/ -~----------~----~----~----~------~----~------~--~---
