1, Generate "big endian" format output.

2, Big endian machine: It thinks the first byte it reads is the biggest.

3, Big endian machines store the most significant byte first ( at the lower address ).

4, Note: Depending on the platform and whether the mem structure is big endian or little endian, you may need to swap the order in which bytes are read.

5, But what happens if a client running on a big endian IBM PowerPC attempts to send a 32-bit integer to a little endian Intel x86?

6, The following example illustrates the difference in byte order between big endian and little endian machines.

7, For instance, PNG documents (a competitor to TIFF) are always big endian.

8, The C program below will print out "Big endian" when compiled and run on a big endian machine, and "Little endian" when compiled and run on a little endian machine.

9, Or, how are arguments transmitted between machines with different addressing schemes, big endian vs. little endian?