Jun-16-2024, 09:41 PM
Gribouillis thank you,
just what i was trying to figure out, prepare_table() is run once anytime either pack() or unpack() is called and could be made less instruction intensive by a direct table assignment as you listed. Not static.
Like I said, just chasing down answers to any question I don't know. Your implementation runs just fine, just studying the why of your choice of prepare_table().
This old DEC-type directory structures have two rad50 words for the file name, one rad50 word for the file extension, 42 files per full directory block 3 * 42 = 126) and less than 42 the the last directory block. rebuilding a table 100's of times for each directory block read that has maybe 10 directory blocks, triggers a red flag. Not because of speed, but personal practice.
Not to inpune your code which I believe was written to help
thanks again
Curbe
just what i was trying to figure out, prepare_table() is run once anytime either pack() or unpack() is called and could be made less instruction intensive by a direct table assignment as you listed. Not static.
Like I said, just chasing down answers to any question I don't know. Your implementation runs just fine, just studying the why of your choice of prepare_table().
This old DEC-type directory structures have two rad50 words for the file name, one rad50 word for the file extension, 42 files per full directory block 3 * 42 = 126) and less than 42 the the last directory block. rebuilding a table 100's of times for each directory block read that has maybe 10 directory blocks, triggers a red flag. Not because of speed, but personal practice.
Not to inpune your code which I believe was written to help
thanks again
Curbe