🚀 go-pugleaf

In article <DEVEN.89Mar1180622@daniel.pawl.rpi.edu> shadow@pawl.rpi.edu (Deven Thomas Corzine) writes:
>I working on writing a shell and a support library, and would like to
>be able to use seglists in the 1.3 Resident list.  I DON'T want to
>have to use the V1.3 run command, or the DOS Execute() function.  I
>want to be able to get at the list of resident seglists, usecounts and
>names, and to be able to modify said list.  Therefore, I'm looking for
>both the data structures used by the Resident command (and how to find
>them) and any mutual exclusion conventions needed to modify the list.
>

I'm planning to have some extensive revisions of the way resident
works for 1.4.  Therefore, please don't use the DOS resident list.
Right now we're the only ones using it, so we can be fairly
free with changes. (well, MCC uses it, but they hang aliases
off it, which is incorrect anyway :-)  )  So I'd prefer to
keep quiet about the data structures, locking conventions, and
internal workings of the shell on this.  Instead I suggest
you set up a resident list for your shell, and hang it either
off a public message port, or a resource.

>Also, when you run a resident command from the CLI or run, does Exit()
>have a check for a resident seglist to decide whether or not to
>UnLoadSeg() the seglist, or does it pass control back to the CLI or

C programs should not be using Exit() which never matches the
exit things your compiler startup wants you to clean up.

The shell has the responsibility of unloading (or not unloading
in the case of resident segments) the programs.

I have this vision of a resident handler ... :-)
-- 
andy finkel		{uunet|rutgers|amiga}!cbmvax!andy
Commodore-Amiga, Inc.

"Question of the Day : When will we get a device independent graphics standard
 that is fast enough to actually be useful ?"

Any expressed opinions are mine; but feel free to share.
I disclaim all responsibilities, all shapes, all sizes, all colors.