#18732: Add tableau query functions glp_eval_tab_row, glp_eval_tab_col to GLPK
backend
-------------------------------------+-------------------------------------
Reporter: mkoeppe | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: sage-6.8
Component: numerical | Resolution:
Keywords: LP, glpk | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/yzh/add_tableau_query_functions_glp_eval_tab_row__glp_eval_tab_col_to_glpk_backend|
380dfb55b3966cd836fa1fbdc8325a9b3df8920e
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by ncohen):
Helloooooo,
> Thanks for the reference! It says that `sig_str` behaves the same as
`sig_on`.
Oh. My mistake. I did not notice `sig_str`, and did not even know about
it. Sorry.
> Does one need to deallocate the memory if an Error is raised between
`sig_on` and `sig_off`?
Well, if you allocate memory somewhere and the function ends, then it is
never deallocated. If you can avoid this easily, it is better to do it.
> How to check that the pointers are not 'null'?
with "if my_pointer == NULL" ?
Nathann
--
Ticket URL: <http://trac.sagemath.org/ticket/18732#comment:6>
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 http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
