Re: Images and libraries (was: OBJECTS.FS Question)

On Mar 29, 1:01 am, m...@[EMAIL PROTECTED]
 (Marcel Hendrix) wrote:
> Bruce McFarling <agil...@[EMAIL PROTECTED]
> writes Re: Images and libraries
(was: OBJECTS.FS Question)
> [..]
>
> > However, what I expect from a SAVESYSTEM is to get my codespace and
> > ALLOTted dataspace back as it was when SAVESYSTEM executed, and to
> > have a hook into the initialization routine that runs when the image
> > is reloaded.
>
> I don't see a reason for a hook. Most of the SAVE-SYSTEMs I am familiar
> with work with a boot vector to put the xt of a startup word in.
>
> So provision for persistent objects is possible under program control --
> no system extensions are needed.

Oh! ... you are reading that like an implementer, as a request to
implement something. I'm writing it like a user, as a request to have
something available, by one means or another.

Yes, normally the hook is "already there" by the time SAVE-SYSTEM
appears in the source of the implementation ... unless the SAVE-SYSTEM
is patched in to a system implemented by someone else, the simplest
way to provide it is to build it in at the ground floor.

SAVE-SYSTEM has to *have* that hook available to the user, it doesn't
have to *add* that hook if the hook already exists.