[Bug-glpk] no range check when converting large timelimit to integer

[Stefan Vigerske]

Hi,

when I do
lpx_set_real_parm(model, LPX_K_TMLIM, 1e+9);

and call some solve routine, then it ends with:
glp_simplex: tm_lim = -2147483648; invalid parameter

So probably the timelimit is somewhere inside GLPK converted to an 
integer without checking whether this is possible.
Maybe GLPK could just set the timelimit to -1 if the double number is 
too big to be converted to an integer.

Best,
Stefan

-- 
Stefan Vigerske
Humboldt University Berlin, Numerical Mathematics
http://www.math.hu-berlin.de/~stefan