#19585: Improve efficiency of calling GAP functions
-------------------------------------+-------------------------------------
Reporter: jaanos | Owner:
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-6.10
Component: interfaces | Resolution:
Keywords: GAP functions | Merged in:
interface | Reviewers:
Authors: Janoš Vidali | Work issues:
Report Upstream: N/A | Commit:
Branch: | 46f1391fd13052e8c684ed3e96434143a58860dc
u/jaanos/improve_calling_gap_function-19585| Stopgaps:
Dependencies: |
-------------------------------------+-------------------------------------
Comment (by tscrim):
Replying to [comment:9 jaanos]:
> I think we have a problem now... what if the function does print
something, but also returns a value? Then we should catch the value, not
the printed output (which is most likely some kind of warning).
This is the current behavior in Sage, so it's not really a problem.
However, with our current approach, we could print out any non-trivial
print statements along with functions that print and give outputs.
Although I think we do need 2 function calls, where the second one is the
current call to `IsIdenticalObject`.
--
Ticket URL: <http://trac.sagemath.org/ticket/19585#comment:12>
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.
