From c1247f5596af74a9f9cc59942cc8b6cf67d27529 Mon Sep 17 00:00:00 2001 From: Enrico Granata Date: Thu, 6 Nov 2014 21:23:20 +0000 Subject: Introduce the notion of "type summary options" as flags that can be passed down to individual summary formatters to alter their behavior in a formatter-dependent way Two flags are introduced: - preferred display language (as in, ObjC vs. C++) - summary capping (as in, should a limit be put to the amount of data retrieved) The meaning - if any - of these options is for individual formatters to establish The topic of a subsequent commit will be to actually wire these through to individual data formatters llvm-svn: 221482 --- lldb/source/Core/ValueObjectConstResult.cpp | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'lldb/source/Core/ValueObjectConstResult.cpp') diff --git a/lldb/source/Core/ValueObjectConstResult.cpp b/lldb/source/Core/ValueObjectConstResult.cpp index 64ee3304e58..b88830f1934 100644 --- a/lldb/source/Core/ValueObjectConstResult.cpp +++ b/lldb/source/Core/ValueObjectConstResult.cpp @@ -359,3 +359,8 @@ ValueObjectConstResult::GetDynamicValue (lldb::DynamicValueType use_dynamic) return ValueObjectSP(); } +lldb::LanguageType +ValueObjectConstResult::GetPreferredDisplayLanguage () +{ + return lldb::eLanguageTypeUnknown; +} -- cgit v1.2.3