[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Overlays as an AA-tree
From: |
Stefan Monnier |
Subject: |
Re: Overlays as an AA-tree |
Date: |
Wed, 21 Sep 2016 14:41:19 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux) |
> My point was that if overlay edges are implemented as markers, their
> movement with buffer changes is for free, and doesn't need to be
> reimplemented.
Keeping overlays in a tree means that the tree has to be updated when
overlays move, so "their movement with buffer changes is for free"
doesn't apply. More to the point, his code makes overlays not use
markers any more (and I agree with this choice).
> in any case, I was only talking about the overlay start/end
> implementation, not about the byte position of markers in general.
I was talking specifically about keeping byte-positions for overlays.
Stefan
- Re: Overlays as an AA-tree, (continued)
Re: Overlays as an AA-tree, Stefan Monnier, 2016/09/21
Re: Overlays as an AA-tree, Joakim Jalap, 2016/09/22
- Re: Overlays as an AA-tree, Stefan Monnier, 2016/09/22
- Re: Overlays as an AA-tree, Joakim Jalap, 2016/09/22
- Re: Overlays as an AA-tree, Stefan Monnier, 2016/09/22
- Re: Overlays as an AA-tree, Joakim Jalap, 2016/09/27
- Re: Overlays as an AA-tree, Stefan Monnier, 2016/09/27
- Re: Overlays as an AA-tree, Eli Zaretskii, 2016/09/27
- Re: Overlays as an AA-tree, Joakim Jalap, 2016/09/28