[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#14666: 24.3.50; emacs_backtrace.txt

From: Eli Zaretskii
Subject: bug#14666: 24.3.50; emacs_backtrace.txt
Date: Wed, 19 Jun 2013 22:51:49 +0300

> Date: Wed, 19 Jun 2013 19:57:21 +0200
> From: martin rudalics <address@hidden>
> CC: Eli Zaretskii <address@hidden>, address@hidden
>  > It is obvious that using these macros in a place where
>  > their assumptions can be violated is a no-no (as witnessed by this
>  > crash).
> I don't think that macros are important here.  They simply obscure the
> backtrace.

Not only that.  They also evaluate the same expressions several times,
assuming that the same expression always evaluates to the same value.

> 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.

I don't think we are lost in this particular case, see the
documentation of ImmSetCompositionWindow function that is being called

reply via email to

[Prev in Thread] Current Thread [Next in Thread]