Method

A method is a function that is a member of a class and may operate on an object.

Related concepts:  FunctionMemberClassObject

Closest Wikipedia entry:  Method (computer programming)

Authoritative Definition

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

Misconceptions about Method
46 documented Misconceptions

Check Yourself
Misconception
AddMemberAtRuntime — Java
Set of class members can change at runtime
Misconception
ArrayHasLengthMethod — Java
To get the length of an array, one needs to call its length method
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
ConcreteClassMustOverride — Java
A concrete class needs to implement all abstract methods and override all concrete methods declared in its abstract superclasses
Misconception
ConcreteClassOnlyImplementClassAbstract — Java
A concrete class only needs to implement those abstract methods it inherits from abstract superclasses
Misconception
ConcreteClassOnlyImplementDirectAbstract — Java
A concrete class only needs to implement abstract methods declared in its direct supertypes
Misconception
ConcreteClassOnlyImplementInterfaceAbstract — Java
A concrete class only needs to implement those abstract methods it inherits from interfaces
Misconception
DeferredReturn — Java
A return statement in the middle of a method doesn't return immediately
Misconception
EqualsComparesReferences — Java
o.equals(p) compares the references stored in the variables o and p
Misconception
ImmutableRequiresFinalParameters — Java
Immutable classes need final constructor/method parameters
Misconception
ImplicitInterfaceImplementation — Java
Java implicitly produces implementations of any methods a class inherits from the interfaces it implements
Misconception
MethodAsField — Java
Each object contains its own special fields for all of its methods
Misconception
MethodWithoutReturnType — Java
A method declaration does not need to include a return type
Misconception
MethodsWithoutClass — Java
Methods can be defined outside 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
NoMethodInheritance — Java
Subclasses inherit fields but not methods
Misconception
NoStringToString — Java
One cannot invoke toString() on a String
Misconception
OutsideInMethodNesting — Java
Nested method calls are invoked outside in
Misconception
ParenthesesOnlyIfArgument — Java
() are optional for method calls without arguments
Misconception
PrivateAccessibleInSubclass — Java
Private members of a superclass are accessible from a subclass
Misconception
RecursiveMethodImpliesRecursiveType — Java
A class with a recursive method represents part of a recursive data structure
Misconception
RecursiveMethodNeedsIfElse — Java
A recursive method needs to contain an if-else statement
Misconception
ReturnCall — Java
Return statements need () around the return value
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
StringLengthField — Java
One can know the length of a String object by accessing its length field
Misconception
ThisExistsInStaticMethod — Java
this is a local variable, also in static methods
Misconception
ToStringPrints — Java
Invoking toString() prints something
Misconception
UseOfSelfTypeImpliesRecursiveType — Java
If a class has a method that has a local variable, parameter, or return value with the class as its type, the class is a recursive type
Misconception
VoidMethodNotRecursive — Java
A method with void return type can't be recursive
Misconception
VoidMethodReturnsValue — Java
A method with void return type can return a value
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
RightToLeftChaining — Python
Chained accesses are invoked from right to left