From: joakim@verona.se
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: emacs-devel@gnu.org, Dmitry Gutov <dgutov@yandex.ru>
Subject: Re: /srv/bzr/emacs/emacs-24 r111116: eval-after-load fix
Date: Fri, 04 Jan 2013 11:41:10 +0100 [thread overview]
Message-ID: <m3mwwpkz7d.fsf@chopper.vpn.verona.se> (raw)
In-Reply-To: <m2pq1lnv6u.fsf@igel.home> (Andreas Schwab's message of "Fri, 04 Jan 2013 10:39:37 +0100")
Andreas Schwab <schwab@linux-m68k.org> writes:
> Dmitry Gutov <dgutov@yandex.ru> writes:
>
>> IIUC, adding stuff to purespace makes GC's job simpler, as it doesn't have
>> to keep track of references to those objects. Is that the only supposed
>> benefit?
>
> The main advantage of the pure space is that it is a compact read-only
> space which can be shared by the OS between all emacs processes.
My first thought when I read this was that this is not so important
these days. Then it occured to me that maybe the opposite is true:
several newer Emacs frameworks rely on spawning new emacs processes.
>
> Andreas.
--
Joakim Verona
prev parent reply other threads:[~2013-01-04 10:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1TqZR5-0007qr-6Z@vcs.savannah.gnu.org>
2013-01-03 1:27 ` /srv/bzr/emacs/emacs-24 r111116: eval-after-load fix Dmitry Gutov
2013-01-03 1:38 ` Glenn Morris
2013-01-03 3:27 ` Stephen J. Turnbull
2013-01-04 5:34 ` Dmitry Gutov
2013-01-04 10:58 ` Stephen J. Turnbull
2013-01-04 18:10 ` Stefan Monnier
2013-01-04 22:32 ` Dmitry Gutov
2013-01-05 2:54 ` Stephen J. Turnbull
2013-01-04 5:32 ` Dmitry Gutov
2013-01-04 9:39 ` Andreas Schwab
2013-01-04 10:41 ` joakim [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3mwwpkz7d.fsf@chopper.vpn.verona.se \
--to=joakim@verona.se \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=schwab@linux-m68k.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).