Conversation
|
OK, so all the tests pass, which means it basically works. But need to find a good way to keep the helpful error messages. |
asm/exception.asm
Outdated
| rts | ||
|
|
||
| .print_error_and_abort | ||
| jsr RVS |
There was a problem hiding this comment.
maybe put a jump vector here whose address is given as a value. The asm code could just print err but the forth code could later give it something proper, once . exists.
There was a problem hiding this comment.
I solved error messages in the most simple way I could imagine now.
Not sure if it is better than a jump vector, but it works.
asm/exception.asm
Outdated
| lda #'r' | ||
| jsr PUTCHR | ||
| jsr PUTCHR | ||
| .print_cr_and_abort |
There was a problem hiding this comment.
Or maybe insert a JSR NOP between lines 85 and 86. Later ' . could be stored there. Just as something simple.
|
I messed around a little, now it prints custom error messages for some error codes. Something still to solve: when parsing a file, and a word is not found, I want it to print the missing word. |
|
OK, I think it is more or less done now, except for all the things I did not think of yet. I am not sure what implications this has for |
|
TODO: Update manual. |
|
TODO: Figure out if anything ought to change related to File I/O error handling. |
|
Very cool. Thank you. |
|
What do you think of this? To break out of the endless |
|
Mulled things over, and it is probably O.K. if exceptions -13 (Undefined Word) and -37 (File I/O Error) print error messages before THROW, rather than in the exception handler. |
|
Probably good to go. |
|
TODO: print unknown exception numbers. |
No description provided.