Re: lynx-dev dev17 clue?

[Henry Nelson]

> away the tables you do not want.  I am surprised you have never tried that.

Time constraints.  Some weekend I'll get a patch made to automate things.
Leonid already told us how to do it, and I have his post saved for future
reference.  Thanks for your recommendations on where to start.

> You may also want to try to reduce MAXHIST and MAXLINKS in userdefs.h.
> But I think the effect will not be visible in binary size, only in run-time
> memory need - and may well be insignificant.

MAXLINKS at least is very significant for stressed machines like mine get
when I have a bunch of students on.  I set it at 5.

> > What does this mean -- more toward CPU, or more toward memory, or neither?
> 
> More heap allocation (malloc and friends) means likely more CPU time,
> but details would depend on the implementation of those functions in

hmm.  Memory is getting pretty cheap these days.  (But so are used CPUs.)
Picked up a 90MHz pentium for $12, and 32MB(16x2)-60ns memory for $35.

__Henry