662548c826
Instead of maintaining separate swig interface files, we can use the API headers directly. They implement the exact same C++ APIs and we can conditionally include the python extensions as needed. To remove the swig extensions from the API headers when building the LLDB framework, we can use the unifdef tool when it is available. Otherwise we just copy them as-is. Differential Revision: https://reviews.llvm.org/D142926
33 lines
1.2 KiB
OpenEdge ABL
33 lines
1.2 KiB
OpenEdge ABL
%feature("docstring",
|
|
"Represents a lexical block. SBFunction contains SBBlock(s)."
|
|
) lldb::SBBlock;
|
|
|
|
%feature("docstring",
|
|
"Is this block contained within an inlined function?"
|
|
) lldb::SBBlock::IsInlined;
|
|
|
|
%feature("docstring", "
|
|
Get the function name if this block represents an inlined function;
|
|
otherwise, return None.") lldb::SBBlock::GetInlinedName;
|
|
|
|
%feature("docstring", "
|
|
Get the call site file if this block represents an inlined function;
|
|
otherwise, return an invalid file spec.") lldb::SBBlock::GetInlinedCallSiteFile;
|
|
|
|
%feature("docstring", "
|
|
Get the call site line if this block represents an inlined function;
|
|
otherwise, return 0.") lldb::SBBlock::GetInlinedCallSiteLine;
|
|
|
|
%feature("docstring", "
|
|
Get the call site column if this block represents an inlined function;
|
|
otherwise, return 0.") lldb::SBBlock::GetInlinedCallSiteColumn;
|
|
|
|
%feature("docstring", "Get the parent block.") lldb::SBBlock::GetParent;
|
|
|
|
%feature("docstring", "Get the inlined block that is or contains this block."
|
|
) lldb::SBBlock::GetContainingInlinedBlock;
|
|
|
|
%feature("docstring", "Get the sibling block for this block.") lldb::SBBlock::GetSibling;
|
|
|
|
%feature("docstring", "Get the first child block.") lldb::SBBlock::GetFirstChild;
|