octave-maintainers
[Top][All Lists]
Advanced

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

Re: Race condition seems to be fixed


From: Daniel J Sebald
Subject: Re: Race condition seems to be fixed
Date: Mon, 21 May 2012 13:35:24 -0500
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 05/21/2012 08:54 AM, Michael Goffioul wrote:
On Mon, May 21, 2012 at 2:48 PM, Jacob Dawid<address@hidden>wrote:

I would regard this as an argument against using the readline input hook.
Comparing and updating the model is an expensive task and we should avoid
doing it whenever possible. When I bloat the symbol table with 10000
variables it takes multiple second to check and rebuild model - you can't
expect it to run every 0.1s at max. Sure, this is a target for optimization
(I think of hashing the symbol table before actually comparing it variable
by variable), but nevertheless we shouldn't stress it I think.


You're right, performances may decrease. That's also why I think it's worth
considering the problem the other way around: let octave tell you when you
need to update the variable browser. In the end, octave is the one who
should know whether something change in the current scope. If you had such
flag, the readline input hook could be very light.

I agree and used that concept in the previous email.

Dan


reply via email to

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