The key list of a FILE object, and exact DDS for the physical files #696
Loading…
Reference in a new issue
No description provided.
Delete branch "defs-carved-keys-20261101"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The key list of a FILE object, and exact DDS for the physical files
The key fields of a physical file are in the catalogue before its format record: entries
of 16 bytes (the field name in cp037 padded to 10, two zero bytes, the number of the field
in the format, a flag), in key order; none for an unkeyed file. Measured on four variants
of one file (no key, KX, KY, KX and KY) and on the 40 public saves.
file_object.zigreturns them in the format (
keys,keys_known). With them the rebuilt member is exact:the fields, the keys (including a key that the program alone cannot choose or carve from
a filler), no filler, no decimal-positions note, no note at all. Every PF member rebuilt
from a
files.savfequals the original DDS of its twin (comments and trailing blanksaside). A definition from DSPFFD rows has no key list and keeps the keys of the program.
Gates