Loading ...
Sorry, an error occurred while loading the content.

Re: [PATCH] Asynchronous functions (settimeout, setinterval, and cancelinterval)

Expand Messages
  • Nikolay Pavlov
    ... the patch is an almost asynchronous feature, or at least a completition of the already existing asynchronous features of vim. With all the autocmd-events
    Message 1 of 105 , Sep 11, 2013
    • 0 Attachment


      On Sep 11, 2013 1:27 PM, "Thomas" <wienecke.t@...> wrote:
      >
      > On 11 September 2013 00:18, Nikolay Pavlov <zyx.vim@...> wrote:
      >>
      >> Why do you keep calling it async?
      >
      > Referring to the introduction to asynchronous programming linked below, the patch is an almost asynchronous feature, or at least a completition of the already existing asynchronous features of vim. With all the "autocmd-events" we already have the posibillity to run code asynchronous.
      > Anyway asynchronous doesn't mean threaded, as far as I know and referring again to the link. That a two different concepts (which you can combine if you want).
      >
      > http://cs.brown.edu/courses/cs168/f12/handouts/async.pdf

      Now please show how you can run one sequence of commands interleaved with the other with this patch. Function that runs with given interval blocks everything until it completes, same for autocommands. You cannot say you implement preemptive multitasking if you have to wait for one task to complete before starting the other. It is not async feature.

      You can, of course, do some hacks with saving a state, exiting and resuming, but you will then be forced to *emulate* preemption without any support from vim. I used to have some simple emulation even without such patch.

      Note though that I would really like it merged. But not with the current name.

      > --
      > --
      > 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+unsubscribe@....
      > For more options, visit https://groups.google.com/groups/opt_out.

      --
      --
      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+unsubscribe@....
      For more options, visit https://groups.google.com/groups/opt_out.
    • Bjorn Tipling
      By the way if anyone wants to check out or help us maintain the fork with timers until Bram is ready to check out the patch, it s here:
      Message 105 of 105 , Nov 25, 2013
      • 0 Attachment
        By the way if anyone wants to check out or help us maintain the fork with timers until Bram is ready to check out the patch, it's here:

        https://github.com/Floobits/vim

        It's a month behind at the moment, but we will keep it up to date.

        --
        --
        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+unsubscribe@....
        For more options, visit https://groups.google.com/groups/opt_out.
      Your message has been successfully submitted and would be delivered to recipients shortly.