On Tuesday, March 14, 2023 at 12:25:50 PM UTC-4, Yaroslav Veremenko wrote:
> Every time I try forth, I start some interpreter, type some words, then it works and I feel like I want to learn more and want to write some code to actually try it out. But every time I hit a wall.
>
> For example yesterday I installed SwiftForth, I read the documentation and it has few pages on source management. The only word that seem to matter to me in this case is INCLUDE. But it doesn't seem to go deep into how to actually use it. This is the process that I can imagine working, but it is crude, and prone to numerous mistakes:
> 1. Open interpreter, write some code, test it until it works
> 2. Hope that SwiftForth doesn't crash and you don't loose all your progress
> 3. Scroll up through the history or list the words, and hope I copy paste stuff that's important to a separate text editor
> 4. Close SwiftForth, start it again, wait for evaluation warning to expire, manually type INCLUDE my-updated-file
>
> SwiftForth doesn't seem to have a command line arguments help in the documentation PDF, nor there seem to be a way to reset the state of a interpreter. At least I couldn't find any. I had similar issues with other interpreters some time back, but I can't remember anymore what they were.
>
> I'm probably missing something obvious, or there's something I don't get.
Sorry all i forgot to add the the new forth word empty needs to be the first call in file.fs
see my previous post on the file ecr.fs