🚀 go-pugleaf

In article <jmk3.724051026@crux1.cit.cornell.edu> jmk3@crux2.cit.cornell.edu (Jay M. Krell) writes:
> >From: vandry@CAM.ORG (Phillip Vandry)
> >Subject: Re: Improving EMACS
>  
> >the loader is supposed to have a check which will force a reload from disk if
> >the disk file is newer than the cached copy.

Which 'loader' do you mean?  The ORCA 'FastFile' system does check the
date/time of the file, so if you copy a new version of an EXE file
into the ORCA utilities directory, it will be loaded instead of the
in-memory version.

Keeping old versions of programs in memory is only a problem with S16
files.

> If you mean the System Loader, I don't think it does. I've heard of people
> having problems debugging because they made their app restartable and instead
> of the loading the latest version, they would accidentally just restart the old
> one from memory. Thus: while developing, keep your apps non-restartable.

Agreed.  I just checked the System Loader chapter of the GS/OS
reference, and can't see anything about the Restart function checking
if the file on disk is newer than the one in memory.

Things get really bad if you have dynamic segments: the System Loader
does check the date, and if it sees that the Dynamic Segment is being
loaded from a 'newer' file, it causes a fatal error.

If I actually want to test the restartability of an application, I
make sure I do a PurgeAll(0x1000) before launching the new version (I
have an APW utility that does this).
-- 
David Empson

Internet: David.Empson@bbs.actrix.gen.nz    EMPSON_D@kosmos.wcc.govt.nz
Snail mail: P.O. Box 27-103, Wellington, New Zealand