Our commands that end up displaying a ValueObject as part of their workflow use Optio...
authorEnrico Granata <egranata@apple.com>
Tue, 26 Mar 2013 18:04:53 +0000 (18:04 +0000)
committerEnrico Granata <egranata@apple.com>
Tue, 26 Mar 2013 18:04:53 +0000 (18:04 +0000)
commit9fb5ab558b9874ac7065337a9ac274e2d857da16
tree478ff60a853cc0be2f1d56af562e6822cc7c3aec
parentcfed3cf33c1a280669cda1015bc86a5c25d2e583
Our commands that end up displaying a ValueObject as part of their workflow use OptionGroupValueObjectDisplay as their currency for deciding the final representation
ValueObjects themselves use DumpValueObjectOptions as the currency for the same purpose

The code to convert between these two units was replicated (to varying degrees of correctness) in several spots in the code
This checkin provides one and only one (and hopefully correct :-) entry point for this conversion

llvm-svn: 178044
lldb/include/lldb/Interpreter/OptionGroupValueObjectDisplay.h
lldb/source/Commands/CommandObjectExpression.cpp
lldb/source/Commands/CommandObjectFrame.cpp
lldb/source/Commands/CommandObjectMemory.cpp
lldb/source/Commands/CommandObjectTarget.cpp
lldb/source/Core/Debugger.cpp
lldb/source/Interpreter/OptionGroupValueObjectDisplay.cpp