AnachronautandClaude Opus 5
588e02aff5
The memory map gave CosmOS 0x0000 through 0x1FFF of Program Memory and applications 0x2000 and above. CosmOS is 8141 bytes at the previous commit, which is fifty one bytes short of the line, and the next thing added to it went over. GOING OVER DOES NOT FAIL WHERE IT HAPPENS. Nothing enforces the division: an application says where it goes with #Base and the loader puts it there, so a CosmOS that has grown past 0x1FFF simply has the next program loaded written over the end of it. What breaks is whichever part of the shell that program happened to cover, at whatever later moment somebody uses it. It turned up here as the monitor's assemble command answering "I do not know" to valid instructions, several commands into a session, on a machine that had booted perfectly well. Both halves are doubled: applications now start at 0x4000 in Program Memory and 0x2000 in Data Memory. That is 16K of code and 8K of data for the system, against the 8775 and 2948 it uses today. Both were on the same trajectory, and moving them together means the twenty files that say #Base are edited once rather than twice. The standalone loader's loadable.asm keeps its old base: it belongs to the loader CosmOS grew out of, not to CosmOS, and its addresses answer to a different program. The unbased-segment diagnostic keeps its old base too - it exists to produce an error message that names the address, and the message is what is recorded. Tests/docs.sh now reads the two limits out of the table in the README and measures both segments against them. It reads them rather than being told them because the table is the specification, and this is the second time in this project that the thing nobody checked is the thing that rotted. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01E2JrLzFvuFX9fgi1LDRjrW
58 lines
1.1 KiB
NASM
58 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
|
|
SWI osExit
|
|
|
|
#Data
|
|
|
|
#Base 0x2000
|
|
|
|
SaidText:
|
|
"it says: "
|
|
NothingText:
|
|
"nothing was said"
|
|
NewLine:
|
|
0x0A 0x00
|
|
|
|
Given:
|
|
#Reserve 0d64
|