unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Philipp Stephani <p.stephani2@gmail.com>
To: "Aurélien Aptel" <aurelien.aptel+emacs@gmail.com>,
	"Elias Mårtenson" <lokedhs@gmail.com>,
	"Tom Tromey" <tom@tromey.com>
Cc: Joakim Jalap <joakim.jalap@fastmail.com>,
	emacs-devel <emacs-devel@gnu.org>
Subject: Re: GNUS Kerberos support, native GSSAPI?
Date: Sun, 23 Apr 2017 17:31:28 +0000	[thread overview]
Message-ID: <CAArVCkQ_wOLKz6W_Mii3Tceh7o8CK6k3sh2S3qXMYOQJaVLQRA@mail.gmail.com> (raw)
In-Reply-To: <CA+5B0FOpvc9DogPRzw8kWHwwxV49or7DW3FbYPW2q5yE74+fsg@mail.gmail.com>

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

Aurélien Aptel <aurelien.aptel+emacs@gmail.com> schrieb am Fr., 10. Feb.
2017 um 19:21 Uhr:

>
> > I tried putting all the interned symbols in a struct and passing
> specifying
> > it as a data pointer when constructing the functions. However, this did
> not
> > work as the emacs_value objects does not seem to have a lifetime outside
> of
> > the invocation of a native function. I haven't seen this documented
> > anywhere, so that was a bit surprising at first. The fact that this
> failed
> > is the reason you see all the calls to env->intern everywhere.
>
> This was not always the case: the behaviour was changed by Philipp at
> some point. We still have the make_global_ref and free_global_ref
> functions in the API, which serve no purpose as a result (correct me
> if I'm wrong).
>

Using make_global_ref is definitely intended to make objects usable across
environments (i.e. you should be able to use them in any thread whenever
any environment is active). If that's not the case, please report a bug.
The alternative of using intern everywhere is also not too bad because it's
much simpler and more obvious (no global state that you have to track
carefully). I'd recommend only switching to global references if there is a
significant performance penalty.

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

  reply	other threads:[~2017-04-23 17:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-06 10:03 GNUS Kerberos support, native GSSAPI? Elias Mårtenson
2017-02-06 14:22 ` Stefan Monnier
2017-02-07  3:14   ` Elias Mårtenson
2017-02-07 14:16     ` Stefan Monnier
2017-02-09  4:45       ` Elias Mårtenson
2017-02-09 11:55         ` Joakim Jalap
2017-02-09 13:02           ` Elias Mårtenson
2017-02-10 18:21             ` Aurélien Aptel
2017-04-23 17:31               ` Philipp Stephani [this message]
2017-04-24 10:53                 ` Elias Mårtenson

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=CAArVCkQ_wOLKz6W_Mii3Tceh7o8CK6k3sh2S3qXMYOQJaVLQRA@mail.gmail.com \
    --to=p.stephani2@gmail.com \
    --cc=aurelien.aptel+emacs@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=joakim.jalap@fastmail.com \
    --cc=lokedhs@gmail.com \
    --cc=tom@tromey.com \
    /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).