[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
experimental code option (was: [Help-glpk] Preprocessing ..)
From: |
Robbie Morrison |
Subject: |
experimental code option (was: [Help-glpk] Preprocessing ..) |
Date: |
Sun, 7 Nov 2010 07:16:10 +1300 (NZDT) |
User-agent: |
SquirrelMail/1.4.17 |
------------------------------------------------------------
Subject: Re: [Help-glpk] Preprocessing - Duplicate Row Removal
Message-ID: <address@hidden>
From: Andrew Makhorin <address@hidden>
Date: Fri, 05 Nov 2010 23:14:13 +0300
------------------------------------------------------------
Andrew Makhorin wrote:
> I think to introduce a preprocessor option (or maybe
> a command-line option in glpsol) to enable/disable
> new untested and experimental features added to glpk.
Hello Andrew
I would prefer a selection mechanism that was not compiled
in. Perhaps an API call like 'glp_enable_experimental'
or 'glp_disable_experimental'. And an equivalent GLPSOL
option, similarly named.
On the other hand, compile-time control over deprecated
APIs would be useful. Some of the Boost C++ libraries
offer macros to prevent old calls from being used. For
instance:
BOOST_FILESYSTEM_NO_DEPRECATED
I try to use these macros whenever possible to keep
my code current. Usually better to fix calls incrementally,
than be confronted with a major overhaul from time to
time.
with best wishes
---
Robbie Morrison
PhD student -- policy-oriented energy system simulation
Technical University of Berlin (TU-Berlin), Germany
University email (redirected) : address@hidden
Webmail (preferred) : address@hidden
[from Webmail client]
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- experimental code option (was: [Help-glpk] Preprocessing ..),
Robbie Morrison <=