*** This commit represents a complete reformatting of the LLDB source code*** to conform to clang-format’s LLVM style. This kind of mass change has*** two obvious implications:Firstly, merging t
*** This commit represents a complete reformatting of the LLDB source code*** to conform to clang-format’s LLVM style. This kind of mass change has*** two obvious implications:Firstly, merging this particular commit into a downstream fork may be a hugeeffort. Alternatively, it may be worth merging all changes up to this commit,performing the same reformatting operation locally, and then discarding themerge for this particular commit. The commands used to accomplish thisreformatting were as follows (with current working directory as the root ofthe repository): find . \( -iname "*.c" -or -iname "*.cpp" -or -iname "*.h" -or -iname "*.mm" \) -exec clang-format -i {} + find . -iname "*.py" -exec autopep8 --in-place --aggressive --aggressive {} + ;The version of clang-format used was 3.9.0, and autopep8 was 1.2.4.Secondly, “blame” style tools will generally point to this commit instead ofa meaningful prior commit. There are alternatives available that will attemptto look through this change and find the appropriate prior commit. YMMV.llvm-svn: 280751
show more ...
Add `six` Python module to lldb/third_party.Six is a python module designed to smooth the process of portingPython 2 code to Python 3. Specifically, six provides a consistentinterface to some of
Add `six` Python module to lldb/third_party.Six is a python module designed to smooth the process of portingPython 2 code to Python 3. Specifically, six provides a consistentinterface to some of the breaking changes between 2 and 3. For example,the syntax for assigning a metaclass differs in Python 2 and 3. Sixaddresses this by providing a single class decorator that will do theright thing depending on which version of Python is being run.There are other examples too, such as dealing with renamed modules,unicode literals, etc.llvm-svn: 250857