From: "Jan D." <jan.h.d@swipnet.se>
Cc: Sean O'Rourke <sorourke@cs.ucsd.edu>,
Emacs-Devel Devel <emacs-devel@gnu.org>
Subject: Re: [patch] enhanced mac drag-n-drop
Date: Sun, 10 Apr 2005 07:47:04 +0200 [thread overview]
Message-ID: <8a42ee34b91cc0fa06a4a6f13a3e903b@swipnet.se> (raw)
In-Reply-To: <wl7jjbwfpc.wl%mituharu@math.s.chiba-u.ac.jp>
> Thanks. I've just encountered a situation that I'd like to use
> code conversion, which may call Feval, inside XTread_socket.
> That is related to a callback function for the clipboard, and it
> should complete code conversion before it returns. Thus passing
> events to Lisp does not work here.
>
> Is GC the only reason to avoid Feval inside XTread_socket? If
> so, is it possible to use code conversion together with
> inhibit_garbage_collection?
The main reason AFAIK is that the Lisp interpreter is not reentrant.
If some Lisp code is preempted by a signal and then XTread_socket calls
Lisp code, you have two instances of the Lisp interpreter running in
parallell, and it is not designed for that. Much like not being thread
safe.
Jan D.
next prev parent reply other threads:[~2005-04-10 5:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-06 0:53 [patch] enhanced mac drag-n-drop Sean O'Rourke
2005-04-06 11:37 ` Stefan Monnier
2005-04-06 16:17 ` Jan D.
2005-04-06 18:12 ` Sean O'Rourke
2005-04-06 19:22 ` Jan D.
[not found] ` <uwtrfsjhv.fsf@jasonrumney.net>
2005-04-07 4:36 ` Jan D.
2005-04-07 6:59 ` Jason Rumney
2005-04-07 13:33 ` Sean O'Rourke
2005-04-07 15:18 ` Jan D.
2005-04-11 19:39 ` Jan D.
2005-04-09 11:00 ` YAMAMOTO Mitsuharu
2005-04-09 13:46 ` Jan D.
2005-04-10 2:03 ` YAMAMOTO Mitsuharu
2005-04-10 5:47 ` Jan D. [this message]
2005-04-10 14:42 ` Stefan Monnier
2005-04-11 1:56 ` Richard Stallman
2005-04-11 3:35 ` Stefan Monnier
2005-04-11 9:49 ` YAMAMOTO Mitsuharu
2005-04-11 16:39 ` Stefan Monnier
2005-04-12 8:24 ` YAMAMOTO Mitsuharu
2005-04-12 2:58 ` Richard Stallman
2005-04-12 3:59 ` Stefan Monnier
2005-04-12 17:24 ` Richard Stallman
2005-04-11 1:56 ` Richard Stallman
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=8a42ee34b91cc0fa06a4a6f13a3e903b@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=emacs-devel@gnu.org \
--cc=sorourke@cs.ucsd.edu \
/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).