On Sat, 11 May 2013 15:44:10 +0200, Xavier de Gaye <xdeg...@gmail.com> wrote: > An alternative would be to allow any python thread to call the vim-python > interface through message passing.
That indeed is also possible, but for it to work properly you need to create interface for waking the main thread from iowait, which again means that you need to change the eventloop implementation anyway. And since you can implement message passing and multithreading whenever you have proper pluggable eventloop (assuming the platform supports something akin to socketpair() for waking) I don't see the point of having way more complicated and non-standard interface via message passing. Not to mention it would force programmers to spend extra effort on data structure locking, which is quite well known to be error-prone and produces hard to debug bugs. The point of implementing new eventloop based on libevent is that you can then use it transparently from any scripting language vim supports (except for VimL itself) without any extra code in each language. Just pull in whatever wrapper the language has for libevent and you're set to go. Not that I'm strictly against such feature, it will still be way better than any updatetime hack out there, it just seems more tedious to both to implement and subsequently to use. Thanks for reply. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
