crazyettin
/
Gidubba
1
0
Fork 0
Code Issues Pull Requests Projects Releases 2 Wiki Activity

Modify the behaviour at the buffer end and fix a typo and some terminology in the readme

This commit is contained in:
CrazyEttin 2022-09-22 00:59:08 +03:00
parent 8485fa75cb
commit d5af5d98b8
2 changed files with 10 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
gidubba.asm
View File

@ -1400,8 +1400,8 @@ inloop: load r1, ffff
load r2, bfsize
brneq r0, r2, chstor
;Backtrack if at the buffer end
load r2, #8
;Ignore the input and print an underscore if at the buffer end
load r2, #5f
store ffff, r2
breq r0, r0, inloop

14
readme.md
View File

@ -11,9 +11,9 @@ System requirements
Gidubba requires at least 4 KiB of RAM. It uses an ASCII-compatible
terminal with local echo at address FFFF, and optionally a character
printer at address FFFE and a paper tape reader and punch or a casette
drive at FFFD. Do not be afraid to modify the code yourself if your
setup requires it! (And if you do, apologies for the spaghetti.)
printer at address FFFE and a paper tape reader and punch or a cassette
deck at FFFD. Do not be afraid to modify the code yourself if your setup
requires it! (And if you do, apologies for the spaghetti.)
Format
------
@ -51,8 +51,8 @@ Commands with two arguments:
Commands with no arguments:
* P: Print
* R: Read from the tape reader or casette drive
* W: Write to the tape punch or casette drive
* R: Read from the tape reader or cassette deck
* W: Write to the tape punch or cassette deck
A delete (^?) discards the preceding character and outputs an underscore
to the terminal. An escape (^[) discards the contents of the current
@ -60,7 +60,9 @@ command or line and outputs a backslash and a newline to the terminal. A
carriage return (^M) or a line feed (^J) inputs a newline and commits
the current command or line. An end-of-file (^Z) discards the current
command and halts the computer or discards the current line and returns
to the command prompt.
to the command prompt. At the end of the input buffer any input other
than those described in this paragraph is ignored and an underscore is
output to the terminal.
There are two kinds of error messages: a question mark (?) for an
erroneous command and an exclamation mark (!) for lack of RAM.