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
17 lines
607 B
OpenEdge ABL
17 lines
607 B
OpenEdge ABL
%feature("docstring",
|
|
"Represents a libdispatch queue in the process."
|
|
) lldb::SBQueue;
|
|
|
|
%feature("autodoc", "
|
|
Returns an lldb::queue_id_t type unique identifier number for this
|
|
queue that will not be used by any other queue during this process'
|
|
execution. These ID numbers often start at 1 with the first
|
|
system-created queues and increment from there."
|
|
) lldb::SBQueue::GetQueueID;
|
|
|
|
%feature("autodoc", "
|
|
Returns an lldb::QueueKind enumerated value (e.g. eQueueKindUnknown,
|
|
eQueueKindSerial, eQueueKindConcurrent) describing the type of this
|
|
queue."
|
|
) lldb::SBQueue::GetKind;
|