|
From: | Daniel Colascione |
Subject: | Re: trunk r116456: Improve dbus performance on synchronous calls |
Date: | Mon, 17 Feb 2014 13:42:06 -0800 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 |
On 02/17/2014 01:08 PM, Michael Albinus wrote:
address@hidden writes:Why `push'? It adds the event on top of `unread-command-events', changing the event order when there are already events in that list.Hrm. I was getting it from sit-for:Nope. You're right: fixed. Thanks for pointing that out.Maybe `sit-for' is wrong then as well? I haven't checked ever (and situations, where `unread-command-events' contains more than one event seem to be rare).
sit-for is right: it's reading one event, then immediately sticking it back on the queue. Push is exactly the right operation there.
[Prev in Thread] | Current Thread | [Next in Thread] |