#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):

 `sage.interfaces.interface.Interface` doesn't look like the most useful
 parent, its non-unique and operates on the assumption that one is dealing
 with a separate process. Here we have a shared library that is full of
 global variables. I think libGAP should aim at directly translating
 Sage<->GAP objects, so that the libGAP user does not have to input gap
 commands as strings at all.

 It wouldn't take much to also build a libtoolized standalone interpreter,
 or even a GAP interpreter that communicates over zeromq. The problem is
 that 3rd party packages often expect a stand-alone gap tree with
 upstream's hacked up semi-autotools to install themselves in. From talking
 with people in St. Andrews I understand that upstream probably would have
 switched their build system already if it were not for this legacy
 problem.

 I got rid of the assert abuse and added some more tests.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/6391#comment:124>
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.

Reply via email to