Re: Race condition seems to be fixed

[Daniel J Sebald]

On 05/21/2012 07:54 AM, John W. Eaton wrote:
> On 21-May-2012, Jacob Dawid wrote:
>
> |     There are other places where the symbol table could change.  For
> |     example, the loop in eval_string in oct-parse.yy, which is similar to
> |     the one in main_loop in toplev.cc and the one in get_debug_input in
> |     input.cc.  Command history can also change in get_debug_input, though
> |     I don't think it should be changing in eval_string.
> |
> |
> | Why not invoke the callback there, too?
>
> It would probably be OK to do that.  My point was that there may be
> more places than the one that you chose where it is needed.

Noted.


> | There is not need to update the symbol table model (which needs to be 
> processed
> | from the symbol table) too often.
>
> I agree that it may not be necessary to update the list of symbols
> that is displayed in the IDE every time it changes, provided that it
> is updated "often enough".  I'm just not sure what "often enough" is.

For a person sitting watching a long batch job on a monitor, I'd say 
updating variables every two to four seconds would be good.  Other apps 
that users could dream up (e.g., monitoring for changes in a variables)? 
 I don't know.    I will clarify this in a followup post.

Dan