Hi Bram,
> > > On Tue, Sep 22, 2020 at 12:40 PM John Marriott < > [email protected]> > > wrote: > > > > > > > > On 23-Sep-2020 04:34, Bram Moolenaar wrote: > > > > Patch 8.2.1726 > > > > Problem: Fuzzy matching only works on strings. > > > > Solution: Support passing a dict. Add matchfuzzypos() to also get > the > > > match > > > > positions. (Yegappan Lakshmanan, closes #6947) > > > > > > > After this patch, mingw64 (gcc 10.2) throws this warning: > > > <snip> > > > gcc -c -I. -Iproto -DWIN32 -DWINVER=0x0603 -D_WIN32_WINNT=0x0603 > > > -DHAVE_PATHDEF -DFEAT_NORMAL -DHAVE_STDINT_H -pipe -march=native -Wall > > > -O3 -fomit-frame-pointer -freg-struct-return -fpie -fPIE > > > -DFEAT_GUI_MSWIN -DFEAT_CLIPBOARD -D__USE_MINGW_ANSI_STDIO search.c -o > > > gobjnative/search.o > > > search.c: In function 'fuzzy_match_recursive.constprop': > > > search.c:4320:54: warning: 'neighbor' may be used uninitialized in this > > > function [-Wmaybe-uninitialized] > > > 4320 | neighborSeparator = neighbor == '_' || neighbor == ' '; > > > | ~~~~~~~~~^~~~~~ > > > search.c:4296:10: note: 'neighbor' was declared here > > > 4296 | int neighbor; > > > | ^~~~~~~~ > > > </snip> > > > > > > The 'neighbor' variable can be initialized to zero. > > I made it a space, does that also work? I guess it doesn't really > matter. > > > Yes. It doesn't really matter. The neighbor variable should be initialized to a proper character value. - Yegappan -- -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/CAAW7x7nxpAX%2B1h6GcJzZT4zCjYTOWgOQtX%3DEX03boKhZkcjhSw%40mail.gmail.com.
