Hello Andrew, > Though it is not an elegant solution, but you can intercept the terminal > output with glp_term_hook and then parse the error and context lines in > the same way as Gusek does. I think it would be quite easy, since at > most one error can be reported. >
I would not consider parsing output a stable interface. E.g. a line "Context: some information" could be either part of an error message or output of a printf statement. The problem is demonstrated by Gusek. The output of printf " not a file :1: not an error \n"; is highlighted as if it where an error. Gusek does not parse any output. It only uses Scintillas capability to route console output to a windows, and to highlight lines which match a regular expression. Does the suggested extension not make sense to you, or do you simply lack the time? In the second case I could provide an implementation. >> void glp_mpl_error_get(glp_tran *tran, char **file, int *line, >> char **message, char **context) Would the function interface be reasonable? Best regards Xypron -- NEU: FreePhone - kostenlos mobil telefonieren und surfen! Jetzt informieren: http://www.gmx.net/de/go/freephone _______________________________________________ Help-glpk mailing list [email protected] http://lists.gnu.org/mailman/listinfo/help-glpk
