make, the following error was observed:
cp ../../ngaImage nativeImage ../../bin/retro-extend nativeImage x86/common.retro x86/cmos-rtc.retro x86/serial.retro x86/display.retro x86/ata.retro x86/listener.retro Initial Image Size: 9914 s:index-of ? + 220 tokens from x86/common.retro + 59 tokens from x86/cmos-rtc.retro + 186 tokens from x86/serial.retro 0xB8000 ? + 517 tokens from x86/display.retro + 323 tokens from x86/ata.retro + 252 tokens from x86/listener.retro New Image Size: 10814 MAX SP: 16, RP: 55 Stack not empty! Stack: ../../bin/retro-embedimage nativeImage >image.c cc -fno-pie -Wall -m32 -DTARGET_X86 -c retro.c -o retro_qwerty.o retro.c:7:10: fatal error: sys/limits.h: No such file or directory 7 | #include <sys/limits.h> | ^~~~~~~~~~~~~~ compilation terminated. make: *** [Makefile:7: native386] Error 1
#Steps to Reproduce
retro -i -t foo.retro(assuming this file does not exist)
- Observe that
retrogoes into the REPL, but does not crash or emit warnings about the fact that the file is missing.
Since most CLI tools will exit with code 1 and emit an error message (or emit a warning if they do not crash on bad input), I found the current behavior surprising.
RETRO 12 (2021.7)
EDIT: A previous version of this issue incorrectly stated the problem. The problem does not relate to word not found errors as previously stated.
The current RetroForth REPL behavior differs slightly from what I expected from a traditional Forth.
In REPL mode, a stack underflow error will exit the process:
$ retro RETRO 12 (2021.7) 524288 Max, 15004 Used, 509284 Free s:put ERROR (nga/execute): Stack Limits Exceeded! At 9320, opcode 29. sp = -1 $
This behavior is unlike most desktop Forth systems (GForth, PForth, etc..), which recover from such an error.
As multitasking becomes more integrated, there may be a need for "task local" variables. This is something I've been thinking a lot about lately, especially with regard to how
hooks would work in a heavily multitasked VM.
I agree that a callback system would be useful, especially for eventually porting the VM to architectures that use interrupts.
You can run an application in non-test mode via
retro app.retro. You can also accomplish this via
retro -f app.retro.
It is possible to run tests via
retro -t -f app.retro. It is not possible to run tests with
retro -t app.retro(notice the missing -f)
Current behavior appears to be a noop. This behavior is inconsistent with the non-test equivalent.
Appears to be online again. Closing, thanks!
REPORTED RESOLVED FIXED