[376] 2025-04-14 12:13:33 FrancoisVignon wrote:

requestClarification - value okf BLK if the input source is not a block

Actually, BLK contains 0 if the input source is not a block ... ok, but when the input source is the block 0 .... ? Actually, I solve this problem by not using block 0 and starting block numeration to 1 ... but not very elegant.

What to you think about changing the BLK content to -1 when source is not a block ? in the meantime, it is what I will do and starting block numeration to 0 ;-)

Thanks for reading me.

[r1444] 2025-04-14 21:35:36 AntonErtl replies:

requestClarification - value okf BLK if the input source is not a block

I also found this irritating. And at first I completely eliminated block 0 (by using an offset), but later found that having a block 0 that cannot be used for load is the traditional way, so I changed Gforth to follow that way. Blocks are a traditional thing. If using Block 0 for something else was good enough in the times of floppy disks, it should be good enough now. In any case, it seems to me that you have understood the issue, and have no need for clarification, so I am closing this topic. If there is any lack of clarity that we should address, please reopen the topic.

If you want to propose a change to the standard, click on "Proposals" above and follow the instructions. However, after Forth-83 and it's change to PICK the desire for breaking existing programs in the interest of elegance has become very small, so I doubt that such a proposal would succeed.