Subject: Re: [boost] different matrix library?
From: DE (satan66613_at_[hidden])
Date: 2009-08-14 12:15:36
on 14.08.2009 at 19:56
Joel Falcou wrote :
> DE wrote:
>> i've put my lib in the vault/linalg
>> there are sources as well as documentation (zipped html and CHM file)
>> if you are interested you might try to use it or even perform some
>> performance testing (would you mind to post results in that case?)
>> i tried to write documentation so that any user would be able to
>> figure out what's going on and use the lib without difficulties
>> if you'd run through it i hope you get the image of my proposition
> A few comments :
> * prefer operator () to operator. operator is never needed and is
> less generic
internally i alwayse use ()
but  are provided for users' convenience
> * do you handle multi-dimensional matrix with dim > 2 ?
> * separating matrix and vector is a bad idea cause a vector is always a
> matrix. Moreover, you lead the user to wonder about the "orientation" of
> the vector.
but they are handled differently (different public interface)
vector is modeled after std::valarray (everybody knows about valarray)
and matrix is just a generalization of std::valarray behavior
oh and vector is a column-vector
> * a lot of things need to be doen as policy instead of separate class
what do you mean by policy?
> * If you want to handle more complex operations, using a NRC allcoation
> schema is better than a sole T* for holding data
don't get it (forgive my unliteratedness)
> * why rewriting expr. tempalte from scratch when proto's around ?
i've heard and forgotten
i've seen and memorized
i've done and understood
...or something like this
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk