#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: Travis Scrimshaw
Authors: Janoš Vidali | Work issues:
Report Upstream: N/A | Commit:
Branch: | f59926575333e34976901f92c1f070e0c168a0b9
u/tscrim/improve_calling_gap_function-19585| Stopgaps:
Dependencies: |
-------------------------------------+-------------------------------------
Comment (by jaanos):
Hi!
> I think we need to mitigate then number of `eval` calls that get made
more so than doing the check in Sage. So if you're happy with my last
change, then I'm okay with setting this to positive review.
That seems like a good idea, however it fails for longer commands, when a
file is used to communicate with GAP (as I said, `last` doesn't seem to
work in this case). Maybe we could check the length of the command, and
then decide how many `eval`s we do based on that (really short cases can
be handled with a single `eval`).
Janoš
--
Ticket URL: <http://trac.sagemath.org/ticket/19585#comment:18>
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.
