unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
To: martin rudalics <rudalics@gmx.at>
Cc: 14666@debbugs.gnu.org
Subject: bug#14666: 24.3.50; emacs_backtrace.txt
Date: Wed, 19 Jun 2013 20:46:16 +0200	[thread overview]
Message-ID: <CAAeL0SRNxFKMSg2qnZLhc0etbgHv1E7jYEZ7Z8xRV1+kh=bh-g@mail.gmail.com> (raw)
In-Reply-To: <51C1F101.80806@gmx.at>

On Wed, Jun 19, 2013 at 7:57 PM, martin rudalics <rudalics@gmx.at> wrote:

> If the input thread wants to calculate a window's size and
> the Lisp thread deletes the window under its feet, we're lost anyway.

Sure.

My point is that these macros hide what's happening. I suppose if someone writes

 if (BUFFERP (b))
    /* do something with b */

in the main window procedure of Emacs, it is easier to think about
race conditions and such than when using macros which hide lots and
lots of detail.

    J





  reply	other threads:[~2013-06-19 18:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-19 15:04 bug#14666: 24.3.50; emacs_backtrace.txt Drew Adams
2013-06-19 15:14 ` Juanma Barranquero
2013-06-19 16:10   ` Eli Zaretskii
2013-06-19 16:47     ` Eli Zaretskii
2013-06-19 16:48       ` Juanma Barranquero
2013-06-19 17:08         ` Eli Zaretskii
2013-06-19 17:23           ` Juanma Barranquero
2013-06-19 17:57             ` martin rudalics
2013-06-19 18:46               ` Juanma Barranquero [this message]
2013-06-19 20:59                 ` martin rudalics
2013-06-19 19:51               ` Eli Zaretskii
2013-06-19 19:44             ` Eli Zaretskii
2013-06-19 19:46               ` Juanma Barranquero
2013-06-19 20:03               ` Juanma Barranquero
2013-06-19 17:44         ` martin rudalics
2013-06-19 19:47           ` Eli Zaretskii
2013-06-19 20:58             ` martin rudalics

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='CAAeL0SRNxFKMSg2qnZLhc0etbgHv1E7jYEZ7Z8xRV1+kh=bh-g@mail.gmail.com' \
    --to=lekktu@gmail.com \
    --cc=14666@debbugs.gnu.org \
    --cc=rudalics@gmx.at \
    /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).