Hi Scott,
If you want the largest native integer, though not 100% portable to weird archs, this should work in x86/x64 and most others:
typedef boost::int_t
::fast fastint_t; Why not just use the standard {u}intptr_t or {u}intmax_t typedef in this case?
For intptr_t, this message comes to mind: http://lists.boost.org/Archives/boost/2005/09/94158.php
Well that certainly explains things. That makes my comment on the boost mailing list a bit moot, as well. Thanks for the pointer! It's been three years since that thread was posted. Do the arguments still apply? I assume they do.
And intmax_t is the wrong choice on 32-bit systems that provide a 64-bit type.
I agree. I merely mentioned it because of the "largest native integer" comment above. Thanks again! -Ossama