gmpl reader keeps gmpl pointer in global variable
- Dominant language
- C++
- Stars
- 53
- Forks
- 47
- PR merge metrics
- No merged PRs in 30d
Description
Issue created by migration from Trac.
Original creator: @svigerske
Original creation time: 2011-03-25 17:25:24
Since https://projects.coin-or.org/CoinUtils/changeset/1389/trunk
the gmpl reader in CoinMpsIO does not free the GMPL pointer after usage anymore, but keeps it in a global variable, which the user has to remember to free.
Would be nice to have a variant where the GMPL pointer is stored in the CoinMpsIO object and freed in the destructor.
Also a CoinMpsIO method to call the GMPL postsolve routine would be nice.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the CoinMpsIO GMPL reader and its current global-pointer handling. Trace how the reader is constructed and cleaned up, then inspect the available postsolve path and object lifetime requirements. Done means the requested ownership variant and postsolve entry point are specified and covered by appropriate project tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100