Hi, > What exactly is the distinction between vector and vector_base classes?
vector_base is the base class for dense vectors (viennacl::vector) as well as vector proxy objects (vector_range, vector_slice). Since some of the constructors of vector_base are tricky, the recommendation is to use viennacl::vector. Also, this allows for an API very similar to Boost.uBLAS. > I assume that users would mostly use 'vector' but it appears > 'vector_base' has useful features such as casting a matrix to be > interpreted as a vector while sharing the memory (this would be very > useful for 'vector' class). Is the same true of 'vector' where there > are features it has but not in 'vector_base'? You can create a vector from scalar_vector, unit_vector, or zero_vector, which is not possible for a vector_base object. Everything else is the same. Best regards, Karli PS: Similar statements hold true for matrix vs. matrix_base. > > ------------------------------------------------------------------------------ > Developer Access Program for Intel Xeon Phi Processors > Access to Intel Xeon Phi processor-based developer platforms. > With one year of Intel Parallel Studio XE. > Training and support from Colfax. > Order your platform today. http://sdm.link/xeonphi > > > > _______________________________________________ > ViennaCL-devel mailing list > ViennaCL-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/viennacl-devel > ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi _______________________________________________ ViennaCL-devel mailing list ViennaCL-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viennacl-devel
