#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: | 16f1f711fce54ae770c81dd957e5cad2baea8fe1
Report Upstream: N/A | Stopgaps:
Branch: |
public/19661 |
Dependencies: |
-------------------------+-------------------------------------------------
Comment (by dimpase):
Replying to [comment:31 ncohen]:
> Replying to [comment:30 dimpase]:
> > Come on, why do you think that 10 lines of
`libgap.blah(libgap.foo...)`, e.g. in ` _polar_graph()` in the same file
are better than an honest 10-line GAP function?
>
> If you make a syntax error somewhere you see it when the module is
loaded, not when the file is run.
> The error is a Python error. On the other hand, if you wait till the
code is loaded, you may get a GAP error. Or may not if the error is not
well reported. Syntax highlight too, which you cannot have if you feed a
string. Plus you can debug with Python commands.
Python commands are pretty useless for debugging code like this, believe
me. On the other hand,
GAP error reporting is pretty good. (Jeez, people, try GAP once, don't be
lazy :-)). Plus, you can debug a GAP function in GAP, as a GAP function,
while debugging the above `libgap...()....`-Python (or `gap...()) code is
a nightmare, cause GAP errors aren't well-reported then.
It is much quicker to write a GAP function, debug/test it in GAP, and feed
it to `function_factory`, than to write/debug `libgap...()....`-Python,
and I do know what I am talking about.
>
> > Is the following a beacon of beauty in your eyes:
>
> I find it much better than the big string. And worse than being able to
work directly on Sage objects.
Has it ever crossed your mind that strings are Sage objects, too? Every
piece of code is a string, you know...
By the way, I wrote that `libgap-`code, and it did cost me some grey hair,
as opposed to the GAP
code you are objecting to on very unclear grounds.
--
Ticket URL: <http://trac.sagemath.org/ticket/19661#comment:32>
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.
