Re: [boost] [tru64cxx] numeric_cast failing again (Boost.Pythoncompilation)

From: Boris Gubenko (Boris.Gubenko_at_[hidden])
Date: 2005-06-23 10:36:40

>
> I'm guessing that in strict ansi mode there's no specialization of
> numeric_limits<unsigned long long>.  [...]

  This is correct. From <limits> :

#if defined(__DECCXX) && !(defined(__STD_STRICT_ANSI) || \
    defined(__STD_STRICT_ANSI_ERRORS)) && !defined(__DECFIXCXXL634)
//++
//  Long Long Specialization
//--
#if defined(__DECCXX) && !defined(__DECFIXCXXL508)
template <>
#endif
class numeric_limits<long long> {
...

  Boris

----- Original Message ----- 
From: "David Abrahams" <dave_at_[hidden]>
To: <boost_at_[hidden]>
Cc: "Fernando Cacciola" <fernando_cacciola_at_[hidden]>
Sent: Thursday, June 23, 2005 10:06 AM
Subject: Re: [boost] [tru64cxx] numeric_cast failing again 
(Boost.Pythoncompilation)

Markus Schöpflin <markus.schoepflin_at_[hidden]> writes:

> Ralf W. Grosse-Kunstleve wrote:
>
>> With the latest CVS I am seeing this error again:
>
> [snip]
>
>> This is the same as I got a few days ago. I am pretty sure it was fixed a
>> couple of days ago, but now it is broken again. Any ideas?
>
> I would be when it worked in the mean time. Have a look at my reply to 
> your
> first post in this thread. Unfortunately I'm not sure how to address this
> problem.

I'm guessing that in strict ansi mode there's no specialization of
numeric_limits<unsigned long long>.  But the real problem here is that
Fernando Cacciola is supposed to fix a looming ODR violation and
replace the old numeric_cast with one that's already written and in
Boost.

  http://lists.boost.org/boost/2005/06/28914.php

Whassup, Fernando?

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com
_______________________________________________
Unsubscribe & other changes: 
http://lists.boost.org/mailman/listinfo.cgi/boost