Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

OsiGlpk members isObjLowerLimitReached_ and isObjUpperLimitReached_ not initialized #38

Closed
svigerske opened this issue Mar 2, 2019 · 2 comments
Closed

OsiGlpk members isObjLowerLimitReached_ and isObjUpperLimitReached_ not initialized #38

svigerske opened this issue Mar 2, 2019 · 2 comments
Labels
bug Something isn't working OsiGlpk

Comments

@svigerske
Copy link
Member

Issue created by migration from Trac.

Original creator: @svigerske

Original creation time: 2007-08-06 17:10:08

Assignee: @mjsaltzman

Version:

Hi,

in case that Branch and Bound is used and intopt is available,
isObjLowerLimitReached_ and isObjLowerUpperReached_ do not get initialized with false.
Other status-booleans isIterationLimit, ...) are initialized in gutsOfConstructor().

I'm using trunk.

Best,
Stefan
@svigerske svigerske added bug Something isn't working major OsiGlpk labels Mar 2, 2019
@svigerske
Copy link
Member Author

Comment by @LouHafer created at 2008-01-08 00:01:57

Fix committed by Stefan Vigerske.

@svigerske
Copy link
Member Author

Comment by @LouHafer created at 2008-01-08 00:01:57

Resolution: fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working OsiGlpk
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@svigerske