On Tue, 18 Oct 2005, Chip Salzenberg wrote: > On Mon, Oct 17, 2005 at 10:09:22PM -0400, Jeff Horwitz wrote: > > On Mon, 17 Oct 2005, Chip Salzenberg wrote: > > > Any problems here? Any suggestions for UUID code that's licensed > > > appropriately for use in Parrot? > > > > the UUID library in e2fsprogs might be appropriate. e2fsprogs is GPL, but > > lib/uuid has a separate and much more flexible BSD-style license. > > http://e2fsprogs.sourceforge.net/ > > Hey, neat. > > On the other hand, the idea has been raised on IRC (by Joshua, IIRC) > that an MD5 or SHA256 would protect against corruption, and would also > incidentally make a dandy UUID.
was there any discussion about what the checksums would be calculated on? one benefit of UUIDs is that they are usually independent of the underlying data they identify, and would therefore have no performance penalty for larger files. i know it's only a one-time hit for PBC files, and a minor one at that, but does this also apply for evals/compiles? -jeff
