[email protected], on 05/19/13 at 01:11:47 -0400, wrote:
> Scrolling up through the terminal output reveals some warnings
> that are potentially useful:
>
> -pipe -DMACOS_X_UNIX -no-cpp-precomp -g -O -U_FORTIFY_SOURCE
> -D_FORTIFY_SOURCE=1
> -I/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7
> -DPYTHON_HOME=\"/Library/Frameworks/Python.framework/Versions/2.7\" -o
> objects/if_python.o if_python.c
> In file included from if_python.c:660:
> if_py_both.h: In function ‘OptionsDestructor’:
> if_py_both.h:1415: warning: suggest explicit braces to avoid ambiguous ‘else’
> if_py_both.h: In function ‘OptionsTraverse’:
> if_py_both.h:1423: warning: implicit declaration of function ‘Py_VISIT’
> if_py_both.h: In function ‘OptionsClear’:
> if_py_both.h:1430: warning: implicit declaration of function ‘Py_CLEAR’
> if_py_both.h: In function ‘WinListDestructor’:
> if_py_both.h:2112: warning: suggest explicit braces to avoid ambiguous ‘else’
Since the choking was on the functions Py_{VISIT,CLEAR}, and the
warnings reflected the lines 1423 and 1430 in if_py_both.h, I decided
to do an 'hg blame' on that file. The result is that the lines in
question were most recently touched by patch 7.3.965 (the python
garbage collection patch).
I cannot bisect to test commits prior to that, because updating to
such a commit (e.g., 7.3.930) deletes all the MacVim parts and leaves
the working directory as plain BramVim. As I noted earlier, BramVim
doesn't have the problem in question.
-gmn
--
--
You received this message from the "vim_mac" 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_mac" 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.
