4 ms·
Did you bother to read the article? He writes that native byte order doesn't matter, not, as you botched the quote "byte order doesn't matter". The byte order
by msbarnett 15y ago
Did you bother to read the article? He writes that native byte order doesn't matter, not, as you botched the quote "byte order doesn't matter".
The byte order of the input data obviously matters, and nothing you've said here disagrees with anything he wrote.
- demallien 15y agoI think that skrebel is trying to say that doing as the article suggests comes with an unnecessary performance penalty hit if your CPU has the same endianness as the data stream.
- fpgeek 15y agoWhy should there be a any performance penalty? A good compiler (and I've worked with at least one that could) would know the machine's endianness and could optimize away that sequence of selections, shifts and ors when it isn't needed.
- alexchamberlain 15y agoOk, but the performance penalty is then at compile time...
- alexchamberlain 15y agoLots of downvotes... Do you disagree? If so, why? Or do you think it is insignificant? I've sat and watch C++ compile for 5 hours... Compile time performance is important too!
- skrebbel 15y agowtf? I didn't botch any quote. It's the last words of the article.
- overcyn 15y ago"...the computer's byte order shouldn't matter to you one bit. Notice the phrase "computer's byte order". What does matter is the byte order of a peripheral or encoded data stream"