🚀 go-pugleaf

In article <1990Oct13.031948.25857@isis.cs.du.edu> chanson@isis.UUCP (Chris Hanson) writes:
> 'real memory') passing it a 'size' parameter, (oh, about 80 x 25 or about
> 2k, more than enough text to fill the screen) a pointer to where our
> virtual.library should put the data...

Nope. It shuld return a pointer to a "locked chunk" of that size. What if you
ask for an overlapping chunk, later? Also, provide calls to unlock a chunk
(I'm not going to use this chunk for a while... move it or swap it out
if you want) and mark a chunk readonly (don't bother to swap it out).

>   As you insert characters (say, adding in one of these little notes-in-
> parenthesis things that I use alot), the editor displays the changes
> onscreen, while doing a virtual.library InsertChunk(), telling virtual.
> library where, how big, and what was inserted.

Hold it right there... is this a VM library or a buffer-management library?
Both are useful, but they're not the same thing. For one thing, addresses
in a buffer can change if you do inserts... so you need to deal with handles
or have the ability to set marks. What if you have two chunks and insert
stuff into the first one? In a VM library, that's just pushed data past the
second page. In a buffer library, the second page moves down with it.

If you do this, see if you can make it portable... and crosspost to
alt.lang.cfutures. This is handy stuff on any system... not just an Amiga.
-- 
Peter da Silva.   `-_-'
<peter@sugar.hackercorp.com>.