It's there but the abstraction is not very leaky. There was a time when we had to really think about the measurable performance hit involved in using TCP/IP on a little-endian processor. Folks working on lower-level stuff do think about this sometimes, admittedly, but the majority of folks don't sweat endianness day to day. This was the last time I thought about endianness in my career. I wrote shareware code generator 16 years ago that generated a byte array on an Intel PC that was later entered into a PalmPilot running a Motorola 68328. "A big-endian machine stores the most significant byte first-at the lowest byte address-while a little-endian machine stores the least significant byte first." - Endiannessĭid you know for a long time Apple computers were big endian and Intel computers were little endian? The Java VM is big endian. But what's the problem? Well, it's kind of like endianness, except we're still talking about it in 2013. This is a pull request that is possibly useful, possibly awesome, but I'll never know because 672 lines (GitHub tells me) changed because they used CRs and I used LFs or I used CRLF and they used LF, or I used.well, you get the idea.
However, it seems there are three kinds of pull requests that I get. It's such a lovely gift when someone wants to contribute their code to my code.
0 kommentar(er)
