Leopold Toetsch wrote:
Indeed. But we probably want to have an UUID to identify
loaded .pasm/.pir/.pbc to avoid loading duplicates.
The UUID as proposed was intended for that; I just hashed up the
definition in the PDD. Er, no pun intended.
As a side note: distinct PBC segments for checksum and/or UUID is probably
simpler to handle.
How so? At least if it's in the header you can just read it in and know
if you've already loaded the file without having to unpack a directory
segment and so on.
Thanks,
Jonathan
