which was an amazing read. To a large degree my package is simply a port of
that project from x86 assembly + forth to julia + forth, although the mapping
is in a few places non-trivial due to the fact that julia is a high level
-language. A huge proportion (say 80%) of the library code in src/lib.4th is
-directly copied from JonesForth. (The fact that it was possible to reuse this
-code was satisfying in its own right!) I've added some additional core
-definitions and modified some of the others with the eventual aim of F83
-compliance (discussed below).
+language. During the bootstrapping process, a huge proportion (say 80%) of the
+library code in src/lib.4th was directly copied from JonesForth. (The fact
+that it was possible to reuse this code was satisfying in its own right!) Since
+that time I've added a significant number of core definitions and modified some
+of the others with the eventual aim of F83 compliance (discussed below).
There's quite a lot to say about the implementation, especially due to its
high-level grounding, but that will have to wait for another time.
One of my goals has been to have forth.jl contain as much of the
[F83 required word set](http://forth.sourceforge.net/standard/fst83/fst83-12.htm)
as makes sense given the underlying VM. (Actually, my main goal goes a bit
-beyond this: I want to be able to, with a couple of exceptions, be compatible
+beyond this: I want to forth.jl to be, with a couple of exceptions, compatible
with the description of forth contained in the second edition of Leo Brodie's
book "Starting Forth".) I'm fairly happy with my progress so far. Of the
-131 required F83 words, only 22 remain unimplemented. These words fall into
-three categories: those I intend to implement in the near future, those I may
-possibly implement at some point, and those that I do not intend to ever implement
-for reasons of obsolescence or incompatibility with the design of the VM.
-
-### F83 Words to be implemented soon
-
- PAD ABORT"
-
-The words `PAD` is a simple oversite. `ABORT"` will also be implemented soon.
+131 required F83 words, only 20 remain unimplemented. These words fall into
+two categories: those I may possibly implement at some point, and those that I
+do not intend to ever implement for reasons of obsolescence or incompatibility
+with the design of the VM.
### F83 Words that may be implemented someday
SAVE-BUFFERS UPDATE BLK HOLD LOAD FORTH-83
These words don't make sense to implement. The double-length integer words are
-useless, because the smallest unit of memory in our VM is a full 64 bit
+useless because the smallest unit of memory in our VM is a full 64 bit
integer. For the same reason, there's no point in dealing with unsigned values
just to gain access to another bit. The block I/O words don't make sense because
we have access to a filesystem via the OS.