
Ublas :

 Next message: Gunter Winkler: "Re: [ublas] Possible defect in mapped_vector"
 Previous message: Markus Rickert: "[ublas] bindings for matrix_vector_range, matrix_vector_slice, bounded_matrix, bounded_vector"
 In reply to: Markus Rickert: "[ublas] bindings for matrix_vector_range, matrix_vector_slice, bounded_matrix, bounded_vector"
 Next in thread: Markus Rickert: "Re: [ublas] bindings for matrix_vector_range, matrix_vector_slice, bounded_matrix, bounded_vector"
 Reply: Markus Rickert: "Re: [ublas] bindings for matrix_vector_range, matrix_vector_slice, bounded_matrix, bounded_vector"
Hi,
> Also, the code in ublas_vector2.hpp seems to be missing stride1/stride2 functionality.
The report at
http://www.cs.kuleuven.be/publicaties/rapporten/tw/TW506.abs.html
doesn't mention stride1/stride2 functionality. I think the stride1/stride2 functionality is an implementation detail of ublas_matrix.hpp used to implement the "storage" functionality. Since ublas_vector2.hpp doesn't seem to depend on ublas_matrix.hpp, I don't think that it should have stride1/stride2 functionality.
The other points seem to be valid. Do you have some code that can be used to test that the bindings for matrix_vector_range, matrix_vector_slice, bounded_matrix and bounded_vector work as intended?
Regards,
Thomas
 Next message: Gunter Winkler: "Re: [ublas] Possible defect in mapped_vector"
 Previous message: Markus Rickert: "[ublas] bindings for matrix_vector_range, matrix_vector_slice, bounded_matrix, bounded_vector"
 In reply to: Markus Rickert: "[ublas] bindings for matrix_vector_range, matrix_vector_slice, bounded_matrix, bounded_vector"
 Next in thread: Markus Rickert: "Re: [ublas] bindings for matrix_vector_range, matrix_vector_slice, bounded_matrix, bounded_vector"
 Reply: Markus Rickert: "Re: [ublas] bindings for matrix_vector_range, matrix_vector_slice, bounded_matrix, bounded_vector"