summaryrefslogtreecommitdiffstats
path: root/lldb/source/Core/ValueObject.cpp
diff options
context:
space:
mode:
authorEnrico Granata <granata.enrico@gmail.com>2012-02-15 02:34:21 +0000
committerEnrico Granata <granata.enrico@gmail.com>2012-02-15 02:34:21 +0000
commit061858ce61c6c3c19a964b572cbcdc8304b287b9 (patch)
tree3ae02b9436e1924547076d088193649922d3bf41 /lldb/source/Core/ValueObject.cpp
parentb228a86fcfd165b06919e43d28b8f1d0713c9802 (diff)
downloadbcm5719-llvm-061858ce61c6c3c19a964b572cbcdc8304b287b9.tar.gz
bcm5719-llvm-061858ce61c6c3c19a964b572cbcdc8304b287b9.zip
<rdar://problem/10062621>
New public API for handling formatters: creating, deleting, modifying categories, and formatters, and managing type/formatter association. This provides SB classes for each of the main object types involved in providing formatter support: SBTypeCategory SBTypeFilter SBTypeFormat SBTypeSummary SBTypeSynthetic plus, an SBTypeNameSpecifier class that is used on the public API layer to abstract the notion that formatters can be applied to plain type-names as well as to regular expressions For naming consistency, this patch also renames a lot of formatters-related classes. Plus, the changes in how flags are handled that started with summaries is now extended to other classes as well. A new enum (lldb::eTypeOption) is meant to support this on the public side. The patch also adds several new calls to the formatter infrastructure that are used to implement by-index accessing and several other design changes required to accommodate the new API layer. An architectural change is introduced in that backing objects for formatters now become writable. On the public API layer, CoW is implemented to prevent unwanted propagation of changes. Lastly, there are some modifications in how the "default" category is constructed and managed in relation to other categories. llvm-svn: 150558
Diffstat (limited to 'lldb/source/Core/ValueObject.cpp')
-rw-r--r--lldb/source/Core/ValueObject.cpp6
1 files changed, 3 insertions, 3 deletions
diff --git a/lldb/source/Core/ValueObject.cpp b/lldb/source/Core/ValueObject.cpp
index 8767b82c87d..9182979fd40 100644
--- a/lldb/source/Core/ValueObject.cpp
+++ b/lldb/source/Core/ValueObject.cpp
@@ -575,7 +575,7 @@ ValueObject::GetSummaryAsCString ()
{
if (m_summary_str.empty())
{
- SummaryFormat *summary_format = GetSummaryFormat().get();
+ TypeSummaryImpl *summary_format = GetSummaryFormat().get();
if (summary_format)
{
@@ -1771,7 +1771,7 @@ ValueObject::GetSyntheticArrayRangeChild (uint32_t from, uint32_t to, bool can_c
// We haven't made a synthetic array member for INDEX yet, so
// lets make one and cache it for any future reference.
- SyntheticArrayView *view = new SyntheticArrayView();
+ SyntheticArrayView *view = new SyntheticArrayView(SyntheticChildren::Flags());
view->AddRange(from,to);
SyntheticChildrenSP view_sp(view);
synthetic_child = new ValueObjectSynthetic(*this, view_sp);
@@ -3075,7 +3075,7 @@ ValueObject::DumpValueObject
std::string value_str;
const char *val_cstr = NULL;
const char *sum_cstr = NULL;
- SummaryFormat* entry = valobj->GetSummaryFormat().get();
+ TypeSummaryImpl* entry = valobj->GetSummaryFormat().get();
if (omit_summary_depth > 0)
entry = NULL;
OpenPOWER on IntegriCloud