Commodore 64 Guides
pickledlight.blogspot.com
Commodore 64 Guides
1–10 of 37 posts
Re: Commodore 64 Guides
#2An invaluable action for preserving heritage.
Re: Commodore 64 Guides
#3Incredible. Thanks so much for this. Just wondering, do you think you’ll do the schematic at some stage?
Re: Commodore 64 Guides
#4Thanks! It is from you that I first heard about Lulu and looks like their price is pretty reasonable (600 page A5 Hardcover only costs 20 bucks but probably a lot more for CAD). I have quite a few manuals and pdfs that I would like to convert to books.
Re: Commodore 64 Guides
#5Very impressive. What's the estimate cost of a print?
Re: Commodore 64 Guides
#6How come the code listings seem to have removed spaces between keyword tokens? Like, for example, on page 185 you have lines like:
> 50 IFHFWhich 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?
Re: Commodore 64 Guides
#7Registered to say, amazing effort. Never owned one but I want to read this now, strangely.
Re: Commodore 64 Guides
#8How 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 can verify that it's that way (without the spaces) in the original. Sometimes you had to do it to fit all the code in two screen lines, because that was the maximum line length. So it probably became a habit for some programmers.
Re: Commodore 64 Guides
#9How 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 can verify that it's that way (without the spaces) in the original. Sometimes you had to do it to fit all the code in two screen lines, because that was the maximum line length. So it probably became a habit for some programmers.
That's a shame :( I had been hoping to use this book with my daughter (she's been getting into coding on retro machines like our C64) but I don't think I want to complicate things with the added cognitive load of tokenizing keywords she doesn't even know yet, by hand.
Re: Commodore 64 Guides
#10Very nice! I do hope he releases the document source to allow for collaborative correcting and improving.