Search results

XCSG assumes that a graph database allows nodes and edges to have tags and attributes. ...wo nodes. Invariably, though not strictly enforced, each edge between two nodes has distinct tags or attributes. Therefore one could also think of this re

...lly represented in data flow only by [[Initialization]] and [[Assignment]] nodes. C/C++ static local variables are also an exception, but they are [[Program ...never <code>5</code>, or any other value. However, if we were to represent DataFlow using a single node for the LocalVariable x, we would see incoming data flo

...tial value of the variable when the method was invoked, and [[Assignment]] nodes represent the values which may be assigned to it later, in a manner resembl The StaticLocalVariable node itself will receive incoming [[DataFlow (Edge)|DataFlow]] edges from its one-time [[Initialization]], from any [[Assignment]] node

A TypeAlias is never the [[TypeOf]] a [[Variable]] or [[DataFlow (Node)|DataFlow]] node, instead the [[TypeOf]] edge points directly to the aliased [[Type]] ...ated with a [[Variable]] defined using a TypeAlias, such as [[Assignment]] nodes representing the static single assignment form of a [[LocalVariable]] (prov

| description = Connects [[DataFlow (Node){{!}}DataFlow nodes]] to one another and to [[Variable]]s, linking the origin of data to locati ...ecified = DataFlow (Node),DataFlow (Node),*,*;Variable,DataFlow (Node),*,*;DataFlow (Node),Variable,*,*

| extends = DataFlow (Edge) ...ts [[Parameter]]s to [[DataFlow (Node){{!}}DataFlow nodes]], and DataFlow nodes to one another, indicating flow of information within that Function.

| extends = DataFlow (Node) ...iableAssignment]] and [[XCSG:InstanceVariableValue|InstanceVariableValue]] nodes, which represent writes and reads of [[XCSG:InstanceVariable| instance vari

...ansferred (such as an [[Assignment]]), or consumed (such as a [[Condition (DataFlow)|Condition]]).

A CallSite is a [[DataFlow (Node)|DataFlow]] node representing the existence of a function call, and the return value ...the CallSite to the called function) are represented as [[CallInputPass]] nodes, connected to the associated CallSite using [[CallInputTo]] edges, and can

...may represent the new value of a variable in continuing [[DataFlow (Edge)|DataFlow]], becoming directly connected by [[LocalDataFlow]] edges to each read of t | extends = DataFlow (Node)

...nodes and an edge: the value used to decide which value will be returned [[DataFlow (Edge)|flows]] into the [[TernaryCondition]], which is connected by a Terna

...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 ...In many cases, a reverse graph of this kind can include a large number of nodes. We can use the Connection View to focus on only the methods we care about