unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: block_input for some APIs
Date: Mon, 12 Dec 2016 13:08:45 -0800	[thread overview]
Message-ID: <f30fd48f-0303-94f4-173b-76ac3697557e@cs.ucla.edu> (raw)
In-Reply-To: <831sxdc9hs.fsf@gnu.org>

On 12/12/2016 10:01 AM, Eli Zaretskii wrote:
> Does anyone remember why we block input around calls to functions like
> getpwnam or tzset or fwrite?

I think this dates back to when C-g and/or other handlers called 
longjmp. Since getpwname etc. are not async-signal-safe we needed to 
block input around them, so that C-g's effects were deferred until these 
functions returned. If I'm right, we don't need to block input around 
them any more, since our signal handlers are safer now.

Similarly for MALLOC_BLOCK_INPUT; we should be able to get rid of its 
machinery now.




  reply	other threads:[~2016-12-12 21:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-12 18:01 block_input for some APIs Eli Zaretskii
2016-12-12 21:08 ` Paul Eggert [this message]
2016-12-12 21:48   ` Stefan Monnier
2016-12-12 21:53     ` Daniel Colascione
2016-12-13  3:46       ` Eli Zaretskii
2016-12-13  0:13     ` YAMAMOTO Mitsuharu
2016-12-13  3:43   ` Eli Zaretskii

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=f30fd48f-0303-94f4-173b-76ac3697557e@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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).