#11912: Clarify simplify_radical and Maxima's radcan
-------------------------------------+-------------------------------------
Reporter: kcrisman | Owner: mvngu
Type: enhancement | Status: needs_review
Priority: minor | Milestone: sage-6.4
Component: documentation | Resolution:
Keywords: sd48 | Merged in:
Authors: Michael Orlitzky | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/mjo/ticket/11912 | 2d50b886561b9cc98585749b6292eaba269da73c
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by kcrisman):
> I can see the benefit for things like `full_simplify()` where we're
mimicking the Mathematica name so that new users can find it through tab
completion. But for `canonicalize_*` I don't think it's going to do us any
good.
Hmm. So should this even be called `canonicalize_radical` or maybe
something else that indicates it doesn't just do radicals? I wonder why
they chose that name in Maxima - maybe there is something in the algorithm
that is 'radical'? (Pun intended.)
--
Ticket URL: <http://trac.sagemath.org/ticket/11912#comment:19>
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.
