2022-05-17 16:32:29 So, I'm thinking about how I'll gradually transistion to a file system. I think in the meantime, I may introduce a word - something like 'end' or 'finis' - that will terminate a LOAD operation. And otherwise, if I come to the end of loading block N, I'll just roll right on into block N+1. So LOAD will load until it reaches an explicit end word. 2022-05-17 16:33:00 Later, after I've got a real file system, I could likely drop that word; it'd just be an interim way to handle source occupying more than one block. 2022-05-17 16:33:23 And until I set that file system up, I'll just manually manage my block ranges. 2022-05-17 16:33:48 Maybe have a tool initially to "promote" a range of blocks to "a file." 2022-05-17 23:43:12 Actually, that's misguided, isn't it? All I really need to do is implement --> 2022-05-17 23:43:26 And then I can load as many blocks as I want.