unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Philipp Stephani <p.stephani2@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: Modules: definition of emacs_value
Date: Wed, 02 Mar 2016 18:14:48 +0000	[thread overview]
Message-ID: <CAArVCkTva2tS3YqUfuPUagWvqJf2ii2df_OuC7VCt--Z-SiHfg@mail.gmail.com> (raw)
In-Reply-To: <jwvy4a1ymld.fsf-monnier+gmane.emacs.devel@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 701 bytes --]

Stefan Monnier <monnier@iro.umontreal.ca> schrieb am Mi., 2. März 2016 um
15:37 Uhr:

> > I don't like giving users raw Lisp_Objects.  I really don't like making
> > 32-bit callers cope with 64-bit values.  If emacs_value is a pointer, we
> > have complete freedom with respect to runtime behavior.  Putting a
> > Lisp_Object directly in an emacs_value is a false economy.
>
> This assumes that the performance cost of the API is negligible.
> Currently, the performance already sucks rocks because of all the extra
> condition-case going on (thanks to your lobbying), but I don't think we
> should add insult to injury.
>
>
Is this just speculation, or do you have actual benchmarks?

[-- Attachment #2: Type: text/html, Size: 1023 bytes --]

  reply	other threads:[~2016-03-02 18:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-29 23:03 Modules: definition of emacs_value Philipp Stephani
2016-02-29 23:15 ` Daniel Colascione
2016-03-02 14:37   ` Stefan Monnier
2016-03-02 18:14     ` Philipp Stephani [this message]
2016-03-04  1:04       ` Stefan Monnier
2016-03-04  1:24         ` John Wiegley
2016-03-02 18:30   ` Philipp Stephani
2016-03-02 20:14     ` Daniel Colascione
2016-03-31 17:32       ` Philipp Stephani

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=CAArVCkTva2tS3YqUfuPUagWvqJf2ii2df_OuC7VCt--Z-SiHfg@mail.gmail.com \
    --to=p.stephani2@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 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).