unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Elias Mårtenson" <lokedhs@gmail.com>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: "Aurélien Aptel" <aurelien.aptel+emacs@gmail.com>,
	"Joakim Jalap" <joakim.jalap@fastmail.com>,
	"Tom Tromey" <tom@tromey.com>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: GNUS Kerberos support, native GSSAPI?
Date: Mon, 24 Apr 2017 18:53:09 +0800	[thread overview]
Message-ID: <CADtN0WLMznkhsnN4Mk2HD_fVUSDwZzTm=OFkZBEjzFF2+LVYCQ@mail.gmail.com> (raw)
In-Reply-To: <CAArVCkQ_wOLKz6W_Mii3Tceh7o8CK6k3sh2S3qXMYOQJaVLQRA@mail.gmail.com>

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

On 24 April 2017 at 01:31, Philipp Stephani <p.stephani2@gmail.com> wrote:


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

Thanks. I'll stick with env->intern then. :-)

I'll also keep your point in mind, and if I see the issue again I'll send a
bug report.

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

      reply	other threads:[~2017-04-24 10:53 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
2017-04-24 10:53                 ` Elias Mårtenson [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='CADtN0WLMznkhsnN4Mk2HD_fVUSDwZzTm=OFkZBEjzFF2+LVYCQ@mail.gmail.com' \
    --to=lokedhs@gmail.com \
    --cc=aurelien.aptel+emacs@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=joakim.jalap@fastmail.com \
    --cc=p.stephani2@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).