Fix for v3 and v5 generation, more robust parsing

dardoria / uuid

Common Lisp implementation of UUIDs according to RFC4122

47 stars 12 forks source link

Closed scymtym closed 13 years ago

scymtym commented 13 years ago

The refactored version of make-v3orv5-uuid for v3 and v5 generation loaded only one byte from the hash when setting the two-byte "time-high" part
The string parser is more strict now and accepts UUID of the form "{...}"

scymtym commented 13 years ago

I saw the "{...}" form here http://docs.python.org/library/uuid.html#example when working on a multi-language project. It is not essential though. I can remove it.