[ScriptInterpreter] Pass the debugger instead of the command interpreter
As discussed in D61090, there's no good reason for the script interpreter to depend on the command interpreter. When looking at the code, it becomes clear that we mostly use the command interpreter as a way to access the debugger. Hence, it makes more sense to just pass that to the script interpreter directly. This is part 1 out of 2. I have another patch in the pipeline that changes the ownership of the script interpreter to the debugger as well, but I didn't get around to finish that today. Differential revision: https://reviews.llvm.org/D61172 llvm-svn: 359330
This commit is contained in:
@@ -29,7 +29,7 @@ class ScriptInterpreterPythonImpl : public ScriptInterpreterPython {
|
||||
public:
|
||||
friend class IOHandlerPythonInterpreter;
|
||||
|
||||
ScriptInterpreterPythonImpl(CommandInterpreter &interpreter);
|
||||
ScriptInterpreterPythonImpl(Debugger &debugger);
|
||||
|
||||
~ScriptInterpreterPythonImpl() override;
|
||||
|
||||
@@ -273,8 +273,7 @@ public:
|
||||
void IOHandlerInputComplete(IOHandler &io_handler,
|
||||
std::string &data) override;
|
||||
|
||||
static lldb::ScriptInterpreterSP
|
||||
CreateInstance(CommandInterpreter &interpreter);
|
||||
static lldb::ScriptInterpreterSP CreateInstance(Debugger &debugger);
|
||||
|
||||
// PluginInterface protocol
|
||||
lldb_private::ConstString GetPluginName() override;
|
||||
|
||||
Reference in New Issue
Block a user