[prev in list] [next in list] [prev in thread] [next in thread] 

List:       vim-dev
Subject:    RE: Using threading to remove blocking
From:       Vince Negri <vnegri () asl-electronics ! co ! uk>
Date:       2002-11-14 12:41:38
[Download RAW message or body]


> With many action them spread inside the code:

> action_key( key )
> {

>		if (need_more_keys()) wait_for_keys()


> This is why you can not act on the action_key part of the code. Too many
of
> them.

I don't see the problem. In this model,
wait_for_keys() - which is going on in the
non-GUI thread - just sleeps waiting for
an event (e.g WaitForSingleObject in win32)
to arrive. The whole point is that all the
places in the code which wait_for_keys() do 
not need to change, the change is localised
inside wait_for_keys().

> Do you think it could make it inside the core of vim ? I think this is
> really gui or component specific and it is up to each gui/component
> implementer to deal with it.

I think that creating a version of Vim which is standalone,
but still runs the main event loop in a different thread from
the GUI, is a very good way of testing the idea and finding
out where the critical sections need to go.

Vince



Legal Disclaimer: Any views expressed by the sender of this message are
not necessarily those of Application Solutions Ltd. Information in this 
e-mail may be confidential and is for the use of the intended recipient
only, no mistake in transmission is intended to waive or compromise such 
privilege. Please advise the sender if you receive this e-mail by mistake.

[prev in list] [next in list] [prev in thread] [next in thread]