4 ms·
I don't think this is about using a gap buffer specifically, but rather about making buffers first-class objects. With respect to the line you quote, what matt
by eadmund 4y ago
I don't think this is about using a gap buffer specifically, but rather about making buffers first-class objects. With respect to the line you quote, what matters is not the specific implementation of a buffer which is chosen, but the fact that code works in terms of buffers rather than strings.
- gumby 4y agoThanks. That (lack of) distinction of course was also in TECO from the beginning, but then again, though I didn't start using TECO myself until the late 70s, even then it wasn't common to think of strings the way they are thought of today. The most common machines at the time had all sorts of strings and buffers of various character widths (on a single machine) and I remember back then I often encountered and used the term "string" in a more abstract way to refer to contiguous set of symbols rather than the more concrete way it is used today that was starting to evolve at that time.