#10341: make MIP backend interface more Python-ic
----------------------------------------------+-----------------------------
Reporter: malb | Owner: ncohen
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-4.6.1
Component: linear programming | Keywords: LP, MIP
Author: Martin Albrecht, Nathann Cohen | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
----------------------------------------------+-----------------------------
Comment(by ncohen):
names aren't used except in these cases, but when the mip.py file will
have been rewritten any creation of variable will mean
storing+concatenating names, any call to add_variables/constraints already
creates variables that are to receive potential names. I still do not know
the loss between calls of cdef methods and cpdef, and one of the reasons
why we have so many optional arguments is to deal with names. And so much
in the backends is about names (I can not stand to look at code when I
know it is never used. I immediately want to remove it)
I mean, all the LP interface does is create constraints and variables.
When you add name considerations to all of these things, you just add time
to earn nothing. I will have fun profiling all this when it will be in to
check what we could earn by removing them or writing it more smartly.
Perhaps I'm just complaining for nothing as usual... Even though cutting
the code by half seems tempting just for its sake `:-D`
Nathann
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10341#comment:40>
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.
