#6391: libGAP! -- create a Cython library interface to gap
------------------------------------------------------------------------+---
Reporter: was |
Owner: was
Type: enhancement |
Status: needs_review
Priority: major |
Milestone: sage-4.7
Component: interfaces |
Keywords:
Author: Dima Pasechnik, Ivan Andrus, Volker Braun, William Stein |
Upstream: N/A
Reviewer: Dima Pasechnik, Ivan Andrus, Volker Braun, William Stein |
Merged:
Work_issues: |
------------------------------------------------------------------------+---
Comment(by dimpase):
Replying to [comment:61 vbraun]:
>
> I haven't tried saving/loading Gap workspaces. But it doesn't make much
sense in libGAP since it would break the Python<->Gap object relations. If
you need to load a huge pre-evaluated Gap script then you probably don't
need libGAP, which is all about fast interaction with Gap.
At least the initialization of libGAP should probably use a prebuilt
workspace, as is done by the current interface.
The reason is to speed it up.
Even with Python<-> GAP relations lost, saving workspace might still make
sense (if you know the GAP names of objects
created, you can get them, right?).
And I don't see why it is really lost, as is it recorded in Gap global
variable libgap_owned_objects.
Which would make it possible to re-create the corresponding Python's
{{{GapElement}}} data.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/6391#comment:62>
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.
