Home » Blog » 2013 » October » N3783: Network Byte Order Conversion -- Robert Pratte

N3783: Network Byte Order Conversion -- Robert Pratte

By Blog Staff | Oct 1, 2013 08:28 AM | Tags: None

Note: This paper was adopted on Saturday at the Chicago meeting for the new Networking TS.

A new WG21 paper is available. A copy is linked below, and the paper will also appear in the next normal WG21 mailing. If you are not a committee member, please use the comments section below or the std-proposals forum for public discussion.

Document number: N3783

Date: 2013-09-27

Network Byte Order Conversion

by Robert Pratte

Excerpt:

This proposal adds support to C++ for converting between host and network byte order.

Add a Comment

Comments are closed.

Comments (1)

0 0

jjlee said on Oct 9, 2013 09:31 AM:

I think it is not easy to use it.
How to convert FLV UI24 (24 bit unsigned int) by current spec?
How to convert WEBM signed and unsigned interger (1 ~ 8 bytes)?

Could we just have something like below? (Just an idea for thinking, might not be correct)


  2. namespace TEST
  3. {

  5. enum endian
  6. {
  7.     little  = 0,
  8.     big     = 1,
  9.     network = big,
  10. #ifdef INTEL_CPU
  11.     host    = little, 
  12. #elif XXX_BIG_ENDIAN_CPU
  13.     host    = big,
  14. #elif YYY_LITTLE_ENDIAN_CPU
  15.     host    = big,
  16. #else
  17. #error unknown CPU
  18. #endif
  19. };

  21. typedef endian EndianFrom;
  22. typedef endian EndianTo;

  24. template <EndianFrom, EndianTo> class EndianConversion
  25. {
  26. public:
  27.     // TFrom and TTo could be any of :
  28.     // int8_t, int16_t, int24_t, int32_t, int40_t, int48_t, int56_t, int64_t,
  29.     // uint8_t, uint16_t, uint24_t, uint32_t, uint40_t, uint48_t, uint56_t, uint64_t
  30.     // and end user could even provide his special type
  31.     template <typename TFrom, typename TTo> void convert(const TFrom&, TTo&);
  32. };
  33. };


Above convert() could even throw an exception if conversion is not possible.

There could be some little endian data in FLV (SoundFormat=3, Linear PCM little endian) and WEBM, how can a big endian host to handle it with current spec?