com.ibm.wala.accessPath
Interface PathElement

All Known Subinterfaces:

PointerPathElement

All Known Implementing Classes:

FieldPathElement, InstanceFieldPathElement, LocalPathElement, StaticFieldPathElement

public interface PathElement

In principle, we could have used pointer-keys directly as components of the access path. Nevertheless, I prefer having another layer of abstraction that separates the actual implementation details (i.e., PointerKeys) from the representation of the access paths.

Field Summary

static PathElement

EMPTY_ELEMENT special element EMPTY_ELEMENT to avoid explicit null elements

Method Summary

boolean

isAnchor() Is this path element constrained to be the first element in an access path?

Field Detail

EMPTY_ELEMENT

static final PathElement EMPTY_ELEMENT

special element EMPTY_ELEMENT to avoid explicit null elements

Method Detail

isAnchor

boolean isAnchor()

Is this path element constrained to be the first element in an access path?