On Wed, Feb 25, 2015 at 6:28 PM, <jing...@apple.com> wrote: > I would rather not conflate simple "confirm" dialogs and something > really interactive like what you are describing. For instance, if you > run into a confirm dialog in a non-interactive environment > (breakpoint command, for example) it makes sense to choose the > default value and continue on. But for an interactive command you > probably want to do something else, either assume that the current > data source (e.g. a "command source" file) is going to provide more > data.
I think the use case required for something like an "explore" command is much simpler. As in, it would always require a real user interacting with it (like with the "breakpoint delete" command). IIRC, "explore" does have a default value (of exiting the session). _______________________________________________ lldb-dev mailing list lldb-dev@cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
