2020-03-08 04:13:15 +11:00
|
|
|
; *** Const ***
|
|
|
|
; Base of the Return Stack
|
|
|
|
.equ RS_ADDR 0xf000
|
|
|
|
; Number of bytes we keep as a padding between HERE and the scratchpad
|
|
|
|
.equ PADDING 0x20
|
2020-03-08 09:09:45 +11:00
|
|
|
; Max length of dict entry names
|
2020-03-10 10:50:51 +11:00
|
|
|
.equ NAMELEN 7
|
2020-03-08 04:13:15 +11:00
|
|
|
; Offset of the code link relative to the beginning of the word
|
2020-03-10 10:50:51 +11:00
|
|
|
.equ CODELINK_OFFSET NAMELEN+3
|
2020-03-08 04:13:15 +11:00
|
|
|
|
2020-03-13 02:39:27 +11:00
|
|
|
; Flags for the "flag field" of the word structure
|
|
|
|
; IMMEDIATE word
|
|
|
|
.equ FLAG_IMMED 0
|
|
|
|
; This wordref is not a regular word (it's not preceeded by a name). It's one
|
|
|
|
; of the NUMBER, LIT, BRANCH etc. entities.
|
|
|
|
.equ FLAG_UNWORD 1
|
|
|
|
|
2020-03-08 04:13:15 +11:00
|
|
|
; *** Variables ***
|
|
|
|
.equ INITIAL_SP FORTH_RAMSTART
|
2020-03-14 07:40:55 +11:00
|
|
|
; wordref of the last entry of the dict.
|
2020-03-08 04:13:15 +11:00
|
|
|
.equ CURRENT @+2
|
2020-03-14 07:40:55 +11:00
|
|
|
; Pointer to the next free byte in dict. During compilation of input text, this
|
|
|
|
; temporarily points to the next free byte in COMPBUF.
|
2020-03-08 04:13:15 +11:00
|
|
|
.equ HERE @+2
|
2020-03-14 07:40:55 +11:00
|
|
|
; Used to hold HERE while we temporarily point it to COMPBUF
|
2020-03-13 04:52:27 +11:00
|
|
|
.equ OLDHERE @+2
|
2020-03-14 07:01:09 +11:00
|
|
|
; Interpreter pointer. See Execution model comment below.
|
|
|
|
.equ IP @+2
|
2020-03-11 12:37:06 +11:00
|
|
|
; Pointer to where we currently are in the interpretation of the current line.
|
2020-03-08 04:13:15 +11:00
|
|
|
.equ INPUTPOS @+2
|
2020-03-08 09:09:45 +11:00
|
|
|
; Buffer where we compile the current input line. Same size as STDIO_BUFSIZE.
|
2020-03-09 23:49:51 +11:00
|
|
|
.equ COMPBUF @+2
|
2020-03-08 09:09:45 +11:00
|
|
|
.equ FORTH_RAMEND @+0x40
|
2020-03-08 04:13:15 +11:00
|
|
|
|
2020-03-12 15:14:44 +11:00
|
|
|
; (HERE) usually starts at RAMEND, but in certain situations, such as in stage0,
|
|
|
|
; (HERE) will begin at a strategic place.
|
|
|
|
.equ HERE_INITIAL FORTH_RAMEND
|
|
|
|
|
2020-03-11 12:37:06 +11:00
|
|
|
; EXECUTION MODEL
|
|
|
|
; After having read a line through stdioReadLine, we want to interpret it. As
|
|
|
|
; a general rule, we go like this:
|
|
|
|
;
|
|
|
|
; 1. read single word from line
|
|
|
|
; 2. compile word to atom
|
2020-03-13 04:08:11 +11:00
|
|
|
; 3. if immediate, execute atom
|
|
|
|
; 4. goto 1 until we exhaust words
|
|
|
|
; 5. Execute compiled atom list as if it was a regular compiledWord.
|
2020-03-11 12:37:06 +11:00
|
|
|
;
|
2020-03-13 04:08:11 +11:00
|
|
|
; Because the Parameter Stack uses SP, we can't just go around calling routines:
|
2020-03-11 12:37:06 +11:00
|
|
|
; This messes with the PS. This is why we almost always jump (unless our call
|
|
|
|
; doesn't involve Forth words in any way).
|
|
|
|
;
|
|
|
|
; This presents a challenge for our interpret loop because step 4, "goto 1"
|
|
|
|
; isn't obvious. To be able to do that, we must push a "return routine" to the
|
|
|
|
; Return Stack before step 3.
|
2020-03-13 04:08:11 +11:00
|
|
|
;
|
|
|
|
; HERE and IMMEDIATE: When compiling in step 2, we spit compiled atoms in
|
|
|
|
; (HERE) to simplify "," semantic in Forth (spitting, in all cases, is done in
|
|
|
|
; (HERE)). However, suring input line compilation, it isn't like during ":", we
|
|
|
|
; aren't creating a new entry.
|
|
|
|
;
|
|
|
|
; Compiling and executing from (HERE) would be dangerous because an
|
|
|
|
; entry-creation word, during runtime, could end up overwriting the atom list
|
|
|
|
; we're executing. This is why we have this list in COMPBUF.
|
|
|
|
;
|
|
|
|
; During IMMEDIATE mode, (HERE) is temporarily set to COMPBUF, and when we're
|
|
|
|
; done, we restore (HERE) for runtime. This way, everyone is happy.
|
2020-03-14 07:01:09 +11:00
|
|
|
;
|
|
|
|
; EXECUTING A WORD
|
|
|
|
;
|
|
|
|
; At it's core, executing a word is having the wordref in IY and call
|
|
|
|
; executeCodeLink. Then, we let the word do its things. Some words are special,
|
|
|
|
; but most of them are of the compiledWord type, and that's their execution that
|
|
|
|
; we describe here.
|
|
|
|
;
|
|
|
|
; First of all, at all time during execution, the Interpreter Pointer (IP)
|
|
|
|
; points to the wordref we're executing next.
|
|
|
|
;
|
|
|
|
; When we execute a compiledWord, the first thing we do is push IP to the Return
|
|
|
|
; Stack (RS). Therefore, RS' top of stack will contain a wordref to execute
|
|
|
|
; next, after we EXIT.
|
|
|
|
;
|
|
|
|
; At the end of every compiledWord is an EXIT. This pops RS, sets IP to it, and
|
|
|
|
; continues.
|
2020-03-11 12:37:06 +11:00
|
|
|
|
2020-03-08 04:13:15 +11:00
|
|
|
; *** Code ***
|
|
|
|
forthMain:
|
2020-03-08 12:20:11 +11:00
|
|
|
; STACK OVERFLOW PROTECTION:
|
|
|
|
; To avoid having to check for stack underflow after each pop operation
|
|
|
|
; (which can end up being prohibitive in terms of costs), we give
|
|
|
|
; ourselves a nice 6 bytes buffer. 6 bytes because we seldom have words
|
|
|
|
; requiring more than 3 items from the stack. Then, at each "exit" call
|
|
|
|
; we check for stack underflow.
|
|
|
|
push af \ push af \ push af
|
2020-03-08 04:13:15 +11:00
|
|
|
ld (INITIAL_SP), sp
|
2020-03-12 15:14:44 +11:00
|
|
|
; LATEST is a *indirect* label to the latest entry of the dict. See
|
|
|
|
; default at the bottom of dict.asm. This indirection allows us to
|
|
|
|
; override latest to a value set in a binary dict compiled separately,
|
|
|
|
; for example by the stage0 bin.
|
2020-03-11 07:02:40 +11:00
|
|
|
ld hl, LATEST
|
2020-03-12 15:14:44 +11:00
|
|
|
call intoHL
|
2020-03-08 04:13:15 +11:00
|
|
|
ld (CURRENT), hl
|
2020-03-12 15:14:44 +11:00
|
|
|
ld hl, HERE_INITIAL
|
2020-03-08 04:13:15 +11:00
|
|
|
ld (HERE), hl
|
2020-03-08 09:09:45 +11:00
|
|
|
forthRdLine:
|
|
|
|
ld hl, msgOk
|
|
|
|
call printstr
|
2020-03-14 07:01:09 +11:00
|
|
|
forthRdLineNoOk:
|
2020-03-08 09:09:45 +11:00
|
|
|
call printcrlf
|
|
|
|
call stdioReadLine
|
|
|
|
ld (INPUTPOS), hl
|
2020-03-14 07:01:09 +11:00
|
|
|
; Setup return stack. As a safety net, we set its bottom to ABORTREF.
|
|
|
|
ld hl, ABORTREF
|
|
|
|
ld (RS_ADDR), hl
|
|
|
|
ld ix, RS_ADDR
|
2020-03-13 04:08:11 +11:00
|
|
|
; We're about to compile the line and possibly execute IMMEDIATE words.
|
|
|
|
; Let's save current (HERE) and temporarily set it to COMPBUF.
|
|
|
|
ld hl, (HERE)
|
2020-03-13 04:52:27 +11:00
|
|
|
ld (OLDHERE), hl
|
2020-03-11 12:37:06 +11:00
|
|
|
ld hl, COMPBUF
|
2020-03-13 04:08:11 +11:00
|
|
|
ld (HERE), hl
|
2020-03-08 09:09:45 +11:00
|
|
|
forthInterpret:
|
2020-03-11 12:37:06 +11:00
|
|
|
call readword
|
|
|
|
jr nz, .execute
|
|
|
|
call find
|
|
|
|
jr nz, .maybeNum
|
|
|
|
ex de, hl
|
|
|
|
call HLisIMMED
|
|
|
|
jr z, .immed
|
|
|
|
ex de, hl
|
|
|
|
call .writeDE
|
|
|
|
jr forthInterpret
|
|
|
|
.maybeNum:
|
|
|
|
push hl ; --> lvl 1. save string addr
|
|
|
|
call parseLiteral
|
|
|
|
pop hl ; <-- lvl 1
|
|
|
|
jr nz, .undef
|
|
|
|
; a valid number in DE!
|
|
|
|
ex de, hl
|
|
|
|
ld de, NUMBER
|
|
|
|
call .writeDE
|
|
|
|
ex de, hl ; number in DE
|
|
|
|
call .writeDE
|
|
|
|
jr forthInterpret
|
|
|
|
.undef:
|
|
|
|
; When encountering an undefined word during compilation, we spit a
|
|
|
|
; reference to litWord, followed by the null-terminated word.
|
|
|
|
; This way, if a preceding word expect a string literal, it will read it
|
|
|
|
; by calling readLIT, and if it doesn't, the routine will be
|
|
|
|
; called, triggering an abort.
|
|
|
|
ld de, LIT
|
|
|
|
call .writeDE
|
2020-03-13 04:08:11 +11:00
|
|
|
ld de, (HERE)
|
2020-03-11 12:37:06 +11:00
|
|
|
call strcpyM
|
2020-03-13 04:08:11 +11:00
|
|
|
ld (HERE), de
|
2020-03-11 12:37:06 +11:00
|
|
|
jr forthInterpret
|
|
|
|
.immed:
|
2020-03-14 10:33:16 +11:00
|
|
|
; For this IMMEDIATE word to be compatible with regular execution model,
|
|
|
|
; it needs to be compiled as an atom list. We need a temporary space for
|
|
|
|
; this, let's use (OLDHERE) while it isn't used.
|
|
|
|
ex de, hl ; atom to write in DE
|
|
|
|
ld hl, (OLDHERE)
|
|
|
|
call DEinHL
|
|
|
|
; Now, let's write the .retRef
|
|
|
|
ld de, .retRef
|
|
|
|
call DEinHL
|
|
|
|
ld iy, (OLDHERE)
|
|
|
|
jr .execIY
|
2020-03-11 12:37:06 +11:00
|
|
|
.execute:
|
|
|
|
ld de, QUIT
|
|
|
|
call .writeDE
|
2020-03-13 04:08:11 +11:00
|
|
|
; Compilation done, let's restore (HERE) and execute!
|
2020-03-13 04:52:27 +11:00
|
|
|
ld hl, (OLDHERE)
|
2020-03-13 04:08:11 +11:00
|
|
|
ld (HERE), hl
|
2020-03-14 10:33:16 +11:00
|
|
|
ld iy, COMPBUF
|
|
|
|
.execIY:
|
2020-03-14 07:01:09 +11:00
|
|
|
; before we execute, let's play with our RS a bit: compiledWord is
|
|
|
|
; going to push (IP) on the RS, but we don't expect our compiled words
|
|
|
|
; to ever return: it ends with QUIT. Let's set (IP) to ABORTREF and
|
|
|
|
; IX to RS_ADDR-2 so that compiledWord re-pushes our safety net.
|
|
|
|
ld hl, ABORTREF
|
|
|
|
ld (IP), hl
|
|
|
|
ld ix, RS_ADDR-2
|
2020-03-11 12:37:06 +11:00
|
|
|
jp compiledWord
|
|
|
|
.writeDE:
|
|
|
|
push hl
|
2020-03-13 04:08:11 +11:00
|
|
|
ld hl, (HERE)
|
2020-03-14 10:33:16 +11:00
|
|
|
call DEinHL
|
2020-03-13 04:08:11 +11:00
|
|
|
ld (HERE), hl
|
2020-03-11 12:37:06 +11:00
|
|
|
pop hl
|
|
|
|
ret
|
|
|
|
|
|
|
|
.retRef:
|
2020-03-14 07:01:09 +11:00
|
|
|
.dw forthInterpret
|
2020-03-11 12:37:06 +11:00
|
|
|
|
2020-03-08 09:09:45 +11:00
|
|
|
msgOk:
|
|
|
|
.db " ok", 0
|