aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Plugins/ScriptInterpreter/Python/lldb-python.h
diff options
context:
space:
mode:
authorAlex Langford <alangford@apple.com>2023-06-27 15:51:27 -0700
committerAlex Langford <alangford@apple.com>2023-07-03 11:17:48 -0700
commitebec53e2d7c79b519aec455d048f5f03fc2e7abe (patch)
tree0d579b7d5ec0d4977468fd222984bd21125bcd81 /lldb/source/Plugins/ScriptInterpreter/Python/lldb-python.h
parente3921b8bff693649602760a6221cd1150420a287 (diff)
downloadllvm-ebec53e2d7c79b519aec455d048f5f03fc2e7abe.zip
llvm-ebec53e2d7c79b519aec455d048f5f03fc2e7abe.tar.gz
llvm-ebec53e2d7c79b519aec455d048f5f03fc2e7abe.tar.bz2
[lldb] Introduce a macro to mark methods as unsupported with no replacement
We already have LLDB_DEPRECATED which is used to mark methods as deprecated with a message and an alternative to use instead. This is expresses an intent of "We recognize this functionality is useful but there are some pitfalls with the interface we have exposed." In other cases, there are no "alternative" methods to use and the code should be refactored to avoid using a method entirely. For example, `SBValue::Cast` should be avoided in favor of using the expression evaluator to perform a cast. There isn't a mechanical solution, the recommendation is to instead refactor your code. This commit renames the existing `LLDB_DEPRECATED` to `LLDB_DEPRECATED_FIXME`, and adds a `LLDB_DEPRECATED` macro to cover the second scenario. Differential Revision: https://reviews.llvm.org/D153928
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/lldb-python.h')
0 files changed, 0 insertions, 0 deletions