#16439: Allow inverse trig functions to all take complex input
-----------------------------+------------------------
Reporter: kcrisman | Owner:
Type: defect | Status: new
Priority: minor | Milestone: sage-6.3
Component: symbolics | Resolution:
Keywords: | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: | Stopgaps:
-----------------------------+------------------------
Comment (by ppurka):
Replying to [comment:2 kcrisman]:
> > I think the computations should be performed using `CDF` and then
coerced back to `complex`. Complex output from these functions should be
handled by the plot function separately.
> Maybe. Is `CDF` basically the same as `complex`? Is there precedent
for this?
I do not know a precedent, but we will not be losing anything from doing
this. The Python `complex` number comprises of two floating point numbers
which are implemented as `double` in C - see
[https://docs.python.org/2/library/stdtypes.html#numeric-types-int-float-
long-complex this documentation]. The `CDF` in Sage also use double
precision floating point numbers.
{{{
sage: CDF.precision()
53
# Following the documentation at
# https://docs.python.org/2/library/sys.html#sys.float_info
sage: import sys
sage: sys.float_info.mant_dig
53
}}}
--
Ticket URL: <http://trac.sagemath.org/ticket/16439#comment:3>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
