On 21/10/13 06:54, Geoff Greer wrote:
If this is the last thing, we'll gladly add it. If it's not the last thing,
please give us a complete list of blockers. Then we can determine if we want to
continue addressing your issues or just maintain our own fork of Vim.
Maintaining your own fork of VIM until this feature has proven long-term
stability
might be the best idea.
Rushing to get it merged when there isn't (to my knowledge) a set of
test cases to
prove its correctness even to a limited degree seems like folly given
the amount
of hard graft it has taken to get VIM to the stability it has today. The
core-dumping
that has been reported to this mailing list alone during its development
has done
nothing to instil confidence in its long-term image with regards to
robustness.
To verify every execution path within any real-time system is
impossible. However,
as VIM as a set of test cases for most of its individual commands, and
any command
can technically be executed from within a timer, I would at least expect
that a set of
test cases be drawn up where the standard test cases, when each is
executed within
a timer, produces the same result as when the test is executed as a
standalone test.
Furthermore, a timer being effectively an "interrupt", there should be
an extra test
case that executes underneath the timer when it fires that can be shown
to produce
a known result when the timer interrupt returns, hence showing that the
execution
of commands within a timer has no unknown side-effects on the
interrupted code.
If this set of test cases could be drawn up and could be run like the
other test cases
I think it's robustness could be proven enough to merge it sooner rather
than later.
--
--
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
