From: "Jan D." <jan.h.d@swipnet.se>
Cc: mituharu@math.s.chiba-u.ac.jp, emacs-devel@gnu.org
Subject: Re: alarm_signal_handler is called too frequently
Date: Thu, 4 Nov 2004 23:41:02 +0100 [thread overview]
Message-ID: <9AF2796A-2EB2-11D9-A7C3-000D93505B76@swipnet.se> (raw)
In-Reply-To: <E1CPOYF-0005kX-AB@fencepost.gnu.org>
I made my question very unclear, I'll try again. Sorry if this is
obvious for others, but I just don't understand.
Say we have three functions, aL, bL and cL, all written in Lisp (hence
the L). Now, obviously aL calling bL calling cL is safe (<-- denotes
return, not cL calls bL).
1:
aL bL cL
| --> | |
| | --> |
| | <-- |
| <-- | |
If we replace bL with code in C instead, is this safe?
2:
aL bC cL
| --> | |
| | --> |
| | <-- |
| <-- | |
I think it must be, there are places in Emacs where C code calls Lisp
functions. Say now that bC calls cL within BLOCK/UNBLOCK_INPUT:
3:
aL bC cL
| --> | |
| BLOCK |
| | --> |
| | <-- |
| UNBLOCK |
| <-- | |
Why is this unsafe, if 2 was safe (if indeed it is)? It is not as
though the signal handler is calling Lisp code, that is obviously
unsafe. But when a dialog or popup menu is popped up, the signal
handler is not involved in processing X events, it is all done inside
bC.
I'm sorry if this is a stupid question, but I just don't get it.
Jan D.
next prev parent reply other threads:[~2004-11-04 22:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 1:15 alarm_signal_handler is called too frequently YAMAMOTO Mitsuharu
2004-10-13 14:43 ` Richard Stallman
2004-10-14 5:16 ` YAMAMOTO Mitsuharu
2004-10-17 9:36 ` YAMAMOTO Mitsuharu
2004-10-25 13:13 ` Richard Stallman
2004-10-25 14:38 ` Jan D.
2004-10-27 10:47 ` Richard Stallman
2004-10-28 18:02 ` Jan D.
2004-10-29 1:37 ` YAMAMOTO Mitsuharu
2004-10-29 7:00 ` Jan D.
2004-10-29 8:24 ` YAMAMOTO Mitsuharu
2004-11-01 7:24 ` Richard Stallman
2004-11-01 9:06 ` Jan D.
2004-11-01 12:21 ` Jan D.
2004-11-02 14:08 ` Richard Stallman
2004-11-02 21:56 ` Jan D.
2004-11-03 17:04 ` Richard Stallman
2004-11-03 17:26 ` Jan D.
2004-11-04 20:42 ` Richard Stallman
2004-11-04 22:41 ` Jan D. [this message]
2004-11-05 12:36 ` Kim F. Storm
2004-11-06 5:22 ` Richard Stallman
2004-11-04 13:02 ` Jan D.
2004-10-31 9:42 ` Richard Stallman
2004-10-31 15:11 ` Jan D.
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=9AF2796A-2EB2-11D9-A7C3-000D93505B76@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=emacs-devel@gnu.org \
--cc=mituharu@math.s.chiba-u.ac.jp \
/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).