#6391: libGAP! -- create a Cython library interface to gap
----------------------------------------------------------------------------+
Reporter: was |
Owner: was
Type: enhancement |
Status: needs_work
Priority: major |
Milestone: sage-5.5
Component: group theory |
Resolution:
Keywords: |
Work issues: assert usage
Report Upstream: N/A |
Reviewers: Dima Pasechnik, Ivan Andrus, Volker Braun, William Stein
Authors: Dima Pasechnik, Ivan Andrus, Volker Braun, William Stein |
Merged in:
Dependencies: #13415, #13123, #13211 |
Stopgaps:
----------------------------------------------------------------------------+
Comment (by vbraun):
Replying to [comment:125 burcin]:
> Would we be able to use IPython as the GAP interpreter if we tied your
libGAP to zeromq?
zeromq is just a transport, you'd have to speak the IPython protocol to do
this. Much harder than just tying stdin/stdout/stderr to sockets.
> AFAICT, the main problem with compiled GAP packages is that they rely on
the object files previously compiled for the GAP executable to find
symbols they need from the GAP kernel. libGAP solves this problem. This
can be fixed by changing GAP's compiler wrapper which adds the path of
these object files to find your libGAP instead.
You also need to prefix the symbol names with `libGAP_` if you want to
link against libGAP with legacy code. Doable but at least in the short
term its much easier to have libGAP and standalone GAP separately. Much
like libSingular and Singular.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/6391#comment:126>
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.
