From: David Kastrup <dak@gnu.org>
To: "Aurélien Aptel" <aurelien.aptel+emacs@gmail.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
Emacs development discussions <emacs-devel@gnu.org>
Subject: Re: More over-engineering
Date: Fri, 27 Nov 2015 18:37:20 +0100 [thread overview]
Message-ID: <878u5jz6lr.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <CA+5B0FN+1mpp20hN=mzm2oi-DVaAavs-4xeRAaU+NUfXQYUBEQ@mail.gmail.com> ("Aurélien Aptel"'s message of "Fri, 27 Nov 2015 18:12:30 +0100")
Aurélien Aptel <aurelien.aptel+emacs@gmail.com> writes:
> On Fri, Nov 27, 2015 at 6:00 PM, Stefan Monnier
> <monnier@iro.umontreal.ca> wrote:
>> Are we really allocating a structure for every Lisp_Object value we pass
>> through the modules API? Why do that?
>
> Look at the old thread for Philip's arguments. As far as I'm
> concerned, we need an indirect pointer to support wide-int
> Lisp_Objects on 32bit platforms. Global reference can still be made
> with the current code. We have a reference counting hash-table to keep
> track of them. Non-global refs are marked explicitely in case the GC
> misses them.
If the same modules cannot be used at the same time for wide-int and
normal int Emacs compilations (can they?), then it would seem that
module code could become significantly simpler when declaring wide-int
and module support mutually exclusive.
--
David Kastrup
next prev parent reply other threads:[~2015-11-27 17:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 17:00 More over-engineering Stefan Monnier
2015-11-27 17:12 ` Aurélien Aptel
2015-11-27 17:37 ` David Kastrup [this message]
2015-11-27 18:02 ` Stefan Monnier
2015-11-27 18:19 ` Eli Zaretskii
2015-11-27 18:53 ` Stefan Monnier
2015-11-27 19:32 ` Eli Zaretskii
2015-11-27 21:55 ` Stefan Monnier
2015-11-28 7:51 ` Eli Zaretskii
2015-11-28 16:22 ` Stefan Monnier
2015-11-28 16:34 ` Eli Zaretskii
2015-11-28 23:13 ` Paul Eggert
2015-11-30 19:40 ` Stefan Monnier
2015-11-30 20:04 ` Eli Zaretskii
2015-11-30 20:39 ` Stefan Monnier
2015-11-30 20:49 ` Eli Zaretskii
2015-12-06 21:16 ` Paul Eggert
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=878u5jz6lr.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=aurelien.aptel+emacs@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.