21–30 of 37 posts
Writing machine language by hand on the C-64 is the closest I've ever felt to the hardware as a programmer. 3 registers, some flags and interrupts.
How come the code listings seem to have removed spaces between keyword tokens? Like, for example, on page 185 you have lines like: > 50 IFHF Which clearly, from context, are supposed to be: > 50 IF HF Is this a typesetting error or did the original text do it that way for some reason? Just to emphasize that BASIC's interpreter didn't care?
Or the plain text version: http://www.zimmers.net/cbmpics/cbm/c64/c64prg.txt
Both found through https://www.c64-wiki.com/wiki/Commodore_64_Programmer%27s_Re...
You could basically visualize the entire 64k in your head.
Good times!
How come the code listings seem to have removed spaces between keyword tokens? Like, for example, on page 185 you have lines like: > 50 IFHF Which clearly, from context, are supposed to be: > 50 IF HF Is this a typesetting error or did the original text do it that way for some reason? Just to emphasize that BASIC's interpreter didn't care?
I forget if Commodore BASIC partly tokenized programs or simply stored them as text, but it definitely stored formatting information, so there was an art to minimizing memory footprint and execution speed by entering them that way.
Very impressive. What's the estimate cost of a print?
I've had some U.S. Letter hardbound books I've printed through them (photo-quality, color) that ran about $45 or so each.
You'd have to go to Lulu and work through all the steps in the post until you got to the last step to see the price.
https://www.retroplace.com/en/feature/operation-manually/162