in reply to Re: Further on buffering huge text files
in thread Further on buffering huge text files

Yes, the filters are known. But the file isn't. The GUI widget should in theory open any huge file, and as fast as possible it should display it and a scroll bar.

Databases won't cut here. It's a pre-written text file that is generated by an outside tool and the GUI should be able to read any such file. Besides, the file grows with time and the GUI should keep up.

  • Comment on Re^2: Further on buffering huge text files

Replies are listed 'Best First'.
Re^3: Further on buffering huge text files
by Anonymous Monk on Mar 09, 2005 at 12:18 UTC
    Can you cache information? If files only grow with time, and your filters are constant, you could record for each line written to the file (or better, for each line read from the file) which filter(s) it matches. Using a bit-vector for each filter, and a single bit per line, you only need 125k of storage per filter for a million line file.
[reply]

In Section Seekers of Perl Wisdom