public class AccumulationTransfer extends CFTransfer
Subclasses should call the accumulate(Node, TransferResult, String...) accumulate}
method to add a string to the estimate at a particular program point.
| Modifier and Type | Field and Description |
|---|---|
protected AccumulationAnnotatedTypeFactory |
typeFactory
The type factory.
|
analysis, sequentialSemantics| Constructor and Description |
|---|
AccumulationTransfer(CFAnalysis analysis)
Build a new AccumulationTransfer for the given analysis.
|
| Modifier and Type | Method and Description |
|---|---|
void |
accumulate(Node node,
TransferResult<CFValue,CFStore> result,
String... values)
Updates the estimate of how many things
node has accumulated. |
addInformationFromPreconditions, finishValue, finishValue, getValueFromFactory, getValueWithSameAnnotations, initialStore, isNotFullyInitializedReceiver, moreSpecificValue, processCommonAssignment, processConditionalPostconditions, processPostconditions, setFixedInitialStore, splitAssignments, strengthenAnnotationOfEqualTo, usesSequentialSemantics, visitArrayAccess, visitAssignment, visitCase, visitClassName, visitConditionalNot, visitEqualTo, visitFieldAccess, visitInstanceOf, visitLambdaResultExpression, visitLocalVariable, visitMethodInvocation, visitNarrowingConversion, visitNode, visitNotEqual, visitObjectCreation, visitReturn, visitStringConcatenateAssignment, visitStringConversion, visitTernaryExpression, visitThisLiteral, visitVariableDeclaration, visitWideningConversionvisitArrayCreation, visitArrayType, visitAssertionError, visitBitwiseAnd, visitBitwiseComplement, visitBitwiseOr, visitBitwiseXor, visitBooleanLiteral, visitCharacterLiteral, visitClassDeclaration, visitConditionalAnd, visitConditionalOr, visitDoubleLiteral, visitExplicitThisLiteral, visitFloatingDivision, visitFloatingRemainder, visitFloatLiteral, visitGreaterThan, visitGreaterThanOrEqual, visitImplicitThisLiteral, visitIntegerDivision, visitIntegerLiteral, visitIntegerRemainder, visitLeftShift, visitLessThan, visitLessThanOrEqual, visitLongLiteral, visitMarker, visitMemberReference, visitMethodAccess, visitNullChk, visitNullLiteral, visitNumericalAddition, visitNumericalMinus, visitNumericalMultiplication, visitNumericalPlus, visitNumericalSubtraction, visitPackageName, visitParameterizedType, visitPrimitiveType, visitShortLiteral, visitSignedRightShift, visitStringConcatenate, visitStringLiteral, visitSuper, visitSynchronized, visitThrow, visitTypeCast, visitUnsignedRightShift, visitValueLiteralclone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, waitvisitArrayCreation, visitArrayType, visitAssertionError, visitBitwiseAnd, visitBitwiseComplement, visitBitwiseOr, visitBitwiseXor, visitBooleanLiteral, visitCharacterLiteral, visitClassDeclaration, visitConditionalAnd, visitConditionalOr, visitDoubleLiteral, visitExplicitThisLiteral, visitFloatingDivision, visitFloatingRemainder, visitFloatLiteral, visitGreaterThan, visitGreaterThanOrEqual, visitImplicitThisLiteral, visitIntegerDivision, visitIntegerLiteral, visitIntegerRemainder, visitLeftShift, visitLessThan, visitLessThanOrEqual, visitLongLiteral, visitMarker, visitMemberReference, visitMethodAccess, visitNullChk, visitNullLiteral, visitNumericalAddition, visitNumericalMinus, visitNumericalMultiplication, visitNumericalPlus, visitNumericalSubtraction, visitPackageName, visitParameterizedType, visitPrimitiveType, visitShortLiteral, visitSignedRightShift, visitStringConcatenate, visitStringLiteral, visitSuper, visitSynchronized, visitThrow, visitTypeCast, visitUnsignedRightShiftprotected final AccumulationAnnotatedTypeFactory typeFactory
public AccumulationTransfer(CFAnalysis analysis)
analysis - the analysispublic void accumulate(Node node, TransferResult<CFValue,CFStore> result, String... values)
node has accumulated.
If the node is an invocation of a method that returns its receiver, then its receiver's type will also be updated. In a chain of method calls, this process will continue backward as long as each receiver is itself a receiver-returning method invocation.
For example, suppose node is the expression a.b().c(), the new value
(added by the accumulation analysis because of the .c() call) is "foo", and b and c
return their receiver. This method will directly update the estimate of a.b().c() to
include "foo". In addition, the estimates for the expressions a.b() and a
would have their estimates updated to include "foo", because c and b (respectively) return
their receivers. Note that due to what kind of values can be held in the store, this
information is lost outside the method chain. That is, the returns-receiver propagated
information is lost outside the expression in which the returns-receiver method invocations
are nested.
As a concrete example, consider the Called Methods accumulation checker: if build
requires a, b, and c to be called, then foo.a().b().c().build(); will typecheck (they
are in one fluent method chain), but foo.a().b().c(); foo.build(); will not -- the
store does not keep the information that a, b, and c have been called outside the chain.
foo's type will be CalledMethods("a"), because only a() was called
directly on foo. For such code to typecheck, the Called Methods accumulation checker
uses an additional rule: the return type of a receiver-returning method rr() is
CalledMethods("rr"). This rule is implemented directly in the TreeAnnotator subclass defined in the
Called Methods type factory.
node - the node whose estimate should be expandedresult - the transfer result containing the store to be modifiedvalues - the new accumulation values