The Sinclair QL Forum

Well done, Derek! Its not your fault that this document is still crawling with errors! To take a few glaring examples after looking at the first few pages: p3: PC.MCTRL = PC_MCTRL = 18020 (not 18021) PC.INTR = PC_INTR = 18021 (not 18022) PC.TPDATA = PC_TDATA It irritated me so much (I find this happ...

Derek_Stewart wrote:<>
I can not believe that 2 comercial books were published with all these glaring errors.
<>

I can. A few honest mistakes is one thing, but.. Still, some of us have come through, relatively unscathed, so perhaps nuff said.

Hi Norm, My eBook is at https://github.com/NormanDunbar/QLAssemblyLanguageBook/releases/tag/October-2020. Chapter 7.8 is where you need to be: <> As you write yourself in the reference you give, its not documented anywhere: I have never seen this documented and it has been discovered by me during lo...

Hi Per, I am in the process of updating the changes, shoukd done by tomorrow. Just a couple of points. "Get parameters on to maths stack": .. "Entry: A1.L top of maths stack" This is false <> Looks like the Advanced QL User Guide (QLAUG) by Adrian Dickens, is also incorrectly in...

Well Derek, since you ask: Using the 18-5-2022 book's page numbers, not the PDF's P7 Supervisor stack: should be $28480 to $28180 , not $28480 to $28140 p151 Getting Parameters: OCR error at penultimate line "..and register AS points to.." AS should be A5. p152 Penultimate paragraph: Line ...

It seems unfair to saddle Derek with all this! I thought the whole point of GitHub was that many different people could work on the same project without FUBAR. Cant everyone sort out their own corrections? BTW1: Some of these corrections are going to mess up any page references! That should be taken...

Looks great, Derek! Well done - and thank you!

I dont really have a dog in this fight; its all the same to me, though I do think it would be nice if more people would like to code for the QL AND derivatives. From the opinions Ive read above, it seems to me that a compromise would suit best; either Norm's suggestion of OL.DNAME/new.name or, perha...

<> A general question: Would it be an idea to swap out all the old nomenclature for the new? Now would be the chance! My main reasons are: 1. to prevent confusion and prevent the evolution of two separate nomenclatures 2. to create a seamless transition once someone wanted to move on to more advanc...

Hi,<> Myother hope is to get all these QL.book authors to regain interest in the QL. A pious thought, indeed ;) IIRC there was some confusion in that book about the RI stack. (Mine only lasted a few days before it split into numerous pieces, so I dont have it.) Perhaps others can confirm? A general...