Michael Jarvis wrote: > I noticed the same warning building with Cygwin, plus a "clobber" > warning in main.c. > > I'm a little obsessive about "no warnings," so my solution was also to > intialize did_free to FALSE, as well as marking the "previous_got_int" > variable as volatile in main.c.
I also like to keep the build warning-free. I had not seen that clobbered warning though. > main.c: In function ‘main_loop’: > main.c:1054:10: warning: variable ‘previous_got_int’ might be clobbered by > ‘longjmp’ or ‘vfork’ [-Wclobbered] > int previous_got_int = FALSE; /* "got_int" was TRUE */ > ^ > > and > > eval.c: In function ‘garbage_collect’: > eval.c:6934:5: warning: ‘did_free’ may be used uninitialized in this function > [-Wmaybe-uninitialized] > return did_free; > ^ > > Patch: Thanks! -- If Microsoft would build a car... ... The airbag system would ask "are you SURE?" before deploying. /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- -- 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/d/optout.
