Re: [Boost-users] size_type doubts / integer library..

Isn't it easier to define those types? int16, int32, int64 uint16, uint32, uint64 Of course the definition is determined by the platform using #ifdef code but basically we have something like typedef unsigned short uint16; It should be enough to handle most integer cases. Use always those types when you need to know it's size and use explicit casting to other types when needed to avoid the warning from bigger to smaller integer size or from signed to unsigned. Try to reduce that situations in any case. Andrea