Re: ublas: reference_type etc.

From: jhrwalter (walter_at_[hidden])
Date: 2002-01-22 03:13:14

--- In boost_at_y..., Kresimir Fresl <fresl_at_g...> wrote:

[snip]
 
> > The major change as far as I see is replacing (const_)
> > reference_type with (const_)reference and (const_)pointer_type 
with 
> > (const_)pointer. This should work with simple 'search and 
replace'.
> 
> Done. Changed files are in the attached zip file (ublas.zip).
 
Checked in to CVS.
 
> I partially tested them: I tried to compile test1.
> I used g++ version 3.0.3 with -DUSE_GCC.
 
Building with gcc 2.95.3 worked as before.
 
> I think that the problems that I encountered are not caused by
> type name changes, because they also apear with your original
> files. (Looking back, I think that I never before tried to compile 
all
> tests ;O)
 
Oops ;-)

> With test11.cpp there were no problems.
> 
> Both in test12.cpp and in test13.cpp, when USE_BOUNDED_ARRAY
> and USE_VECTOR_OF_VECTOR are defined, `bad_alloc' exception
> is thrown.

Confirmed. This was a bug.
 
> Combination USE_MATRIX and USE_STD_VECTOR can not be
> compiled. I attached compete error message for `float'
> (file std_vec_error); for `double' and `complex<>' error messages
> are similar. In short, problem is conversion from `const float* 
const' to
> `float*'  in g++'s header stl_iterator.h, which is triggered from
> `matrix<>::iterator1.
 
Confirmed. This was a problem with gcc 3.0.x.
 
> Other combinations of #defines in test12 and test13 can be compiled
> and executed.
> 
> Sincerely,
> 
> fres
> 
> PS. I will not be in Zagreb for next few days, but when I return, I
> will try other tests.

[snip some long template related error messages ;-]
 
Thanks for your support and best regards
 
Joerg