[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug-glpk] [Fwd: Re: Old API removed but still built]

From: Andrew Makhorin
Subject: [Bug-glpk] [Fwd: Re: Old API removed but still built]
Date: Mon, 12 Aug 2013 17:03:44 +0400

-------- Forwarded Message --------
From: Jan Engelhardt <address@hidden>
To: Andrew Makhorin <address@hidden>
Cc: address@hidden
Subject: Re: Old API removed but still built
Date: Mon, 12 Aug 2013 14:22:50 +0200 (CEST)

On Wednesday 2013-08-07 22:02, Andrew Makhorin wrote:

>> Between glpk-4.48 and 4.52, the LPX API was removed according to the 
>> ChangeLog, but the header file glplpx.h is still there and lpxapi01.c is 
>> still compiled into the library. Is that not kind of redundant?
>Glplpx.h and lpxapi01.c need to be kept (for a while), because some
>internal glpk routines still use obsolete api routines prefixed with
>lpx. However, eventually the old api will be completely removed from the

Once glp routines no longer use the lpx ones, would it be possible
to provide a lpx compatibility library that uses glp?

>> (The "4ti2" program still uses the LPX API, so I am looking for a 
>> shortcut to get it built.)
>The best way is to use the new api routines. It is quite easy to change
>the existing code using lpxapi01.c as a reference.

That's not the shortcut I had intended to go ;)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]