Sorry to hear about the the pill chomping. Does it lead to a more mellow
approach to coding, leaving the rest of us to resort to shouting at the screen as
usual? If not then the following simple editing example may help. If
you find any errors in it I'll update this post).
The thing to remember when writing a screen is that the editor will always
use the most recently LIST
ed screen. To use your ROOT word as an example,
here's how it might have been entered.
1) First load the editor
2) Make sure you're using the editor vocabulary (you will be if you've
just loaded it)
3) Select your screen (I'm assuming you want decimal 18)
I'm also assuming that it's empty (you can make it so using CLRSCR
if you want)
4) Now type in your FORTH (assuming UDG), leaving two spaces after each P
Code: Select all
0 P ( SAMPLE EDIT SESSION)
2 P : ROOT 1000000. D* SQRT
4 P SWAP 3PAP CR CR ;
5) If you've no more screens to edit then save the above using
That's all there is to it. You can then distribute your screen 18 by posting the
SCR12.F file (the file numbering is in hex).
The line numbering above leaves a space between each line as it's easier to
correct errors during development. Also remember you can type 18 LIST
time to review your progress and then continue editing.
There are only three gotchas that I can think of:
a) To stop the text at the end of one line merging with the start of another
it is traditional to use two spaces after the P
b) Remember you're in editor mode and that there is an editor command called I
if your word contains the DO LOOP counter I
then switch to the FORTH
vocabulary before testing it.
c) If you enter a line that is too long then it'll be discarded rather than
corrupting the next line.