>> If you aim for portability, you can simply use int8_t, int16_t, etc. >> in your implementation - no need to use it in the archive interfaces >> as far as I get it. Sorry if I miss the point :) > If a library user wants his archives to be portable he has to use > int8_t, int16_t, etc.. for all data integral types that he wants to > portably serialize. Having those types in the interface might help > making users aware of the fact that they should use those types if they > want their serialized archives to be portable. However just emphasizing > this at a prominent place in the documentation might be enough. > Matthias Yeah, that's what I tried to express :)
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
