Load cannot be called twice in one block

[vkichline]

If block 1 of blocks.fb contains the following code, it works as expected:
2 3 thru
If, on the other hand, it contains the following, only block 2 is loaded:
2 load 3 load
Expected: both block 2 and block 3 should be loaded.

Why it matters: I want block 1 to be a system load block, essentially configuring my system. Typically I load several individual blocks and several series of blocks using load and thru repeatedly in block 1. This makes a Forth system very flexible.

[flagxor]

Hi vkichline,

I'm having trouble reproducing this.
Which platform are you seeing this on?

[vkichline]

Esp32Forth on a variety of chips. Load is just: block 1024 evaluate, so if the loaded block contains a load, there is no way to continue at the next statement once the inner load is completed. gForth and others maintain a list to unwind. On Feb 24, 2024, at 10:57 AM, Brad Nelson ***@***.***> wrote:  Hi vkichline, I'm having trouble reproducing this. Which platform are you seeing this on? — Reply to this email directly, view it on GitHub<#53 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABCSFDWC7CJHPEKALKMUMITYVIZZHAVCNFSM6AAAAAAY3T6HQSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRSGU2DGOJZGU>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[vkichline]

Here is a proposed repo case: Screen 1: .” Screen 1” cr 2 load .” Required: print this line.” Cr Screen 2: .” Screen 2” cr ——— Expected: Screen 1 Screen 2 Required: print this line. Actual: Screen 1 Screen 2 On Feb 24, 2024, at 12:28 PM, Van Kichline ***@***.***> wrote:  Esp32Forth on a variety of chips. Load is just: block 1024 evaluate, so if the loaded block contains a load, there is no way to continue at the next statement once the inner load is completed. gForth and others maintain a list to unwind. On Feb 24, 2024, at 10:57 AM, Brad Nelson ***@***.***> wrote:  Hi vkichline, I'm having trouble reproducing this. Which platform are you seeing this on? — Reply to this email directly, view it on GitHub<#53 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABCSFDWC7CJHPEKALKMUMITYVIZZHAVCNFSM6AAAAAAY3T6HQSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRSGU2DGOJZGU>. You are receiving this because you authored the thread.Message ID: ***@***.***>