17:36 <MrMobius> why does this give an "unstructured" error? : x1 5 ; immediate : x2 x1 ;

17:45 <MrMobius> in gforth

18:09 <veltas> MrMobius: I would assume it's either a warning that you've got an unbalanced stack effect (putting 5 on stack during compilation) indicating a control structure is incomplete within the definition

18:10 <veltas> Or the control-flow stack is the data stack and you've put 5 over the colon-sys that ; consumes

18:16 <MrMobius> veltas I think you're right

18:30 <veltas> "unstructured" is not a very helpful error message, I'm sure there's some austrianism in there somewhere

20:03 <veltas> MrMobius: I'm working on a forth for the ZX spectrum yes

20:04 <veltas> I have implemented most of it already but right now I'm focusing on rewriting it in Forth rather than assembler

20:04 <veltas> Well it will be assembly in forth + cross-compiled colon definitions

21:46 <MrMobius> veltas, interesting

21:46 <MrMobius> what kind of threading?

22:05 <lispmacs[work]> someone was chatting with me earlier about flashforth unified memory space: I just wanted to mention I found out that there are keywords for disabling and enabled writes to flash and eeprom. So you could disable eeprom writes at your top level loop, requiring other words to explicitly enable eeprom writes before doing one.

22:16 <veltas> MrMobius: The existing version has indirect and tokens as build options, but I think I will remove tokens as an option