|
From: | Daniel J Sebald |
Subject: | Re: synchronize gui's debug actions with the octave core thread (bug #41139) |
Date: | Sun, 12 Jan 2014 21:58:59 -0600 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111108 Fedora/3.1.16-1.fc14 Thunderbird/3.1.16 |
On 01/12/2014 09:01 PM, Daniel J Sebald wrote:
Torsten, I see you added a mutex-protected queue to make the debugger more robust. I like the queue and making the debugger more robust has been a goal I worked on. I would like to point out that with the queue you added this is getting very close to what I did with the prototype "background queue". It's not too difficult to add such a thing. Foreground queue is the existing commands visible to the user (e.g., typing at the command line) and background queue would be commands not visible to the user (initiated by the GUI in response to debugger action, for example).
Or I suppose there could simply be just one queue having an option that it be processed visibly or not. But maybe there's a good reason to keep such queues separate if one type were to have a priority over the other.
Dan
[Prev in Thread] | Current Thread | [Next in Thread] |