From: Eli Zaretskii <eliz@gnu.org>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: raeburn@raeburn.org, qguo@ualberta.ca, emacs-devel@gnu.org
Subject: Re: Quesition about Lisp_Vector
Date: Sat, 12 Nov 2011 17:53:39 +0200 [thread overview]
Message-ID: <83ehxdfibg.fsf@gnu.org> (raw)
In-Reply-To: <87lirljqee.fsf@uwakimon.sk.tsukuba.ac.jp>
> From: "Stephen J. Turnbull" <stephen@xemacs.org>
> Cc: raeburn@raeburn.org,
> qguo@ualberta.ca,
> emacs-devel@gnu.org
> Date: Sun, 13 Nov 2011 00:45:29 +0900
>
> Eli Zaretskii writes:
>
> > Having string data accessible through indirection allows to relocate
> > strings without affecting callers who have references to Lisp strings
> > in local variables. (This is similar to the ability to relocate
> > buffer text, because buffer text is also accessed through
> > indirection.)
>
> The implementation is similar, but the rationale is not. Buffers
> cannot be allocated by the s[1] trick, because they could not grow
> bigger than the allocated size
I wasn't implying they could. I was just explaining why accessing
string through indirection is important on its own right, not just
because of some optimization. That is very much tangential to the
main issue discussed in this thread, so apologies if it disrupted the
discussion.
> > These abilities are important, because strings, like buffers, can
> > be large, so being able to relocate them during GC helps making
> > more efficient use of the available memory.
>
> I wonder if the problem is not more that there are so many of them
> allocated and deallocated, leading to fragmentation, rather than the
> size.
Yes, that too.
next prev parent reply other threads:[~2011-11-12 15:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-11 6:29 Quesition about Lisp_Vector Qiang Guo
2011-11-11 8:59 ` Andreas Schwab
2011-11-11 9:01 ` Ken Raeburn
2011-11-12 3:42 ` Stephen J. Turnbull
2011-11-12 8:49 ` Eli Zaretskii
2011-11-12 15:45 ` Stephen J. Turnbull
2011-11-12 15:53 ` Eli Zaretskii [this message]
2011-11-13 1:02 ` Ken Raeburn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83ehxdfibg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=qguo@ualberta.ca \
--cc=raeburn@raeburn.org \
--cc=stephen@xemacs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.