coin-or / OS

Optimization Services
Other
1 stars 4 forks source link

Discrepancies between OSgL schema and C++ implementation in OSDataStructures #38

Closed svigerske closed 5 years ago

svigerske commented 5 years ago

Issue created by migration from Trac.

Original creator: @h-i-gassmann

Original creation time: 2010-09-22 19:17:43

Assignee: somebody

Version: 2.0

CC: junma kmartin

Keywords: OSgL schema, implementation, constitution

SparseVector in OSDataStructures has int indexes; double values;

For consistence with OSgL it should be IntVector idx; DoubleVector nonz;

Kipp Comment -- I think it would be a mistake to have to define an object for each element in an array. For example,

IntVector* idx;

seems far more cumbersome than

int* indexes;

Having a constructor and destructor called for each nonzero could take a lot time for large problems.

There is also a discrepancy between the implementation of the int and double vectors in C++ and in the OSgL schema.

(changed by kmartin at 2010-09-22 20:01:17)

svigerske commented 5 years ago

Comment by @h-i-gassmann created at 2015-03-05 21:05:46

Resolution: wontfix