Enrico Granata c3387333ce <rdar://problem/11742979> ... SWIG is smart enough to recognize that C++ operators == and != mean __eq__ and __ne__ in Python and do the appropriate translation But it is not smart enough to recognize that mySBObject == None should return False instead of erroring out The %pythoncode blocks are meant to provide those extra smarts (and they play some SWIG&Python magic to find the right function to call behind the scenes with no risk of typos :-) Lastly, SBBreakpoint provides an == but never provided a != operator - common courtesy is to provide both llvm-svn: 180987		2013-05-03 01:29:27 +00:00
..
interface	<rdar://problem/11742979>	2013-05-03 01:29:27 +00:00
build-swig-Python.sh	Makefile patches from Charles Davis and Daniel Malea (+ one or two tweaks).	2012-11-01 18:55:16 +00:00
edit-swig-python-wrapper-file.py	Fix remaining Python issues leftover from my previous patch.	2011-06-01 02:33:12 +00:00
finish-swig-Python-LLDB.sh	Rename unwind_diagnose.py to diagnose_unwind.py. Change	2013-04-30 03:03:06 +00:00
modify-python-lldb.py	Make sure that the lldb globals:	2012-12-10 19:18:23 +00:00
python-extensions.swig	<rdar://problem/11742979>	2013-05-03 01:29:27 +00:00
python-typemaps.swig	<rdar://problem/13499317>	2013-05-02 17:29:04 +00:00
python-wrapper.swig	Since we use C++11, we should switch over to using std::unique_ptr when C++11 is being used. To do this, we follow what we have done for shared pointers and we define a STD_UNIQUE_PTR macro that can be used and it will "do the right thing". Due to some API differences in std::unique_ptr and due to the fact that we need to be able to compile without C++11, we can't use move semantics so some code needed to change so that it can compile with either C++.	2013-04-18 18:10:51 +00:00