public interface IValue extends IDebugElement
An implementation may choose to re-use or discard values on iterative thread suspensions. Clients cannot assume that values are identical or equal across iterative thread suspensions and must check for equality on iterative suspensions if they wish to re-use the objects.
An implementation that preserves equality across iterative suspensions may display more desirable behavior in some clients. For example, if variables are preserved while stepping, a UI client would be able to update the UI incrementally, rather than collapse and redraw the entire list or tree.
Clients may implement this interface.
IVariable
Modifier and Type | Method and Description |
---|---|
String |
getReferenceTypeName()
Returns a description of the type of data this value contains
or references.
|
String |
getValueString()
Returns this value as a
String . |
IVariable[] |
getVariables()
Returns the visible variables in this value.
|
boolean |
hasVariables()
Returns whether this value currently contains any visible variables.
|
boolean |
isAllocated()
Returns whether this value is currently allocated.
|
getDebugTarget, getLaunch, getModelIdentifier
getAdapter
String getReferenceTypeName() throws DebugException
DebugException
- if this method fails. Reasons include:
String getValueString() throws DebugException
String
.DebugException
- if this method fails. Reasons include:
boolean isAllocated() throws DebugException
For example, if this value represents
an object that has been garbage collected, false
is returned.
DebugException
- if this method fails. Reasons include:
IVariable[] getVariables() throws DebugException
DebugException
- if this method fails. Reasons include:
boolean hasVariables() throws DebugException
DebugException
- if this method fails. Reasons include:
Copyright (c) 2000, 2015 Eclipse Contributors and others. All rights reserved.Guidelines for using Eclipse APIs.