Call

A call is the invocation of a function or method.

Related concepts:  FunctionMethodReturn

Closest Wikipedia entry:  Subroutine

Authoritative Definition

Wikipedia does not necessarily offer the best fitting definition of a concept. The exact meaning we attribute to the concept of Call is based on principled authoritative sources such as:

Misconceptions about Call
47 documented Misconceptions

Check Yourself
Misconception
BaseCaseNotNeeded — Java
Recursive computations do not necessarily need a base case
Misconception
BaseCaseSelfRecursive — Java
The base case of a structural recursion consists of a recursive self-call
Misconception
CallNotStaticallyChecked — Java
A method invocation on a reference of a type that does not have that method won't compile
Misconception
CallOnPrimitive — Java
One can invoke a method on primitive values
Misconception
CallRequiresVariable — Java
One needs a variable to invoke a method
Misconception
CallWithoutFrame — Java
A method invocation does not necessarily allocate a stack frame
Misconception
CallerFrameContainsCalleeFormal — Java
Stack frame of caller includes variables for callee's formal parameters
Misconception
CannotChainMemberAccesses — Java
Member accesses cannot be chained together
Misconception
CannotChainMemberToConstructor — Java
Method calls or field accesses cannot be chained to a constructor invocation
Misconception
ChainedMethodsNotCalledFromOutside — Java
Chained methods are all called on the object at the beginning of the chain
Misconception
ConstructorAllocates — Java
The constructor allocates the object
Misconception
ConstructorReturnsObject — Java
Constructors need to return objects
Misconception
ConstructorWithoutNew — Java
One can write the constructor name, without new, to instantiate a class
Misconception
DeferredReturn — Java
A return statement in the middle of a method doesn't return immediately
Misconception
FrameIsClassInstance — Java
A stack frame is the same as an instance of a class
Misconception
NoCallOnStringLiteral — Java
One cannot invoke methods on String literals
Misconception
NoInsideMethodCallInConstructor — Java
It is foirbidden to call other methods on the same object while inside its constructor
Misconception
NoStringToString — Java
One cannot invoke toString() on a String
Misconception
ObjectsMustBeNamed — Java
A variable is needed to instantiate an object
Misconception
OutsideInMethodNesting — Java
Nested method calls are invoked outside in
Misconception
ParenthesesOnlyIfArgument — Java
() are optional for method calls without arguments
Misconception
RecursiveCallSiteNoReturn — Java
Tail-recursive call sites of non-void methods need no return statement
Misconception
ReturnCall — Java
Return statements need () around the return value
Misconception
ReturnUnwindsMultipleFrames — Java
A return statement can unwind multiple call stack frames
Misconception
RightToLeftChaining — Java
Chained accesses are invoked from right to left
Misconception
StackTraceIsCallHistory — Java
A stack trace is the sequence of previously called methods
Misconception
StaticCallPolymorphic — Java
A static method call is dispatched polymorphically at runtime based on the argument types
Misconception
StaticDispatch — Java
The method to be called is determined by the static type
Misconception
SuperAlwaysHasParentheses — Java
To call a method on a superclass, parentheses are needed after the keyword super
Misconception
SuperNotFirstStatement — Java
super() can be called anywhere in the constructor of a subclass
Misconception
CallbackParametersInCaller — JavaScript
Parameters of a callback function may be written as parameters of the caller function
Misconception
FunctionAsValueWithParentheses — JavaScript
To use a function as a value, one needs to have parentheses after its name
Misconception
FunctionsCannotBeImmediatelyInvoked — JavaScript
Functions cannot be called in the expression in which they are defined
Misconception
NoFunctionCallsChaining — JavaScript
It is not allowed to chain function calls
Misconception
NumberOfParametersMatchArguments — JavaScript
Functions must be called with the same number of arguments as defined in their signature
Misconception
CannotChainAttributeAccesses — Python
Attribute accesses cannot be chained together
Misconception
CannotChainAttributeToObjectInstantiation — Python
Method calls, and attribute accesses in general, cannot be chained to a constructor invocation.
Misconception
DeferredReturn — Python
A return statement in the middle of a function doesn't return immediately
Misconception
InitCreates — Python
__init__ must create a new object
Misconception
InitReturnsObject — Python
__init__ needs to return an object
Misconception
ObjectsMustBeNamed — Python
A variable is needed to instantiate an object
Misconception
OutsideInFunctionNesting — Python
Nested function calls are invoked outside in
Misconception
ParenthesesOnlyIfArgument — Python
() are optional for function calls without arguments
Misconception
ReturnCall — Python
Return statements need () around the return value
Misconception
ReturnUnwindsMultipleFrames — Python
A return statement can unwind multiple call stack frames
Misconception
RightToLeftChaining — Python
Chained accesses are invoked from right to left
Misconception
BaseCaseNotNeeded — Scratch
Recursive computations do not necessarily need a base case