Re: [ublas] traits compilation errors under g++ 3.2.3 with BOOST_UBLAS_USE_INTERVAL

From: Jerry Swan (pmxjs_at_[hidden])
Date: 2006-08-29 12:37:54

>Have you defined BOOST_UBLAS_USE_INTERVAL when compiling?
Yes - it's the code that's bookended by #ifdef BOOST_UBLAS_USE_INTERVAL ... #endif
that fails to compile.

Failing to define BOOST_UBLAS_USE_INTERVAL means that the compiler tries to use the default version of scalar_traits, which then results in an error because there's no std::abs or std::sqrt specialization for interval (I guess it could be argued that the default version of scalar_traits abs etc should have ::abs, rather then std::abs...).

Jerry.

>>> mail_at_[hidden] 08/29/06 4:44 AM >>>
On Thursday, 24. August 2006 12:03, Jerry Swan wrote:
> g++ 3.2.3 chokes on line 269 of traits.hpp:
>     struct scalar_interval_type_traits : scalar_type_traits<T> {
>
> In addition, it complains about the specializations of type_traits for
> specific intervals (type_traits<boost::numeric::interval<float> > etc)
> saying that they've already been instantiated.
>
> Is this likely to be a function of header file ordering, is it broken, or
> is there perhaps something else I'm doing wrong?

Have you defined BOOST_UBLAS_USE_INTERVAL when compiling?

Michael
-- 
___________________________________
Michael Stevens Systems Engineering

34128 Kassel, Germany
Phone/Fax: [phone]

Navigation Systems, Estimation  and
                 Bayesian Filtering
    http://bayesclasses.sf.net
___________________________________
_______________________________________________
ublas mailing list
ublas_at_[hidden]
http://lists.boost.org/mailman/listinfo.cgi/ublas


This message has been checked for viruses but the contents of an attachment
may still contain software viruses, which could damage your computer system:
you are advised to perform your own checks. Email communications with the
University of Nottingham may be monitored as permitted by UK legislation.