🚀 go-pugleaf

     A couple of comments on this issue.  First don't use T: for
paging.  This has come to be the place to put small temporary files,
and most users have it assigned to RAM: or some other ram disk. The
best idea would be to use a new name such as SWAP:

     Second, I like the library idea, and doing it right should be
easy and highly portable.  Create a swap.device -- actually two, one
for machines with MMU's and one for machines without.  Programs would
be would be guaranteed that the most recently seeked to page was
valid.  The swap device would have to write all pages opened
read/write when it was necessary to flush them on the non-MMU version,
but could check the hardware flags on the MMU version.

     I lean strongly toward making SWAP: a normal file system, with
the normal protocol for using it being to delete the file instead of
closing it.  If the swap.device flushed pages after a user settable
interval of non-activity this would mean that editors, etc. could
provide automatic file backup with no effort.

     What do people think?  This unfortunately sounds like a project
for Dave Haynie or Bill Hawes who certainly have more to do than they
can handle.  (In particular we really need just one person writing
stuff which manages the page table entries, this MUST be compatible
with setcpu.)

--

					Robert I. Eachus

with STANDARD_DISCLAIMER;
use  STANDARD_DISCLAIMER;
function MESSAGE (TEXT: in CLEVER_IDEAS) return BETTER_IDEAS is...