Search results

XCSG assumes that a graph database allows nodes and edges to have tags and attributes. Nodes and edges in XCSG can be of one or more kinds. The word "kind" is used instead of "

Static local variables are typically treated in [[DataFlow (Edge)|DataFlow]] in a manner similar to [[Parameter]]s: the StaticLocalVariable node itsel ...h. The initialization is typically [[LocalDataFlow]], the cross-invocation edges are [[InterproceduralDataFlow]].

LocalDataFlow edges represent the movement of data within a particular [[Function]]. The existe | extends = DataFlow (Edge)

...ce of a function call, and the return value of that call. Their [[TypeOf]] edges point to the return type of the [[Function]] called; for void functions, th ...lInputTo]] edges, and can be accessed from the CallSite by following those edges in reverse.

Data is considered to [[DataFlow (edge)|flow]] through an Operator, even though an Operator may modify both ...assSite]]s for [[Method]] calls, and simply by [[InterproceduralDataFlow]] edges for field accesses).

...taFlow (Edge)|DataFlow]], becoming directly connected by [[LocalDataFlow]] edges to each read of the corresponding variable that receives the assigned value ...eads of the same Variable receiving their incoming InterproceduralDataFlow edges from the Variable itself.

...ions that the [[Function]] can return to using [[InterproceduralDataFlow]] edges. | extends = DataFlow (Node)

...of code you wish to follow, and choose the appropriate Smart View script- dataflow for fields, and calls for methods. For more information on investigating t ...graph shows that this method, <code>configureOrientation</code>, has read edges to three screen orientations, "portrait," "landscape," and "unspecified."

* Frontier edges now appear in pinned graphs. * Default Smart View scripts no longer show edge labels for Call and Dataflow edges.