On Sat, May 25, 2013 at 1:13 PM, Bram Moolenaar <[email protected]> wrote: > Did you also check for correctness? It's easy to make a regexp engine > that's fast but wrong. And do they possibly run out of memory and > crash? I rewrote the original Vim regexp engine to be iterative instead > of recursive to handle that.
The Vim regexp engines always produced identical results, as did the Perl and Python scripts. There were a few bytes of discrepancies between Vim1/Vim2, Perl/Python, and egrep, but those were mostly due to invalid UTF-8 bytes in the data file. (I had wanted to use the exact same, flawed input data as the original benchmark, but of course this isn't necessary.) More challenging tests for memory usage etc. would be interesting but I have no idea how to go about this. > I need some tests to do profiling, I could perhaps use some of this. Sure, it's free for the taking. -- -- 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.
