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
15 lines
379 B
OpenEdge ABL
15 lines
379 B
OpenEdge ABL
%feature("docstring",
|
|
"SBCommandInterpreterRunOptions controls how the RunCommandInterpreter runs the code it is fed.
|
|
|
|
A default SBCommandInterpreterRunOptions object has:
|
|
|
|
* StopOnContinue: false
|
|
* StopOnError: false
|
|
* StopOnCrash: false
|
|
* EchoCommands: true
|
|
* PrintResults: true
|
|
* PrintErrors: true
|
|
* AddToHistory: true
|
|
|
|
") lldb::SBCommandInterpreterRunOptions;
|