5 ms·
It's actually worse than that. The first 3 groupings (textually) of the uuid might be little endian while the other 2 are big endian. Learning this cost me mor
by firebird84 4y ago
It's actually worse than that. The first 3 groupings (textually) of the uuid might be little endian while the other 2 are big endian. Learning this cost me more time than I care to admit.
https://en.wikipedia.org/wiki/Universally_unique_identifier#Variants https://en.wikipedia.org/wiki/Universally_unique_identifier#...
- cpach 4y agoWhat the…? This fact will haunt me in my dreams :-p
- throwaway9870 4y agoI had to write some EFI/GPT code earlier this year and was dumbfounded to learn this. This is right up there with the mork file format.
- formerly_proven 4y agoMaking mixed-endian even more haunted is quite the achievement. I congratulate whoever did this at Microsoft for their lasting contribution.
- amluto 4y agoThis is consistent with the misguided structure in the RFC. The first three fields (the time fields) are multibyte integers. The remainder is just bytes. The dashes in the textual representation are just there to confuse you.
- qwerty456127 4y agoWhy would this matter (except when you build an index for a big database)? Note: > 6.8. Opacity: UUIDs SHOULD be treated as opaque values and implementations SHOULD NOT examine the bits in a UUID to whatever extent is possible.
- legulere 4y agoWhen you translate between UUIDs in binary and in text form and communicate with other code the binary UUIDs. The other code might expect the uuids in a different encoding.