Anachronaut
87d819847e
SWI osExit takes a status in A, and the shell keeps it. Fifty eight exits across twenty three programs now say deliberately whether they worked: 25 did what they were asked, 24 did not, 9 were asked wrongly. Compare is the exception and says so - one there means the files differ, which is a result rather than a failure, the way diff has always had it. IN A RATHER THAN Q, which is not a departure from the rule that a service answers in Q. This one takes an ARGUMENT, the way osPrintNumber takes A and B, and it never returns to answer anything. A is free precisely because a return would have put it back - and Q is the ALU's output, so a small number costs four instructions there against one in A. The shell does not print it. A program that failed has already said so in words and a number beside that is noise, so osLastStatus hands it back and Status is the program that shows it. That indirection is the point: the number exists for the thing that cannot read words. MARKING THE EXITS FOUND A DEFECT ON THE FIRST RUN. Type and More printed why they had failed and then fell through into the success exit, reporting that all was well. Nobody had noticed, because while the only reader was a person, the person could see both the complaint and the claim. Two smaller things. Snake sets the console to line mode and then exits with zero, and the linter flagged the second RSTA as redundant - an exit status and a console mode, equal by accident, which is the class that must never be collapsed. And the README still taught answering by writing into the frame, three months of habit that SRET replaced yesterday; that section is gone and the one describing SRET stands in its place.
59 lines
1.1 KiB
NASM
59 lines
1.1 KiB
NASM
; A program that is told what to work on.
|
|
;
|
|
; Everything loaded before this one did the same thing however it was started, because
|
|
; there was no way to tell one anything. A tool that edits a document needs to know which
|
|
; document, and that is the same need a dozen other things will have, so it is a service
|
|
; rather than something an editor arranges for itself.
|
|
;
|
|
; run says it was given nothing
|
|
; run whatever else says "whatever else"
|
|
;
|
|
; The whole rest of the line arrives, spaces and all, rather than a list of words. What
|
|
; counts as an argument is the program's business; the system's business is handing over
|
|
; what was typed.
|
|
|
|
#Include services.asm
|
|
|
|
#Program
|
|
|
|
#Base 0x4000
|
|
|
|
start:
|
|
SETD.0 Given
|
|
INIB 0d64
|
|
SWI osArgument
|
|
|
|
SETD.0 Given
|
|
LDA.0
|
|
BRA sayNothing
|
|
|
|
SETD.0 SaidText
|
|
SWI osPrintString
|
|
SETD.0 Given
|
|
SWI osPrintString
|
|
BRI sayEnd
|
|
|
|
sayNothing:
|
|
SETD.0 NothingText
|
|
SWI osPrintString
|
|
|
|
sayEnd:
|
|
SETD.0 NewLine
|
|
SWI osPrintString
|
|
RSTA
|
|
SWI osExit
|
|
|
|
#Data
|
|
|
|
#Base 0x2000
|
|
|
|
SaidText:
|
|
"it says: "
|
|
NothingText:
|
|
"nothing was said"
|
|
NewLine:
|
|
0x0A 0x00
|
|
|
|
Given:
|
|
#Reserve 0d64
|