public interface IVariable extends IDebugElement, IValueModification
An implementation may choose to re-use or discard variables on iterative thread suspensions. Clients cannot assume that variables 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.
IValue
,
IStackFrame
,
IValueModification
Modifier and Type | Method and Description |
---|---|
String |
getName()
Returns the name of this variable.
|
String |
getReferenceTypeName()
Returns a description of the type of data this variable is
declared to reference.
|
IValue |
getValue()
Returns the value of this variable.
|
boolean |
hasValueChanged()
Returns whether this variable's value has changed since the last suspend event.
|
getDebugTarget, getLaunch, getModelIdentifier
getAdapter
setValue, setValue, supportsValueModification, verifyValue, verifyValue
IValue getValue() throws DebugException
DebugException
- if this method fails. Reasons include:
String getName() throws DebugException
DebugException
- if this method fails. Reasons include:
String getReferenceTypeName() throws DebugException
DebugException
- if this method fails. Reasons include:
boolean hasValueChanged() throws DebugException
Implementations that choose not to implement this function should always
return false
.
DebugException
- if an exception occurs determining if this variable's
value has changed since the last suspend event
Copyright (c) 2000, 2018 Eclipse Contributors and others. All rights reserved.Guidelines for using Eclipse APIs.