package libglpk-dev
tags 445565 upstream confirmed
thanks

* Andrew Makhorin <[EMAIL PROTECTED]> [2007-10-15 18:12]:

> Currently lib_free_env is not api routine, however, if necessary, one
> could call it as _glp_lib_free_env that does not require glplib.h to
> be included in the source code.

Yes, one can, in principle, call any function present in libgplk.so
(remember our previous discussion about _glp_lib_xprintf).  However, I do
not think we should encourage users to call non-API, inernal routines from
their programs.

> All glpk routines always free all allocated memory, so if the
> application program has deleted all problem objects, only one memory
> block not longer than 1K remains unallocated. 

This is probably the problem meant by the bug reporter.

> If you think that in some cases this would be useful, I could make
> lib_free_env available on api level.

Yes, I think such a cleanup routine will be useful in the API, insuring that
no allocated blocks are left behind.

Thanks,

-- 
Rafael



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to