On Jan 4, 2010, at 6:29 AM, YannLC wrote:
On 4 jan, 15:06, Jason Grout <jason-s...@creativetrax.com> wrote:
I'm curious where you see this eventually going?
(1) MPComplexField replaces ComplexField
(2) MPComplexField provides an alternative to ComplexField (this is
what you're proposing right now, right?)
Yes, even if I would like (1) to happen in a far future the best way
to do it is probably to test it for some time before
If (1), then is MPC qualitatively better than what we do right now
for
ComplexField,
It provides "correct rounding" (that's where the slight overhead comes
from).
It also provides some functions for which we use Pari (e.g. arccos)
or does it just offload code to an external library so we
don't have to maintain it,
The use of a library used by other projects and not only Sage is
indeed also a strong plus I think.
I think this should go in as (2), perhaps as an optional package to
start with, assuming the performance issues can be addressed (and it
looks like there's been progress made in that area) it would make
sense to eventually move to this as the default. For one thing, it'll
make writing arbitrary complex arithmetic in Cython *much* easier
(currently, one either needs to bear the Python overhead, or keep
track of the imaginary and real parts separately doing all arithmetic
by hand--not ideal even if one ignores the rounding issues).
- Robert
--
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
