1

I am a bit perplexed by the Boost ublas documentation. It does not seem clear to me that the sparse and dense matrix classes share a common parent class---which I believe is by design. But then how can I design an API that can accept either sparse or dense matrix, assuming that it need only operate on entries of the matrix using the operator() accessor, say. For example, something like this:

float doMatrixMath(matrix_base<float> m) 
{
  return m(1,1)+m(2,2);
}

Perhaps my thinking about this is wrong-headed. Any guidance regarding how to think about the object modeling of ublas classes would be appreciated!

David Alexander
  • 358
  • 1
  • 12

1 Answers1

1

Templates unfortunately. You can use a very generic type, or dig in and find something more concrete, but the general idea is:

template< typename MatrixType >
float doMatrixMath(MatrixType m) 
{
  return m(1,1)+m(2,2);
}

Of course this can be enhanced with a more concrete type and return value detection...

Kornel Kisielewicz
  • 55,802
  • 15
  • 111
  • 149
  • I thought so ... though in a way this is better as you really don't want virtual method dispatch when you call m(1,1). Can you elaborate on your point about type detection? – David Alexander Sep 03 '11 at 14:30