* Architectural restructure
@ 2022-09-09 12:05 Karl Dahlke
0 siblings, 0 replies; only message in thread
From: Karl Dahlke @ 2022-09-09 12:05 UTC (permalink / raw)
A couple months ago I wrote an email about architecture, I think that
was the subject.
Nothing is more fundamental than the way we store the lines in the
20 years ago I picked a simple design that was fine relative to the
computers of the day.
Since then it has shown some inadequacies.
Thus, for my birthday, I am trying to majorly restructure edbrowse so
that lines are link list, not all stored in sequence in an array.
No one part of this is hard, but it touches everything and is a lot of
work and will be a lot of testing.
But even on some medium files it will help performance, and perhaps
Example, g/7$/ .m-2 that would take weeks on one of those seq 1000000
files, and no amount of my mass operation fixup would help that one,
but with link lists it would fly.
Moving text about is just changing some link pointers, you see.
And I can get rid of all those specialized mass delete mass join mass
read mass substitute routines.
So it's a lot of work, and testing, and probably chasing down some seg
faults, you know pointers in c and such, and I greatly appreciate your
patience when those appear, but will be worth it.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2022-09-09 12:05 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-09-09 12:05 Architectural restructure Karl Dahlke
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).