For small utilities I like the two-byte load address in the PRG. For data files loaded into changing destinations, it feels like information in the wrong place.
Do you standardize one convention per project or mix deliberately?
Load addresses: keep them in the file or outside?
3 replies · opened AUG 12 ago
One convention per file type. Executables self-load; data goes where the loader asks. Then the directory names make the distinction obvious.
Mixing is fine if the build produces a manifest. The danger is not two conventions; it is hidden conventions.
Put the destination in source and generate both file and manifest from it. Manual duplication always drifts.
Want to add to this transmission?
SIGN IN TO REPLY →