Frankly, you have slowly drifted off the subject since your previous post. We are talking about how to wrap GSL and make GSL work better with C++, rather than do advertisement for yet another C++ vector/matrix library.
For the original question, my personal opinion on this subject is that just build the program in C++ with some favorite style and narrow the interface between the C++ part and GSL facilities. By contrast, wrapping GSL is not an easy choice because GSL utilizes so many classic C style coding tricks, e.g., void* pointer conversion etc. Specifically, for vector/matrix support library, a third part one out of GSL can be used, because most parts of GSL facilities can work well with built-in array (which are widely supported in other vector/matrix libraries) and do not rely on specific GSL vector/matrix interfaces. On Thu, Sep 10, 2009 at 1:25 PM, Rohit Garg <rpg....@gmail.com> wrote: > Well, you can of course use ublas and the like, but after looking at > these benchmarks, > > http://eigen.tuxfamily.org/index.php?title=Benchmark-August2008 > > I wouldn't touch them with a bargepole if I can help it. As far as > C++ey API goes, may be this > > http://eigen.tuxfamily.org/index.php?title=API_Showcase > > will convince to think twice, if not more. -- HZ _______________________________________________ Help-gsl mailing list Help-gsl@gnu.org http://lists.gnu.org/mailman/listinfo/help-gsl
