I still don't see what value you get joining the code to do "Give me one answer with a default value" with the much more complex "enter an interactive session that may have many questions (and you might want to alter the prompt to show where you are in the session currently, etc." I have no objection to adding the latter if there's a good use for it. But given that the IOHandlerConfirm is around 10 lines of code, I see no benefit in complicating it with the code to implement the more complex session.
Jim > On Feb 26, 2015, at 7:08 AM, Siva Chandra <sivachan...@google.com> wrote: > > 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
