[Coin-osi-devel] OsiRowCut question
lou at cs.sfu.ca
Thu Apr 13 11:37:49 EDT 2006
This makes a fair bit of sense to me. Anyone more familiar with the
class origins see a problem here?
Do you really need a constructor? From poking about in various parts of
COIN, the de facto convention seems to be that setXXX copies the arguments,
while assignXXX takes ownership. CoinPackedVector::assignVector already exists.
Shouldn't be too hard to create an OsiRowCut::assignRow method to complement
Do you want to take a stab at some code?
More information about the Osi