On 5/1/2012 10:40 PM, Steven Watanabe wrote:
Obviously this isn't going to work unless the compiler supports a 128-bit int. I suppose it would be better to cause a compile error if there isn't a sufficiently wide integer type.
That's what it's documented to do. Here's the full spec for boost::uint_t<N>::fast :
The easiest-to-manipulate, built-in, unsigned integral type with at least N bits. The parameter should be a positive number. A compile-time error results if the parameter is larger than the number of bits in the largest integer type.
If I change 65 to 66, the code fails to compile. Can something this simple really be a bug in the library? Yes, I know, I could check the source code, but I'm being lazy right now. If this is not a clear case of pilot error, I'll take a look. Thanks, Scott