OpenGrok
Home
Sort by relevance
Sort by last modified time
Full Search
Definition
Symbol
File Path
History
|
|
Help
Searched
defs:ValueObject
(Results
1 - 4
of
4
) sorted by null
/art/compiler/utils/
allocation.h
37
class
ValueObject
{
/frameworks/opt/telephony/src/java/com/android/internal/telephony/cat/
CommandDetails.java
22
abstract class
ValueObject
{
30
class CommandDetails extends
ValueObject
implements Parcelable {
93
class DeviceIdentities extends
ValueObject
{
104
class IconId extends
ValueObject
{
115
class ItemsIconId extends
ValueObject
{
/external/lldb/source/Core/
ValueObject.cpp
1
//===--
ValueObject
.cpp -----------------------------------------*- C++ -*-===//
12
#include "lldb/Core/
ValueObject
.h"
62
//
ValueObject
constructor
64
ValueObject
::
ValueObject
(
ValueObject
&parent) :
107
//
ValueObject
constructor
109
ValueObject
::
ValueObject
(ExecutionContextScope *exe_scope,
156
ValueObject
::~ValueObject (
[
all
...]
/external/lldb/include/lldb/Core/
ValueObject.h
1
//===--
ValueObject
.h -------------------------------------------*- C++ -*-===//
36
///
ValueObject
:
39
/// that is evaluated in some particular scope. The
ValueObject
also has the capibility of being the "child" of
41
/// If a
ValueObject
is a root variable object - having no parent - then it must be constructed with respect to some
43
/// The
ValueObject
will update itself if necessary before fetching its value, summary, object description, etc.
46
/// A brief note on life cycle management for ValueObjects. This is a little tricky because a
ValueObject
can contain
54
/// The
ValueObject
mostly handle this automatically, if a value object is made with a Parent
ValueObject
, then it adds
58
/// or pointers to them. So all the "Root level"
ValueObject
derived constructors should be private, and
61
/// However, if you are making an derived
ValueObject
that will be contained in a parent value object, you should jus
[
all
...]
Completed in 218 milliseconds