#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: | 31a173bccd732cb8d8b656d6882dcec074a87b7d
u/jaanos/improve_calling_gap_function-19585| Stopgaps:
Dependencies: |
-------------------------------------+-------------------------------------
Changes (by jaanos):
* status: needs_work => needs_review
Comment:
OK, I had to make sure that getting variables with long names is properly
handled. As it is, it is possible that `eval`s with commands a bit longer
than the cutoff are made directly to GAP instead of with a temporary file
(due to the `Print()` being wrapped around the variable name), but this
shouldn't be a problem.
I am setting this back to "needs review" due to this additional changes.
Janoš
--
Ticket URL: <http://trac.sagemath.org/ticket/19585#comment:25>
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.
