Norman Dunbar writes:
<>
> I am one very puzzled (and p*ss*d off) programmer I can tell you.
> Does QLiberator work under SMSQ - I've seen mentions of using bit 31 in
> addresses etc, but my experiences today have been horrendous - I've wasted
a
> lunch hour and two (yes two) tea breaks trying to re-compile this program
!
>
> (I'm going off Malcolm now as well - he suggested the changed :o) - joke
!)
>
> Any Ideas anyone ?
Here are some of my spells:
I find a lot of the Qlib problems Ive had (and solved) have had to do with
the Qlib stack getting into a mess, and hanging the program or the whole
environment, due to lack of memory. Perhaps the stack underflows into the
channel table, or something.. Anyway, by increasing the number of channels,
eg using the $$chan directive, most weird errors and myserious lockups
seem to vanish. Nowadays I add at least two to the number of channels
actually used. The $$stac directive also plays a part, so on compiling a new
program for the first time, I keep both chan and stac big, and then work my
way down (with the aid of the compile-with-stats facility at the main
console) until the program starts playing up. Then I add a good dollop of
space back in. I find with the new colour drivers some(?) programs seem to
require more stack space than previously. BTW I use V2.35. Id say its
compatible on the whole. Isnt there a V2.36?
Does anyone know the qsave sav-file format? I know most of it, but dont
understand the significance of the second word (version or facilities?), nor
some of the extra bits in the variable types' top nibble. Are files qsaved
on Minerva interchangable with SMSQ ones (integer tokenisation, etc)?
Per
