Re: native byte order integer and utf-8

If you need unsigned 32-bit numbers of a particular endianess, use either 'V' for little-endian or 'N' for network-order (big-endian).

Cuts out the guesswork and platform dependence of the other 32-bit(ish) templates.

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

Comment on Re: native byte order integer and utf-8

Replies are listed 'Best First'.
Re^2: native byte order integer and utf-8 by bhildred (Novice) on Dec 08, 2013 at 16:20 UTC
I knew about V and N but the spec says native byte order, And since I didn't write the spec . . .	[reply]
Re^3: native byte order integer and utf-8 by BrowserUk (Patriarch) on Dec 08, 2013 at 16:48 UTC
but the spec says native byte order, Native to what? The producer? The consumer? What does the spec say about data transferred from little-endian to big-endian or vice versa? With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday' Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice.	[reply]
Re^4: native byte order integer and utf-8 by Anonymous Monk on Dec 08, 2013 at 16:51 UTC
STDIN/STDOUT is local machine, native, L, http://developer.chrome.com/extensions/messaging.html#native-messaging The same format is used to send messages in both directions: each message is serialized using JSON, UTF-8 encoded and is preceded with 32-bit message length in native byte order.	[reply]