🚀 go-pugleaf

An interesting problem was just described to me.  It seems that the
fileforall operator has a minor bug in it.  As it enumerates the files
on the disk (if you have a NTX), it leaves a copy of the file name on
the stack.  512 files later, kablooie.  The solution of course is to
redifine it so that it does a pop after each call to get the filename.
The problem apparently does not show up unless you have over 512 files
of the disk.

One of Don's clients got bit by that one, and Don dug around until hi
found it.  Watch for a ***VERY*** interesting article to appear shortly
in Byte magazine.


Something to experiment with:  proc caching.  you can fool the font machinery
into caching the result of a proc, and depending on the amount of memory
that you have, it seems possible to cache an ENTIRE page bitmap.  The
ENTIRE page bitmap however takes a LOT of cache, so may or may not work unless
you have megabytes and megabytes of memory, or a hard disk.

Cheers
Woody
a