summaryrefslogtreecommitdiffstats
path: root/lldb/source/Interpreter/StateVariable.cpp
Commit message (Collapse)AuthorAgeFilesLines
* This is a very large commit that completely re-does the way lldbCaroline Tice2010-09-041-320/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | handles user settable internal variables (the equivalent of set/show variables in gdb). In addition to the basic infrastructure (most of which is defined in UserSettingsController.{h,cpp}, there are examples of two classes that have been set up to contain user settable variables (the Debugger and Process classes). The 'settings' command has been modified to be a command-subcommand structure, and the 'set', 'show' and 'append' commands have been moved into this sub-commabnd structure. The old StateVariable class has been completely replaced by this, and the state variable dictionary has been removed from the Command Interpreter. Places that formerly accessed the state variable mechanism have been modified to access the variables in this new structure instead (checking the term-width; getting/checking the prompt; etc.) Variables are attached to classes; there are two basic "flavors" of variables that can be set: "global" variables (static/class-wide), and "instance" variables (one per instance of the class). The whole thing has been set up so that any global or instance variable can be set at any time (e.g. on start up, in your .lldbinit file), whether or not any instances actually exist (there's a whole pending and default values mechanism to help deal with that). llvm-svn: 113041
* A few more misc warning fixes.Eli Friedman2010-07-091-1/+1
| | | | llvm-svn: 108030
* Initial checkin of lldb code from internal Apple repo.Chris Lattner2010-06-081-0/+320
llvm-svn: 105619
OpenPOWER on IntegriCloud