FILE-object definitions: the files of a save file name their own fields #695
Loading…
Reference in a new issue
No description provided.
Delete branch "file-object-reader-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?
FILE-object definitions: the files of a save file name their own fields
A save file that holds the files carries the record format description of every
file in its library catalogue.
core/file_object.zigreads the field and formatrecords of the physical files (kind 0x0b90, listed as 0x1901 by the catalogue):
file, format, level identifier, and per field the name, type (A, P, S), bytes,
digits, decimal positions and buffer positions. Measured on 40 public PF saves
(
tools/file-definitions.sh --save) against their DSPFFD rows: all 641 fields and101 formats equal.
savf rpgleuses the definitions of the save file of theprogram when
--filesis absent and they prove every external file of the program(else the program alone, as before);
--no-file-objectskeeps the old mode, and--files FILE.savfreads the definitions from a separate save file of the files.savf.zigreads the physical-file item (name repeated in the header; thecatalogue page found by its marker when the catalogue has more than one page) and
keeps the catalogue image in the Archive. Display files (kind 0x1901) have another
layout and are not read yet.
Six twins of the c8x family (c8x-privf-2, -privf-4, -privg-1, -privg-2, -privh-1,
c8x-s2-sqlfiles-1) keep their DSPFFD rows as
dspffd.json, notfiles.json: theirprograms use several files of one layout, and the position naming of
rpg_file_defs.zigthen finds two fields at a buffer position and refuses the names(the matrix would turn from 0 to 4..20 failures). The save-file definitions of those
twins are exact (the test compares them with the rows); the naming gap is the next
work of the definitions path.
Gates