cvs commit: path caching

I committed the code. Right now it just prunes off the oldest element in the array... efficient, but not precise. It should prune off the last accessed element, which means the timestamp needs to be tracked. I have the default limit set to 500 elements, but not sure if that's a good default or not. I'll look at the pruning logic a bit more, maybe next week. This needs to be automatic and efficient. Monte On Fri, 2003-06-20 at 16:26, Wom.bat wrote: > [snipsnap] > > yeah... good idea... > > I think the best solution would be to use a most-frequently-used check and > to throw out the non-used paths, but this would be nonsense as every time > a file is read, the access would need to be logged... so my proposal is to > store the date, and then then throw out the oldest ones when a limit is > reached; this limit and the whole caching functionality should be > customizable, > of course ;) > > David > >