On Tue, 17 May 2011 21:03:44 +0200, Diego Biurrun <[email protected]> wrote: >> If they really are missing on a real-life system you can replace them >> with autofoo AFAICT. > > Just replacing them with their equivalents without "fast" in the name > seems way easier.
It is easier for you. But there must be a reason why the author used those types. I guess they really are int_fast32_t is typically a 64-bits integer on Alpha; that's for compilation. For development, I think telling that we only care about the low order 32-bits is also valuable. So neither int32_t nor int64_t fit here IMHO. -- Rémi Denis-Courmont http://www.remlab.net/ ------------------------------------------------------------------------------ What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Libmpeg2-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmpeg2-devel
