#19661: the srgs from Cossidente and Penttila construction of hemisystems in
H(3,q^2)
-------------------------+-------------------------------------------------
Reporter: | Owner:
dimpase | Status: needs_review
Type: | Milestone: sage-7.0
enhancement | Resolution:
Priority: major | Merged in:
Component: graph | Reviewers:
theory | Work issues:
Keywords: | Commit:
Authors: | ea9cdab1a268c70b5f89006cfd9635b554637a18
Report Upstream: N/A | Stopgaps:
Branch: |
public/19661 |
Dependencies: |
-------------------------+-------------------------------------------------
Comment (by dimpase):
Replying to [comment:24 ncohen]:
> > It is unclear to me what particular part of implementation you don't
agree with.
>
> I don't agree with your defining a rather long gap script as a *string*
and executing it. It seems that it can be avoided.
It is not a GAP script, it is a GAP function. If you know other ways to
define a new GAP function within Sage library code, pray tell me how to do
it. Apart from it, I only know `eval` functions (libgap/gap), which are
much uglier.
I hope you don't want me to replace what I have with a sequence of
`libgap.eval...`.
(Hint: `libgap.function_factory` was created for a reason...)
There ways for doing this with C/C++ (in Cython files you can do something
like `cdef extern from C-source-file.c"), but it's because they have to be
compiled. Whereas GAP functions are interpreted.
If you really want I can move computations of e and nu over to Python.
--
Ticket URL: <http://trac.sagemath.org/ticket/19661#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 https://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
