From: Kevin S. Van Horn (Kevin.VanHorn_at_[hidden])
Date: 2002-11-12 12:48:00
Daryle Walker writes (about allowing uint_t<N>::fast to be a nonstandard
type such as long long when necessary):
> The reason it hasn't been added is that there is no guarantee
> that long long constants can be used at compile-time (since it's not
> officially part of C++).
1. Do you know of ANY platform that support long long that doesn't also
give you a way to define long long constants?
2. Even if you can't write long long literals, you can still write things
like (unsigned long long)(-1) as a compile-time constant for the maximum
allowed unsigned long long value.
3. You don't need long long constants to implement <boost/integer.hpp>
in a way that takes advantage of long long's if they exist, so why do
4. <boost/cstdint.hpp> already provides support for long long on those
platforms that provide it. It seems quite strange that I can have
uintmax_t be a nonstandard integer type, but uint_t<N>::fast cannot be a
nonstandard integer type.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk