Re:Qualcomm, Microsoft Announce Snapdragon 835 PCs with Giga...
by MichaelGG on Thursday June 01, 2017 @01:05PM
(#14462154)
Memory model and byte order is enough to add breakage to stuff written in all of those languages.
[ Parent
| on HN ]
Re:Qualcomm, Microsoft Announce Snapdragon 835 PCs with Giga...
by problems on Thursday June 01, 2017 @02:21PM
(#14462947)
I believe Java and C# enforce specific byte orders to get around this issue, so I doubt you'll see a problem there unless interacting with C++ libraries.
Re:Qualcomm, Microsoft Announce Snapdragon 835 PCs with Giga...
by MichaelGG on Thursday June 01, 2017 @02:26PM
(#14462997)
Not if you're converting bytes into integers, for instance. E.g. https://msdn.microsoft.com/en-us/library/system.bitconverter... - it's arch specific.
Re:Qualcomm, Microsoft Announce Snapdragon 835 PCs with Giga...
by problems on Thursday June 01, 2017 @03:44PM
(#14463799)
Interesting, similar functions in the Java world are always big endian:
http://docs.oracle.com/javase/6/docs/api/java/math/BigIntege...
Seems like a rather poor decision on Microsoft's part. Fortunately rather few things interact with data this way anyways, most serialization formats are text based or include endian information.