The Sinclair QL Forum

If memory serves. Functions in QDOS need parentheses, but in SMSQ/E does not.

I think the big thing to sort out is the mechanism for loading and executing code that either stops the OS task scheduler and disables interrupts, or both? Also, I'm not clear, though I am sure many here are, if it is possible to return to the operating system after this step or if a restart is ...

At the risk of setting myself up...

Are there any other QLib utilities that are wanted? I don't mean improvements to QLib itself, but things like the add/remove runtimes programs.

Having said that, There is mention in the user manual on the subject of the 'Trace' option, of a possible 'debugger ...

It works a treat, Martin, at least on the program I tried it on. Thank you :)
The removal program appears to remove 114 bytes more than the size of the Qlib_run I just compiled into it. Is that normal?
Adding it again using your program restores the object to the "correct" size, ie 114 bytes less ...

Here's a program that will remove the runtimes.

There is also a small update to the previous program. It's functionally the same, it just correctly displays the QLib version number in QLib V3.45

Version 3.45 has a version number of 3.45a. The version number is stored in the compiled program ...

I don't know if there is any interest in this, But this program will add the runtimes to a compiled program that does not have them.

It makes a hole for the runtimes to fit into, Inserts the runtimes, then goes round patching all the pointers to take into account that parts of the compiled program ...

I have thrown together a BASIC program that takes a Qliberated object program. And if the runtimes are included, it overwrites the runtimes with my Q604F runtimes (renamed for this program as runQ60). By luck, the new runtimes are slightly smaller than the old runtimes, so it will fit over the old ...

But it falls apart with the cache on. I don't know why this happens.

Think of the cache as a lookup table.

You have a cacheline referenced by address so if you had

X = 0x1000XXXX
Y = 0x0000XXXX

Then even though XXXX is the same on both the cache has two different copies. So if you write ...

As I understand it so far, the problem lies in the Q_ERR mechanism and also in the handling of integer FOR loops.

So any program that doesn't use either should work?


QLiberator uses the top 3 bits of the 'value' long word pointer in name table entries as flags.

One bit flags that this name ...

Ideally, to my mind, would be to devise a different scheme for doing this that would work transparently for all systems and without slowing things down by having to test for CPU type and flushing caches..

Any thoughts? Anyone?


The new Q_ERR is probably not noticeably slower than the original ...