[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Dynamic loading progress
From: |
Eli Zaretskii |
Subject: |
Re: Dynamic loading progress |
Date: |
Tue, 17 Mar 2015 19:08:29 +0200 |
> From: Stefan Monnier <address@hidden>
> Cc: Aurélien Aptel <address@hidden>,
> address@hidden, address@hidden
> Date: Tue, 17 Mar 2015 12:37:27 -0400
>
> > Actually, most accesses to buffer text do precisely that: access one
> > character at a time. The API typically accepts the buffer position.
> > Why do you think this is inefficient?
>
> For efficient parsing (as done by forward-word, forward-sexp and
> friends), I think you need to keep both the current "charpos" and
> "bytepos", but Elisp interfaces don't give access to this level.
The API we provide for accessing buffer text should handle that as
well. For example, we could model it on FETCH_CHAR_ADVANCE.
Re: Dynamic loading progress, Stephen Leake, 2015/03/24