Replies: 1 comment 5 replies
-
There is no a standard throw code for this case at the moment, so the system should define own code from the range [-4095..-256]. A standard throw code could be assigned in the future.
Yes. But the exit status should not be 0 in this case. Probably, it makes sense to always use the throw code as the exit status by default (i.e., unless the program specifies a different value for the exit status using system-specific means). A Forth system can support a batch mode, which avoids any interaction with the user. In this mode, REPL (interpreting of stdin) should not show a prompt, should output error messages in stderr, and should stop on any uncaught exception. It's convenient to use the throw code as the exit status by default in this mode. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
The POSIX signal
SIGTERMis the defaultkill(1)action to terminate a program cleanly; essentiallyBYE. I do not see a suitable exception code for this. Should the system define one of its own from the reserved system exceptions [-4095..-256]? Or should there be a standard one assigned? Also its behaviour when there is noCATCHframe would be to cleanly exit in the same manner asBYE.Beta Was this translation helpful? Give feedback.
All reactions