AnachronautandClaude Opus 5
3449405b18
CosmOS had 1,161 bytes of Program Memory left before the address applications load at, and Tab completion is not going to fit in that with anything to spare. So the wall moves up one page: the system keeps below 0x4FFF and 0x2FFF, and an application is based at 0x5000 and 0x3000. A PAGE IS A CHEAP THING TO GIVE IT AND AN EXPENSIVE THING TO RUN OUT OF. An application still has 44K of Program Memory before the vector table and the largest one here uses 7.5K, so what was taken from applications is space nothing has ever asked for - while what the system gained is the difference between building the next thing and counting bytes while building it. Not doubling, which was the version that would have cost application space worth minding. One page, and the same again when it is needed. Nothing in the machine knows where the wall is, so this is 34 #Base lines, one threshold in the fault handler, and the table in the CosmOS README that Tests/docs.sh reads its limits out of. The native assembler's scratch map had to move with it, and docs.sh said so before anything ran: its data reached 0x40D6 and its buffers began at 0x4000, so they were sitting on its variables. That file already carries a paragraph about the floor coming up and the map staying where it was. It has happened twice now, and been caught by a check the first time wrote. Twenty three recordings are the same runs a page higher. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01E2JrLzFvuFX9fgi1LDRjrW
86 lines
1.7 KiB
NASM
86 lines
1.7 KiB
NASM
; The source reader on its own, before anything is built on top of it.
|
|
;
|
|
; Everything else in the assembler reads its source through srcNext, so a fault in here
|
|
; would turn up later as a mysterious wrong byte in an output file. It is worth checking by
|
|
; itself, against a file whose contents are already known.
|
|
;
|
|
; It reads whatever it was told to, prints every character back, and then says how many
|
|
; lines went past. The file it is given is deliberately bigger than one block, so the seam
|
|
; between one block and the next is crossed rather than assumed.
|
|
;
|
|
; Written by Anachronaut
|
|
|
|
#Include services.asm
|
|
|
|
#Program
|
|
|
|
#Base 0x5000
|
|
|
|
start:
|
|
SETD.0 Wanted
|
|
INIB 0d23
|
|
SWI osArgument
|
|
SETD.0 Wanted
|
|
LDA.0
|
|
BRA nothingAsked
|
|
|
|
SETD.0 Wanted
|
|
CALL srcOpen
|
|
BNQ noFile
|
|
|
|
readLoop:
|
|
CALL srcNext
|
|
BNQ readDone
|
|
SETD.0 SrcChar
|
|
LDA.0
|
|
OUTA 0x00 ; Straight to the console: one character is not a string.
|
|
BRI readLoop
|
|
|
|
readDone:
|
|
SETD.0 LinesText
|
|
SWI osPrintString
|
|
SETD.0 SrcLine
|
|
LDA.0
|
|
INCD.0
|
|
LDB.0
|
|
SWI osPrintNumber
|
|
SETD.0 NewLine
|
|
SWI osPrintString
|
|
SWI osExit
|
|
|
|
nothingAsked:
|
|
SETD.0 AskText
|
|
SWI osPrintString
|
|
SWI osExit
|
|
|
|
noFile:
|
|
SETD.0 NoFileText
|
|
SWI osPrintString
|
|
SWI osExit
|
|
|
|
#Data
|
|
|
|
#Base 0x3000
|
|
|
|
Wanted:
|
|
#Reserve 0d23
|
|
|
|
LinesText:
|
|
"---- lines: "
|
|
NewLine:
|
|
"
|
|
"
|
|
AskText:
|
|
"say which file
|
|
"
|
|
NoFileText:
|
|
"no such file
|
|
"
|
|
|
|
; The libraries go last, after both segments have been based. An included file that carries
|
|
; code brings its own #Program and #Data lines with it, and a #Base has to come before
|
|
; anything is in the segment it bases - so the bases are set here and the code arrives after.
|
|
#Include scratch.asm
|
|
#Include numbers.asm
|
|
#Include source.asm
|