|
From: | John W. Eaton |
Subject: | Re: JIT interrupt handler naming |
Date: | Thu, 25 Jul 2013 09:22:26 -0400 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20130116 Icedove/10.0.12 |
On 07/24/2013 09:49 PM, Max Brister wrote:
On Wed, Jul 24, 2013 at 3:16 PM, John W. Eaton <address@hidden <mailto:address@hidden>> wrote: On 07/24/2013 05:19 PM, Max Brister wrote: If we want to support disabling interrupts I do not think the API should be JIT specific. If we add a function to disable interrupts in the interpreter, we should make JIT match that behavior. What is meant by "interrupts" in this context? jwe Anything that sets octave_interrupt_state.
I don't think we should be disabling interrupts by default. Whether code is JIT compiled or not, users will expect that they can interrupt Octave.
jwe
[Prev in Thread] | Current Thread | [Next in Thread] |