🚀 go-pugleaf

idg10@cl.cam.ac.uk (I.D. Griffiths) writes:

> You're missing the fact that !Edit runs as a normal application and not a
> module application...  Although maybe it doesn't, it's hard to tell
> since I think the task manager only uses memory allocation to decide
> (i.e. 0k of app space means it's a module task...).  I don't know
> precisely what edit does, although it is quite likely to have some
> assembler patching...

It certainly appears to run as a module task which claims a chunk of
application space for workspace. It is started with the '*Desktop_Edit'
command, which you shouldn't use :-). Aside: It occurrs to me - since all
tasks must be started with a * command, why don't Acorn put a
'*RunModule <modulename>' command into the kernal, rather than each
module having to supply it's own '*Desktop_<name>' command? You would
still need the mechanism on startup of checking to see if you were
already running, etc, but this would eliminate a lot of superfluous
command tables being checked every time a * command is issued...

BTW There is a minor related bug with the Task Manager. Normally Pinboard
starts out being listed in the task manager as a module task, which is
fine. If you then load a backdrop into pinboard, the Task Manager moves
Pinboard into the application tasks area, as Pinboard is now using
application area. But now if you kill the backdrop Pinboard *stays* in
the application tasks area with a 0k wimpslot.

--
Confusious say: "Man who sit on hot stove is better off"