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

In article <96221626203559@[EMAIL PROTECTED]
>, Marcel Hendrix <mhx@[EMAIL PROTECTED]
>
wrote:
>Bruce McFarling <agila61@[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.

It depends. I can understand Anton Ertl's argument. You want
SAVE-SYSTEM to save a snapshot of the system and be done with it.
If your system understands ALLOCATE, the allocated memory should
be transparently in the snapshot.

Mostly I use SAVE-SYSTEM via
        lina -c ape.frt
In this case I may take measures to prevent static 1 Megabyte
arrays in the resulting ape (ape.exe for MS fans) even if I have
to write a special initialisation. Then the mindset is compiling
a program, not taking a snapshot.

>-marcel

Groetjes Albert

--
-- 
Albert van der Horst, UTRECHT,THE NETHERLANDS
Economic growth -- like all pyramid schemes -- ultimately falters.
albert@[EMAIL PROTECTED]
 &=n http://home.hccnet.nl/a.w.m.van.der.horst