|
Boost : |
From: Gary Powell (Gary.Powell_at_[hidden])
Date: 2001-01-15 16:57:42
>>
> Regarding intmax_t and uintmax_t, it seems safe to recommend its use for
> cases where we need "the largest built-in integer type".
>
> For the other types, I would rather not encourage too much dependence on
> the number of bits some int has. Of course, if your algorithm really
> needs
> it, go ahead: boost/cstdint.hpp is the best you can get. I just want to
> make sure nobody thinks
> for(boost::uintmax_t i = 0; i < 10; ++i)
> or somesuch is the current fashion for writing
> for(int i = 0; i < 10; ++i)
<<
Should we make a specialization for
std::numeric_limits<boost::uintmax>::digits ?
Then you could use genative programming to do the intelligent thing if the
number of digits is less than you need.
-gary-
gary.powell_at_[hidden]
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk