On Tuesday, December 10, 2013 11:22:53 AM UTC-6, ZyX wrote: > On Dec 10, 2013 7:57 PM, "Ben Fritz" <[email protected]> wrote: > > > > On Tuesday, December 10, 2013 6:55:53 AM UTC-6, Christian Brabandt wrote: > > > On Tue, December 10, 2013 13:24, Marc Weber wrote: > > > > Have you tried cyclic linked lists/ dictionaries like these samples ? > > > > > > > > fun! CyclicDictionary(count) > > > > let start = {} > > > > let prev = start > > > > for i in range(1, a:count) > > > > let new_ = {'prev': prev} > > > > endfor > > > > let start.prev = new_ > > > > > > > > return start > > > > endf > > > > > > > > > > > > fun! CyclicList(count) > > > > let lists = map(range(0,a:count-1), '[]') > > > > > > > > for i in range(0, a:count-1) > > > > call add(lists[i], lists[(i+1) % a:count]) > > > > call add(lists[i], lists[(i-1+a:count) % a:count]) > > > > endfor > > > > return lists[0] > > > > endf > > > > > > > > let dict = CyclicDictionary(100000) > > > > let list = CyclicList(100000) > > > > > > > > if dict and list are both read back correctly neither size nor cycles > > > > seem to be a problem .. > > > > > > Oh wow, simply sourcing that in my Windows gvim (7.4.0) crashes it. > > > > > > > I can reproduce on a self-compiled 7.4.113 (HUGE features with dynamic > > python and perl). But it is strange. I source the script and everything > > seems fine. I can enter and exit insert mode without problem. About 30 > > seconds later, Vim crashes (when I'm not actually doing anything in > > Vim). > > Does :call garbagecollect(1) trigger the crash?
Yes. Adding "call garbagecollect()" to the end of the script makes Vim crash immediately instead of after a long delay, when sourcing. -- -- 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.
