(41) program/function label/name ROM pages "path"

[cdmackay]

(03-02-2019 02:36 AM)rprosperi Wrote:  User programs (CAT-1 and I believe CAT-2) are searched before CAT-3, so a user program can essentially 'take over' a built-in function (e.g. if you make a program with global label "MOD", later when you XEQ "MOD", your function is called, not the OS function).

That aside, I believe the system scans pages 4-F in increasing order looking for a global label to match if executed manually, or when entering a program.

Thanks very much indeed Bob.

I was confused since I'd convinced myself that since AMC_OS/X (for example) appears to take over the CAT & XEQ commands, that meant the ROM modules' pages' FATs must be searched before the OS ROM pages 0–2. I now realise that it doesn't take over those commands, it instead appears to remap/intercept those keys, to call its own versions of those commands. Or something

…

This all came up because of another problem I was having: I'd loaded OSX3, but I wasn't getting its versions of CAT/XEQ. It was definitely loaded: I could call its other functions directly, but I was getting the OS versions of CAT/XEQ when I pressed those keys.

This confused me for some time, before I stumbled over an older post of yours, for which many thanks.

I had the modules mapped in this order:

4 4LIB
6 YFNX
7 OSX3

since I installed YFNX first, of course, and so chose the first free port, then installed OSX3 after.

And that was indeed the problem: I started again, this time with OSX3 in page 6 and YFNX in page 7, and now the CAT & XEQ keys are getting me the OSX3 versions. So thank you again for that.

[I'm aware of the restrictions on pages 6 & 7, but I don't (yet) need either printer or HP-IL support, and both YFNX & OSX3 are officially page6-safe]

If Monte or Ángel are reading: would you please consider making a note of the OSX3/YFNX/PWRX page-ordering restrictions in one of the relevant manuals? Apologies if it is in there, but I don't remember any mention of OSX3 needing to be in a lower page than YFNX, for example. There may have been an example showing it that way, but not that it had to be that way.

All good now, thanks again.