#9704: refactor "trace" -- make trace command call trace method on input if
available
---------------------------+------------------------------------------------
Reporter: was | Owner: jason
Type: enhancement | Status: needs_review
Priority: minor | Milestone: sage-4.5.2
Component: misc | Keywords:
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
---------------------------+------------------------------------------------
Comment(by jason):
-1 on this idea. This means that "trace" means *completely* different
things depending on the input. Instead, we ought to decide what "trace"
means and make two functions. I think trace(x) should be x.trace (and
give a mathematical meaning), and the current trace should be code_trace
or trace_execution or something like that.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9704#comment:2>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
