Calledinvoked

Calledinvoked is a term used in software development to describe a two-phase model of function usage, combining the notions of a call site being identified (called) and the actual execution of the function body (invoked). The term is not part of any formal language specification; it appears in some debugging, profiling, and telemetry contexts to distinguish the preparation or resolution of a function from its runtime execution.

In practice, calledinvoked emphasizes that resolving a function reference (for example, resolving a symbol, a delegate, or a reflective method handle) can occur separately from entering the function's code. This distinction is common in languages with reflection, higher-order functions, or asynchronous dispatch, where a symbol may be located or prepared long before the invocation begins.

Instrumentation and logging often use separate timestamps or events for called and invoked phases, enabling analysis of latency between resolution and execution or to diagnose delays due to dynamic loading, caching, or binding. The concept helps in performance tuning and in understanding invocation lifecycles in complex call graphs.

Example: A log shows: processOrder.called at 12:01:02.123, processOrder.invoked at 12:01:02.135, then processOrder.completed at 12:01:02.250, illustrating the two-phase lifecycle.

See also: call, invoke, reflection, dynamic dispatch, profiling, instrumentation.