medismailben wrote: > The reason behind this change is to have a top-level command that will cover > scripting related subcommands.
>From @jimingham reply: Which other scripting subcommands do you envision, besides the [template](https://github.com/llvm/llvm-project/pull/97273) subcommand? One that I want, powered by facilities we can add to the template, is that a class that implements a breakpoint callback should have a registry method (that's the part we can probably generate with the template instantiation) that adds callback class and help info to lldb. Then you would do: ``` (lldb) scripting instances list Breakpoint Callbacks: my_module.MyBreakpointCallback: This does something really cool, if you pass the right value for the key "even_cooler", it does something even cooler. ``` And similar for all the other affordances. We could do this by having `breakpoint callback implementation list` but I think having them listed here would make all the different affordances we have more discoverable. BTW, I'm not proposing `instances` as the name, but I couldn't think of a better one off the top of my head. Maybe `scripting callback list`? It might also be handy to have: (lldb) scripting modules list -l Python MyFirstModule : /Users/Me/MyPythonModules/my_first_script.py etc... Which would list all the Python modules that we've loaded with "command script import" and where they came from. https://github.com/llvm/llvm-project/pull/97263 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
