JDevlieghere wrote: > This looks good. I wonder if we ought to do something a little less ad hoc > about the cases where our command return objects are from HandleCommands, so > they won't necessarily have the result of a single command. In the case where > a UI is parsing these, it might very well need to know that fact. They all > currently have `<>` around the command name, but sadly we don't outlaw `<` as > the initial character of a command, so you can't 100% tell from that.
I can add an enum to indicate whether the command was a user command or something LLDB put together and have two constructors that each do the appropriate thing. `GetCommand` could then return a predefined value for non-user commands. https://github.com/llvm/llvm-project/pull/125132 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
