> It does not seem to be very practical for what I want to do, however:
> given that the gap will be known only *inside* of the callback
> function, is there a "natural" way to write the gap "outside" of the
> function's scope so that it can be read right after the call to
> glp_intopt?

My mistake. The callback function is given a "void *" pointer meant
precisely for this kind of situation. I used it, and it works
perfectly.

Nathann

_______________________________________________
Help-glpk mailing list
Help-glpk@gnu.org
https://lists.gnu.org/mailman/listinfo/help-glpk

Reply via email to