[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Dynamic loading progress
From: |
Aurélien Aptel |
Subject: |
Re: Dynamic loading progress |
Date: |
Tue, 17 Mar 2015 11:51:44 +0100 |
On Tue, Mar 17, 2015 at 10:52 AM, Eli Zaretskii <address@hidden> wrote:
> 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?
Iterating on a buffer content will need, for each character (I think)
2 funcalls (char-after, forward-char) and a fixnum -> int64_t
conversion. It seems like a non-negligible overhead, but maybe it
isn't, I don't know...
- Re: Dynamic loading progress, (continued)
Re: Dynamic loading progress, Stephen Leake, 2015/03/05
Re: Dynamic loading progress, Stephen Leake, 2015/03/05
Re: Dynamic loading progress, Stephen Leake, 2015/03/16
Re: Dynamic loading progress, Stephen Leake, 2015/03/17
Re: Dynamic loading progress, Stephen Leake, 2015/03/24