View source for Call an object method

[[Category:Object oriented]]
[[Category:Encyclopedia]]
{{task|Basic language learning}}

In [[object-oriented programming]] a method is a function associated with a particular class or object. In most forms of object oriented implementations methods can be static, associated with the class itself; or instance, associated with an instance of a class.

Show how to call a static or class method, and an instance method of a class.
=={{header|ActionScript}}==
<syntaxhighlight lang="actionscript">// Static
MyClass.method(someParameter);

// Instance
myInstance.method(someParameter);</syntaxhighlight>
=={{header|Ada}}==
Ada is a language based on strict typing. Nevertheless, since Ada 95 (the first major revision of the language), Ada also includes the concepts of a class. Types may be tagged, and for each tagged type T there is an associated type T'Class. If you define a method as "procedure Primitive(Self: T)", the actual parameter Self must be of type T, exactly, and the method Primitive will be called, well, statically. This may be surprising, if you are used to other object-oriented languages.

If you define a method as "prodedure Dynamic(Self: T'Class)", the actual parameter can be either T or any of its descendents. Now, if you call Self.Primitive within the procedure Dynamic, it will be dispatching, i.e., it will call the primitive function matching the type of Self (i.e., either T or any of its subtype). This is what you would expect in many other object-oriented languages. 

Finally, a static method can be defined as a subprogram within the same package that holds the object type and the other methods. 

Specify the class My_Class, with one primitive subprogram, one dynamic subprogram and a static subprogram:
<syntaxhighlight lang="ada">   package My_Class is
      type Object is tagged private;
      procedure Primitive(Self: Object); -- primitive subprogram
      procedure Dynamic(Self: Object'Class);
      procedure Static;
   private
      type Object is tagged null record;
   end My_Class;</syntaxhighlight>

Implement the package:
<syntaxhighlight lang="ada">   package body My_Class is
      procedure Primitive(Self: Object) is
      begin
	 Put_Line("Hello World!");
      end Primitive;

      procedure Dynamic(Self: Object'Class) is
      begin
	 Put("Hi there! ... ");
	 Self.Primitive; -- dispatching call: calls different subprograms,
                         -- depending on the type of Self  
      end Dynamic;

      procedure Static is
      begin
	 Put_Line("Greetings");
      end Static;
   end My_Class;</syntaxhighlight>

Specify and implement a subclass of My_Class:
<syntaxhighlight lang="ada">   package Other_Class is
      type Object is new My_Class.Object with null record;
      overriding procedure Primitive(Self: Object);
   end Other_Class;
   
   package body Other_Class is
      procedure Primitive(Self: Object) is
      begin
	 Put_Line("Hello Universe!");
      end Primitive;
   end Other_Class;</syntaxhighlight>

The main program, making the dynamic and static calls:

<syntaxhighlight lang="ada">with Ada.Text_IO; use Ada.Text_IO;

procedure Call_Method is
   
   package My_Class is ... -- see above
   package body My_Class is ... -- see above
            
   package Other_Class is ... -- see above
   package body Other_Class is ... -- see above
   
   Ob1: My_Class.Object; -- our "root" type
   Ob2: Other_Class.Object; -- a type derived from the "root" type
      
begin
   My_Class.Static;
   Ob1.Primitive; 
   Ob2.Primitive; 
   Ob1.Dynamic; 
   Ob2.Dynamic;
end Call_Method;</syntaxhighlight>

{{out}}

<pre>Greetings
Hello World!
Hello Universe!
Hi there! ... Hello World!
Hi there! ... Hello Universe!</pre>
=={{header|ALGOL 68}}==
Algol 68 doesn't do OO as such, but it has structures, the members of which can be procedures. This allows OO features to be implemented, though without syntactic sugar, "this" pointers must be passed explicitly. In Algol 68, <code>a OF b</code> is used where most other languages would use <code>b.a</code>.
<br>
This means that a call to an instance method called "print" say of a class instance "a" in Algol 68 would be written <code>( print OF a )( a )</code>, - note the explicit "this" parameter - whereas <code>a.print</code> would be used in most other languages.
<br>
Class methods could be members of the structure (as here) without a "this" parameter, or could be procedures defined outside the structure.
<br>
In this example, the instance and class methods return VOID, but this is not necessary, any return type could be used.
<syntaxhighlight lang="algol68">
BEGIN # demonstrate a possible method of simulating class & instance methods  #
    # declare a "class"                                                       #
    MODE ANIMAL = STRUCT( STRING                 species
                        , PROC( REF ANIMAL )VOID print    # instance method   #
                        , PROC VOID              cm       # class method      #
                        );
    # constructor                                                             #
    PROC new animal = ( STRING species )REF REF ANIMAL:
         BEGIN
             HEAP ANIMAL     newv := ANIMAL( species
                                           , ( REF ANIMAL this )VOID:
                                               print( ( "[animal instance[", species OF this, "]]" ) )
                                           , VOID: print( ( "[animal class method called]" ) )
                                           );
             HEAP REF ANIMAL newa := newv;
             newa
         END # new animal # ;

    REF ANIMAL a
           := new animal( "PANTHERA TIGRIS" ); # create an instance of ANIMAL #
    cm OF a;                                   # call the class method        #
    ( print OF a )( a )                        # call the instance method     #
END
</syntaxhighlight>
{{out}}
<pre>
[animal class method called][animal instance[PANTHERA TIGRIS]]
</pre>

=={{header|Apex}}==
<syntaxhighlight lang="java">// Static
MyClass.method(someParameter);

// Instance
myInstance.method(someParameter);</syntaxhighlight>

=={{header|AutoHotkey}}==
{{works with|AutoHotkey_L}}
(AutoHotkey Basic does not have classes)
<syntaxhighlight lang="ahk">class myClass
{
	Method(someParameter){
		MsgBox % SomeParameter
	}
}

myClass.method("hi")
myInstance := new myClass
myInstance.Method("bye")</syntaxhighlight>
=={{header|Bracmat}}==
Bracmat has no classes. Rather, objects can be created as copies of other objects. In the example below, the variable <code>MyObject</code> has a copy of variable <code>MyClass</code> as value. Notice the extra level of reference in <code>(MyObject..Method)$argument</code>, comparable to <code>MyObject->Method(argument)</code> in C. Rather than being the object itself, <code>MyObject</code> points to an object and can be aliased by assigning to another variable.

Inside an object, the object is represented by <code>its</code>, comparable to <code>this</code> in other languages.
<syntaxhighlight lang="bracmat">( ( myClass
  =   (name=aClass)
      ( Method
      = .out$(str$("Output from " !(its.name) ": " !arg))
      )
      (new=.!arg:?(its.name))
  )
& (myClass.Method)$"Example of calling a 'class' method"
& new$(myClass,object1):?MyObject
& (MyObject..Method)$"Example of calling an instance method"
& !MyObject:?Alias
& (Alias..Method)$"Example of calling an instance method from an alias"
);</syntaxhighlight>
Output:
<pre>Output from aClass: Example of calling a 'class' method
Output from object1: Example of calling an instance method
Output from object1: Example of calling an instance method from an alias</pre>


=={{header|C}}==
C has structures and it also has function pointers, which allows C structures to be associated with any function with the same signature as the pointer. Thus, C structures can also have object methods.
<syntaxhighlight lang="c">
#include<stdlib.h>
#include<stdio.h>

typedef struct{
        int x;
        int (*funcPtr)(int);
}functionPair;

int factorial(int num){
        if(num==0||num==1)
                return 1;
        else
                return num*factorial(num-1);
}

int main(int argc,char** argv)
{
        functionPair response;

        if(argc!=2)
                return printf("Usage : %s <non negative integer>",argv[0]);
        else{
                response = (functionPair){.x = atoi(argv[1]),.funcPtr=&factorial};
                printf("\nFactorial of %d is %d\n",response.x,response.funcPtr(response.x));
        }
        return 0;
}
</syntaxhighlight>
And yes, it works :
<pre>
$ ./a.out 10

Factorial of 10 is 3628800
</pre>
=={{header|C++}}==
<syntaxhighlight lang="cpp">// Static
MyClass::method(someParameter);

// Instance
myInstance.method(someParameter);

// Pointer
MyPointer->method(someParameter);
</syntaxhighlight>
=={{header|C_sharp|C#}}==
<syntaxhighlight lang="csharp">// Static
MyClass.Method(someParameter);
 
// Instance
myInstance.Method(someParameter);</syntaxhighlight>
=={{header|ChucK}}==
<syntaxhighlight lang="c">
MyClass myClassObject;
myClassObject.myFunction(some parameter);
</syntaxhighlight>
=={{header|Clojure}}==
<syntaxhighlight lang="clojure">(Long/toHexString 15) ; use forward slash for static methods
(System/currentTimeMillis)

(.equals 1 2)    ; use dot operator to call instance methods
(. 1 (equals 2)) ; alternative style</syntaxhighlight>
=={{header|COBOL}}==
{{Works with|COBOL 2002}}
There are two ways to invoke a method: the <code>INVOKE</code> statement and inline method invocation.
<syntaxhighlight lang="cobolfree">*> INVOKE statements.
INVOKE my-class "some-method"          *> Factory object
    USING BY REFERENCE some-parameter
    RETURNING foo
INVOKE my-instance "another-method"    *> Instance object
    USING BY REFERENCE some-parameter
    RETURNING foo

*> Inline method invocation.
MOVE my-class::"some-method"(some-parameter) TO foo       *> Factory object
MOVE my-instance::"another-method"(some-parameter) TO foo *> Instance object</syntaxhighlight>

To call factory methods of objects of an unknown type (such as when you may have a subclass of the class wanted), it is necessary to get a reference to the class's factory object by calling the <code>"FactoryObject"</code> method.
<syntaxhighlight lang="cobolfree">INVOKE some-instance "FactoryObject" RETURNING foo-factory
*> foo-factory can be treated like a normal object reference.
INVOKE foo-factory "someMethod"</syntaxhighlight>

=={{header|CoffeeScript}}==
While CoffeeScript does provide a useful class abstraction around its prototype-based inheritance, there aren't any actual classes.
<syntaxhighlight lang="coffeescript">class Foo
    @staticMethod: -> 'Bar'

    instanceMethod: -> 'Baz'

foo = new Foo

foo.instanceMethod() #=> 'Baz'
Foo.staticMethod() #=> 'Bar'</syntaxhighlight>


=={{header|Common Lisp}}==
In Common Lisp, classmethods are methods that apply to classes, rather than classes that contain methods.
<syntaxhighlight lang="lisp">(defclass my-class ()
  ((x
    :accessor get-x  ;; getter function
    :initarg :x      ;; arg name 
    :initform 0)))   ;; initial value

;; declaring a public class method
(defmethod square-x ((class-instance my-class))
  (* (get-x class-instance) (get-x class-instance)))

;; create an instance of my-class
(defvar *instance*
  (make-instance 'my-class :x 10))

(format t "Value of x: ~a~%" (get-x *instance*))

(format t "Value of x^2: ~a~%" (square-x *instance*))
</syntaxhighlight>
Output (CLISP v2.49):
<pre>$ clisp object.cl
Value of x: 10
Value of x^2: 100
</pre>


=={{header|D}}==
<syntaxhighlight lang="d">struct Cat {
    static int staticMethod() {
        return 2;
    }

    string dynamicMethod() { // Never virtual.
        return "Mew!";
    }
}

class Dog {
    static int staticMethod() {
        return 5;
    }

    string dynamicMethod() { // Virtual method.
        return "Woof!";
    }
}

void main() {
    // Static methods calls:
    assert(Cat.staticMethod() == 2);
    assert(Dog.staticMethod() == 5);

    Cat c; // This is a value on the stack.
    Dog d; // This is just a reference, set to null.

    // Other static method calls, discouraged:
    assert(c.staticMethod() == 2);
    assert(d.staticMethod() == 5);

    // Instance method calls:
    assert(c.dynamicMethod() == "Mew!");
    d = new Dog;
    assert(d.dynamicMethod() == "Woof!");
}</syntaxhighlight>

=={{header|Delphi}}==
{{works with|Delphi|6.0}}
{{libheader|SysUtils,StdCtrls}}
This example shows the creation of a simple integer stack object. The object contains "Push" and "Pop" static methods. 

<syntaxhighlight lang="Delphi">

{Simple stack interface}

type TSimpleStack = class(TObject)
 private
  FStack: array of integer;
 protected
 public
  procedure Push(I: integer);
  function Pop(var I: integer): boolean;
  constructor Create;
 end;


{ TSimpleStack implementation }

constructor TSimpleStack.Create;
{Initialize stack by setting size to zero}
begin
SetLength(FStack,0);
end;

function TSimpleStack.Pop(var I: integer): boolean;
{Pop top item off stack into "I" returns False if stack empty}
begin
Result:=Length(FStack)>=1;
if Result then
	begin
	{Get item from top of stack}
	I:=FStack[High(FStack)];
	{Delete the top item}
	SetLength(FStack,Length(FStack)-1);
	end;
end;

procedure TSimpleStack.Push(I: integer);
{Push item on stack by adding to end of array}
begin
{Increase stack size by one}
SetLength(FStack,Length(FStack)+1);
{Insert item}
FStack[High(FStack)]:=I;
end;


procedure ShowStaticMethodCall(Memo: TMemo);
var Stack: TSimpleStack;	{Declare stack object}
var I: integer;
begin
{Instanciate stack object}
Stack:=TSimpleStack.Create;
{Push items on stack by calling static method "Push"}
for I:=1 to 10 do Stack.Push(I);
{Call static method "Pop" to retrieve and display stack items}
while Stack.Pop(I) do
	begin
	Memo.Lines.Add(IntToStr(I));
	end;
{release stack memory and delete object}
Stack.Free;
end;



</syntaxhighlight>
{{out}}
<pre>
10
9
8
7
6
5
4
3
2
1
Elapsed Time: 10.571 ms.
</pre>



=={{header|Dragon}}==
Making an object of class and then calling it.
<syntaxhighlight lang="dragon">r = new run()
r.val()</syntaxhighlight>
=={{header|Dyalect}}==

Dyalect supports both instance and static methods. Instance methods have a special <code>this</code> reference that returns an instance. Static method are always invoked through the type name.

<syntaxhighlight lang="dyalect">//Static method on a built-in type Integer
static func Integer.Div(x, y) {
    x / y
}
 
//Instance method
func Integer.Div(n) {
    this / n
}
 
print(Integer.Div(12, 3))
print(12.Div(3))</syntaxhighlight>

{{out}}

<pre>4
4</pre>
=={{header|E}}==
{{improve|E|Add runnable example.}}
A method call in E has the syntax <code><var>recipient</var>.<var>verb</var>(<var>arg1</var>, <var>arg2</var>, <var>...</var>)</code>, where <var>recipient</var> is an expression, <var>verb</var> is an identifier (or a string literal preceded by <code>::</code>), and <var>argN</var> are expressions.

<syntaxhighlight lang="e">someObject.someMethod(someParameter)</syntaxhighlight>

In E, there are no distinguished "static methods". Instead, it is idiomatic to place methods on the maker of the object. This is very similar to methods on constructors in JavaScript, or class methods in Objective-C.

=={{header|Ecstasy}}==
Calling a method or function in Ecstasy follows roughly the same conventions as in Java and C#, but in order to prevent certain types of bugs, Ecstasy explicitly disallows calling a function <i>as if it were a method</i>. 
<syntaxhighlight lang="java">
module CallMethod {
    /**
     * This is a class with a method and a function.
     */
    const Example(String text) {
        @Override
        String toString() {                             // <-- this is a method
            return $"This is an example with text={text}";
        }

        static Int oneMoreThan(Int n) {                 // <-- this is a function
            return n+1;
        }
    }

    void run() {
        @Inject Console console;

        Example example      = new Example("hello!");
        String  methodResult = example.toString();      // <-- call a method
        console.print($"Result from calling a method: {methodResult.quoted()}");

     // Int funcResult = example.oneMoreThan(12);      // <-- compiler error
        Int funcResult = Example.oneMoreThan(12);      // <-- call a function
        console.print($"Results from calling a function: {funcResult}");

        // methods and functions are also objects that can be manipulated;
        // note that "function String()" === "Function<<>, <String>>"
        Method<Example, <>, <String>> method = Example.toString;
        function String() func   = method.bindTarget(example);
        console.print($"Calling a bound method: {func().quoted()}");

        // by default, a method with target T converts to a function taking a T;
        // Ecstasy refers to this as "Bjarning" (because C++ takes "this" as a param)
        val func2 = Example.toString;                   // <-- type: function String()
        console.print($"Calling a Bjarne'd function: {func2(example).quoted()}");

        // the function is just an object, and invocation (and in this case, binding,
        // as indicated by the '&' operator which requests a reference) is accomplished
        // using the "()" operator
        val func3 = Example.oneMoreThan;                // <-- type: function Int(Int)
        val func4 = &func3(13);                         // <-- type: function Int()
        console.print($"Calling a fully bound function: {func4()}");
    }
}
</syntaxhighlight>

{{out}}
<pre>
Result from calling a method: "This is an example with text=hello!"
Results from calling a function: 13
Calling a bound method: "This is an example with text=hello!"
Calling a Bjarne'd function: "This is an example with text=hello!"
Calling a fully bound function: 14
</pre>

=={{header|Elena}}==
The message call:
<syntaxhighlight lang="elena">
    console.printLine("Hello"," ","World!");
</syntaxhighlight>
=={{header|Elixir}}==
Elixir doesn't do objects.  Instead of calling methods on object you send messages to processes.  Here's an example of a process created with spawn_link which knows how to receive a message "concat" and return a result.
<syntaxhighlight lang="elixir">
defmodule ObjectCall do
  def new() do
    spawn_link(fn -> loop end)
  end
  
  defp loop do
    receive do
      {:concat, {caller, [str1, str2]}} ->
        result = str1 <> str2
        send caller, {:ok, result}
        loop
    end
  end
  
  def concat(obj, str1, str2) do
    send obj, {:concat, {self(), [str1, str2]}}

    receive do
      {:ok, result} ->
        result
    end
  end
end

obj = ObjectCall.new()

IO.puts(obj |> ObjectCall.concat("Hello ", "World!"))
</syntaxhighlight>

=={{header|EMal}}==
{{trans|Wren}}
<syntaxhighlight lang="emal">
type MyClass ^|we are defining a new data type and entering in its static context|^
fun method = void by block do writeLine("static method called") end
model ^|we enter the instance context|^
  fun method = void by block do writeLine("instance method called") end
end
type CallAnObjectMethod
var myInstance = MyClass() ^|creating an instance|^
myInstance.method()
MyClass.method()
</syntaxhighlight>
{{out}}
<pre>
instance method called
static method called
</pre>

=={{header|Factor}}==
In Factor, there is no distinction between instance and static methods. Methods are contained in generic words and specialize on a class. Generic words define a <i>method combination</i> so methods know which object(s) to dispatch on. (But most methods dispatch on the object at the top of the data stack.) Under this object model, calling a method is no different than calling any other word.

<syntaxhighlight lang="factor">USING: accessors io kernel literals math sequences ;
IN: rosetta-code.call-a-method

! Define some classes.
SINGLETON: dog
TUPLE: cat sassiness ;

! Define a constructor for cat.
C: <cat> cat

! Define a generic word that dispatches on the object at the top
! of the data stack.
GENERIC: speak ( obj -- )

! Define methods in speak which specialize on various classes.
M: dog speak drop "Woof!" print ;
M: cat speak sassiness>> 0.5 > "Hiss!" "Meow!" ? print ;
M: object speak drop "I don't know how to speak!" print ;

! Call speak on various objects.
! Despite being a method, it's called like any other word.
dog speak
0.75 <cat> speak
0.1 <cat> speak
"bird" speak</syntaxhighlight>
{{out}}
<pre>
Woof!
Hiss!
Meow!
I don't know how to speak!
</pre>
=={{header|Forth}}==
{{works with|4tH|3.62.0}}
{{trans|D}}
There are numerous, mutually incompatible object oriented frameworks for Forth. This one works with the FOOS preprocessor extension of [[4tH]].
<syntaxhighlight lang="forth">include lib/compare.4th
include 4pp/lib/foos.4pp

[ASSERT]                               \ enable assertions

:: Cat
   class
     method: dynamicCat                \ virtual method
   end-class {

    :static staticCat { 2 } ;          \ static method
    :method { s" Mew!" } ; defines dynamicCat
  }                                    \ for unrelated classes,
;                                      \ method names have to differ

:: Dog
   class
     method: dynamicDog                \ virtual method
   end-class {

    :static staticDog { 5 } ;
    :method { s" Woof!" } ; defines dynamicDog
  }                                    \ for unrelated classes,
;                                      \ method names have to differ

static Cat c                           \ create two static objects
static Dog d

: main
  assert( class -> staticCat 2 = )     \ check for valid method return
  assert( class -> staticDog 5 = )     \ of a static method

  assert( c -> staticCat 2 = )         \ check for valid method return
  assert( d -> staticDog 5 = )         \ of a static method

  assert( c => dynamicCat s" Mew!"  compare 0= )
  assert( d => dynamicDog s" Woof!" compare 0= )
;                                      \ same for dynamic methods

main</syntaxhighlight>

Works with any ANS Forth

Needs the FMS-SI (single inheritance) library code located here:
http://soton.mpeforth.com/flag/fms/index.html
<syntaxhighlight lang="forth">include FMS-SI.f

:class animal
  variable cnt 0 cnt ! \ static instance variable
  :m init: 1 cnt +! ;m
  :m cnt: cnt @ . ;m
;class

:class cat <super animal
  :m speak ." meow" ;m
;class

:class dog <super animal
  :m speak ." woof" ;m
;class

cat Frisky   \ instantiate a cat object named Frisky
dog Sparky   \ instantiate a dog object named Sparky

\ The class method cnt: will return the number of animals instantiated
\ regardless of which animal object is used.

\ The instance method speak will respond differently depending
\ on the class of the instance object.

Frisky cnt:  \ => 2 ok
Sparky cnt:  \ => 2 ok
Frisky speak \ => meow ok
Sparky speak \ => woof ok
</syntaxhighlight>
=={{header|Fortran}}==
In modern Fortran a "derived type" concept corresponds to "class" in OOP. Such types have "type bound procedures", i.e. static methods. Procedure pointer components depend on the value of the object (so they are object-bound), can be redefined runtime and correspond approx to instances.
<syntaxhighlight lang="fortran">
! type declaration
type my_type
 contains
procedure, pass :: method1
procedure, pass, pointer :: method2
end type my_type

! declare object of type my_type
type(my_type) :: mytype_object

!static call
 call mytype_object%method1() ! call method1 defined as subroutine
!instance?
 mytype_object%method2() ! call method2 defined as function

</syntaxhighlight>
=={{header|FreeBASIC}}==
<syntaxhighlight lang="freebasic">
' FB 1.05.0 Win64

Type MyType
  Public:
    Declare Sub InstanceMethod(s As String)
    Declare Static Sub StaticMethod(s As String)
  Private:
    dummy_ As Integer ' types cannot be empty in FB
End Type

Sub MyType.InstanceMethod(s As String)
  Print s
End Sub

Static Sub MyType.StaticMethod(s As String)
  Print s
End Sub

Dim t As MyType
t.InstanceMethod("Hello world!")
MyType.Staticmethod("Hello static world!")
Print
Print "Press any key to quit the program"
Sleep 
</syntaxhighlight>

{{out}}
<pre>
Hello world!
Hello static world!
</pre>

=={{header|FutureBasic}}==
<syntaxhighlight lang="futurebasic">
local fn FBClassDemo
  // Class
  ClassRef class = fn MutableStringClass
  // Cocoa base class name as human-readable string
  print fn StringFromClass( class )
  
  // Instantiate
  CFMutableStringRef mutStr = fn MutableStringNew
  
  // Method with single argument
  MutableStringSetString( mutStr, @"Hello, World!" )
  print mutStr
  
  // Method with multiple arguments
  MutableStringReplaceAllOccurrencesOfString( mutStr, @"World", @"Rosetta Code" )
  print mutStr
end fn

fn FBClassDemo

HandleEvents
</syntaxhighlight>
{{output}}
<pre>
NSMutableString
Hello, World!
Hello, Rosetta Code!
</pre>

=={{header|Go}}==
Go distances itself from the word "object" and from many object oriented concepts.  It does however have methods.  Any user-defined type in Go can have methods and these work very much like "instance methods" of object oriented languages.  The examples below illustrate details of Go methods and thus represent the concept of instance methods.
<syntaxhighlight lang="go">type Foo int // some custom type

// method on the type itself; can be called on that type or its pointer
func (self Foo) ValueMethod(x int) { }

// method on the pointer to the type; can be called on pointers
func (self *Foo) PointerMethod(x int) { }


var myValue Foo
var myPointer *Foo = new(Foo)

// Calling value method on value
myValue.ValueMethod(someParameter)
// Calling pointer method on pointer
myPointer.PointerMethod(someParameter)

// Value methods can always be called on pointers
// equivalent to (*myPointer).ValueMethod(someParameter)
myPointer.ValueMethod(someParameter)

// In a special case, pointer methods can be called on values that are addressable (i.e. lvalues)
// equivalent to (&myValue).PointerMethod(someParameter)
myValue.PointerMethod(someParameter)

// You can get the method out of the type as a function, and then explicitly call it on the object
Foo.ValueMethod(myValue, someParameter)
(*Foo).PointerMethod(myPointer, someParameter)
(*Foo).ValueMethod(myPointer, someParameter)</syntaxhighlight>
Go has no direct equivalent to class methods as long as you think of a Go type as a class.  A Go ''package'' however can be organized and used much like a class, and in this context, any function exported from the package works much like a class method.

An example package:
<syntaxhighlight lang="go">package box

import "sync/atomic"

var sn uint32

type box struct {
    Contents string
    secret uint32
}

func New() (b *box) {
    b = &box{secret: atomic.AddUint32(&sn, 1)}
    switch sn {
    case 1:
        b.Contents = "rabbit"
    case 2:
        b.Contents = "rock"
    }
    return
}

func (b *box) TellSecret() uint32 {
    return b.secret
}

func Count() uint32 {
    return atomic.LoadUint32(&sn)
}</syntaxhighlight>
Example use:
<syntaxhighlight lang="go">package main

import "box"

func main() {
    // Call constructor.  Technically it's just an exported function,
    // but it's a Go idiom to naming a function New that serves the purpose
    // of a constructor.
    b := box.New() 

    // Call instance method.  In Go terms, simply a method.
    b.TellSecret()
    
    // Call class method.  In Go terms, another exported function.
    box.Count()
}</syntaxhighlight>

==Icon and {{header|Unicon}}==
Icon does not have objects or methods; they can be implemented on top of other types such as records.

Unicon has no concept of static methods; all methods are normally invoked using an instance of a class. While it is technically possible to call a method without an instance, it requires knowledge of the underlying implementation, such as the name-mangling conventions, and is non-standard.  
<syntaxhighlight lang="unicon">procedure main()

   bar := foo()  # create instance
   bar.m2()      # call method m2 with self=bar, an implicit first parameter

   foo_m1( , "param1", "param2")  # equivalent of static class method, first (self) parameter is null
end

class foo(cp1,cp2)
   method m1(m1p1,m1p2)
      local ml1
      static ms1
      ml1 := m1p1
      # do something
      return
   end
   method m2(m2p1)
      # do something else
      return
   end
initially 
   L := [cp1]
end</syntaxhighlight>
=={{header|Haskell}}==

Haskell doesn't have objects in OOP sence (i.e. first-class sitizens 
appearing in runtime with incapsulated state and ability to send messages (methods) to other objects). 

Haskell has first-class immutable records with fields of any type, representing abstraction and incapsulation (due to purity). 
Polymorphism is implemented via type-classes, which are similar to OOP interfaces. 

Dummy example: 
<syntaxhighlight lang="haskell">data Obj = Obj { field :: Int, method :: Int -> Int }

-- smart constructor
mkAdder :: Int -> Obj
mkAdder x = Obj x (+x) 

-- adding method from a type class
instanse Show Obj where
  show o = "Obj " ++ show (field o) </syntaxhighlight>

<pre>*Main> let o1 = Obj 1 (*5) 
*Main> field o1
1
*Main> method o1 6
30
*Main> show o1
Obj 1

*Main> let o2 = mkAdder 5
*Main> field o2
5
*Main> method o2 6
11
*Main> show o2
Obj 5</pre>
=={{header|J}}==

Note: In some languages "everything is an object".  This is not the case in J.  In J, non-trivial objects will contain arrays.  This is a relatively deep issue, beyond the scope of this page, except that: method invocations are relatively rare, in J.

All method invocations must contain two underline characters in J:

Static:

<syntaxhighlight lang="j">methodName_className_ parameters</syntaxhighlight>

and, given an object instance reference:

<syntaxhighlight lang="j">objectReference=:'' conew 'className'</syntaxhighlight>

an instance invocation could be:

<syntaxhighlight lang="j">methodName__objectReference parameters</syntaxhighlight>

Note that J also supports infix notation when using methods.  In this case, there will be a second parameter list, on the left of the method reference.

<syntaxhighlight lang="j">parameters methodName_className_ parameters</syntaxhighlight>
or
<syntaxhighlight lang="j">parameters methodName__objectReference parameters</syntaxhighlight>

These variations might be useful when building combining words that need to refer to two different kinds of things.  But mostly it's to be consistent with the rest of the language.

Finally, note that static methods can be referred to using the same notation as instance methods -- in this case you must have a reference to the class name:

<syntaxhighlight lang="j">classReference=: <'className'
methodName__classReference parameters</syntaxhighlight>

This might be useful when you are working with a variety of classes which share a common structure.

You can also refer to a dynamic method in the same fashion that you use to refer to a instance method -- in this case you must know the object name (which is a number).  For example, to refer to a method on object 123

<syntaxhighlight lang="j">methodName_123_ parameters</syntaxhighlight>

This last case can be useful when debugging.
=={{header|Java}}==
Static methods in Java are usually called by using the dot operator on a class name:
<syntaxhighlight lang="java">ClassWithStaticMethod.staticMethodName(argument1, argument2);//for methods with no arguments, use empty parentheses</syntaxhighlight>
Instance methods are called by using the dot operator on an instance:
<syntaxhighlight lang="java">ClassWithMethod varName = new ClassWithMethod();
varName.methodName(argument1, argument2);
//or
new ClassWithMethod().methodName(argument1, argument2);</syntaxhighlight>

Instance methods may not be called on references whose value is <code>null</code> (throws a <code>NullPointerException</code>). <!--Maybe add reflection stuff here too? It might be too complicated or it might not belong here-->

Note: Static methods can also be called using the dot syntax on a reference to an instance, looking identical to an instance method call, but this is highly discouraged, and compilers usually complain about that (with a warning, not a failed compilation). The reason for this is that such a call is actually equivalent to a static method call on the ''static (compile-time) type'' of the reference in the source code. That means the runtime value of that reference is actually irrelevant, and the reference may be <code>null</code> or be a reference to an instance of a subclass, the compiler will still make it a call to the static method based on the class of the value at compile-time (i.e. inheritance does not apply; the method call is not resolved at runtime).

This means that there is no benefit to making a static method call this way, because one can make the call based on the static type that is already known from looking at the code when it is written. Furthermore, such a call may lead to serious pitfalls, leading one to believe that changing the object that it is called on could change the behavior. For example, a common snippet to sleep the thread for 1 second is the following: <code>Thread.currentThread().sleep(1000);</code>. However, since <code>.sleep()</code> is actually a static method, the compiler replaces it with <code>Thread.sleep(1000);</code> (since <code>Thread.currentThread()</code> has a return type of <code>Thread</code>). This makes it clear that the thread that is put to sleep is not under the user's control. However, written as <code>Thread.currentThread().sleep(1000);</code>, it may lead one to falsely believe it to be possible to sleep another thread by doing <code>someOtherThread.sleep(1000);</code> when in fact such a statement would also sleep the current thread.
=={{header|JavaScript}}==
If you have a object called <tt>x</tt> and a method called <tt>y</tt> then you can write:
<syntaxhighlight lang="javascript">x.y()</syntaxhighlight>
=={{header|Julia}}==
    module Animal

    abstract type Animal end
    abstract type Dog <: Animal end
    abstract type Cat <: Animal end
 
    struct Collie <: Dog
        name::String
        weight::Float64
    end

    struct Persian <: Cat
        name::String
        weight::Float64
    end

    #
    # This function is static: it works on any dog, even on a blank instance, in 
    #   the same way, to produce the same output for anything that isa Dog in type.
    #
    function soundalert(a::T) where T <: Dog
        println("Woof!")
    end

    #
    # This function depends on the class instance's data for its value, so this type
    #   of function is one way to do an instance method in Jula.
    #
    masskg(x) = x.weight
=={{header|Kotlin}}==
Kotlin does not have static methods, but they can be easily simulated by <code>companion object</code> methods.

<syntaxhighlight lang="kotlin">class MyClass {
    fun instanceMethod(s: String) = println(s)

    companion object {
        fun staticMethod(s: String) = println(s)
    }
}

fun main() {
    val mc = MyClass()
    mc.instanceMethod("Hello instance world!")
    MyClass.staticMethod("Hello static world!")
}</syntaxhighlight>

{{out}}
<pre>
Hello instance world!
Hello static world!
</pre>

=={{header|Latitude}}==

In Latitude, everything is an object. Being prototype-oriented, Latitude does not distinguish between classes and instances. Calling a method on either a class or an instance is done by simple juxtaposition.
<syntaxhighlight lang="latitude">myObject someMethod (arg1, arg2, arg3).
MyClass someMethod (arg1, arg2, arg3).</syntaxhighlight>
The parentheses on the argument list may be omitted if there is at most one argument and the parse is unambiguous.
<syntaxhighlight lang="latitude">myObject someMethod "string constant argument".
myObject someMethod (argument). ;; Parentheses are necessary here
myObject someMethod. ;; No arguments</syntaxhighlight>
Finally, a colon may be used instead of parentheses, in which case the rest of the line is considered to be the argument list.
<syntaxhighlight lang="latitude">myObject someMethod: arg1, arg2, arg3.</syntaxhighlight>
=={{header|LFE}}==

LFE/Erlang doesn't have an object system. However, since LFE is a Lisp, one can do the same thing in LFE as one did in Lisps before CLOS: use closures to create and work with objects. 

Not only that, but one may also use Erlang lightweight process to accomplish something very similar!

Examples for both approaches are given below.


===With Closures===
<syntaxhighlight lang="lisp">(defmodule aquarium
 (export all))

(defun fish-class (species)
  "
  This is the constructor that will be used most often, only requiring that
  one pass a 'species' string.

  When the children are not defined, simply use an empty list.
  "
  (fish-class species ()))

(defun fish-class (species children)
  "
  This contructor is mostly useful as a way of abstracting out the id
  generation from the larger constructor. Nothing else uses fish-class/2
  besides fish-class/1, so it's not strictly necessary.

  When the id isn't know, generate one.
  "
  (let* (((binary (id (size 128))) (: crypto rand_bytes 16))
         (formatted-id (car
                         (: io_lib format
                           '"~32.16.0b" (list id)))))
    (fish-class species children formatted-id)))

(defun fish-class (species children id)
  "
  This is the constructor used internally, once the children and fish id are
  known.
  "
  (let ((move-verb '"swam"))
    (lambda (method-name)
      (case method-name
        ('id
          (lambda (self) id))
        ('species
          (lambda (self) species))
        ('children
          (lambda (self) children))
        ('info
          (lambda (self)
            (: io format
              '"id: ~p~nspecies: ~p~nchildren: ~p~n"
              (list (get-id self)
                    (get-species self)
                    (get-children self)))))
        ('move
          (lambda (self distance)
            (: io format
              '"The ~s ~s ~p feet!~n"
              (list species move-verb distance))))
        ('reproduce
          (lambda (self)
            (let* ((child (fish-class species))
                   (child-id (get-id child))
                   (children-ids (: lists append
                                   (list children (list child-id))))
                   (parent-id (get-id self))
                   (parent (fish-class species children-ids parent-id)))
              (list parent child))))
        ('children-count
          (lambda (self)
            (: erlang length children)))))))

(defun get-method (object method-name)
  "
  This is a generic function, used to call into the given object (class
  instance).
  "
  (funcall object method-name))

; define object methods
(defun get-id (object)
  (funcall (get-method object 'id) object))

(defun get-species (object)
  (funcall (get-method object 'species) object))

(defun get-info (object)
  (funcall (get-method object 'info) object))

(defun move (object distance)
  (funcall (get-method object 'move) object distance))

(defun reproduce (object)
  (funcall (get-method object 'reproduce) object))

(defun get-children (object)
  (funcall (get-method object 'children) object))

(defun get-children-count (object)
  (funcall (get-method object 'children-count) object))
</syntaxhighlight>

With this done, one can create objects and interact with them. Here is some usage from the LFE REPL:
<syntaxhighlight lang="lisp">; Load the file and create a fish-class instance:

> (slurp '"object.lfe")
#(ok object)
> (set mommy-fish (fish-class '"Carp"))
#Fun<lfe_eval.10.91765564>

; Execute some of the basic methods:

> (get-species mommy-fish)
"Carp"
> (move mommy-fish 17)
The Carp swam 17 feet!
ok
> (get-id mommy-fish)
"47eebe91a648f042fc3fb278df663de5"

; Now let's look at "modifying" state data (e.g., children counts):

> (get-children mommy-fish)
()
> (get-children-count mommy-fish)
0
> (set (mommy-fish baby-fish-1) (reproduce mommy-fish))
(#Fun<lfe_eval.10.91765564> #Fun<lfe_eval.10.91765564>)
> (get-id mommy-fish)
"47eebe91a648f042fc3fb278df663de5"
> (get-id baby-fish-1)
"fdcf35983bb496650e558a82e34c9935"
> (get-children-count mommy-fish)
1
> (set (mommy-fish baby-fish-2) (reproduce mommy-fish))
(#Fun<lfe_eval.10.91765564> #Fun<lfe_eval.10.91765564>)
> (get-id mommy-fish)
"47eebe91a648f042fc3fb278df663de5"
> (get-id baby-fish-2)
"3e64e5c20fb742dd88dac1032749c2fd"
> (get-children-count mommy-fish)
2
> (get-info mommy-fish)
id: "47eebe91a648f042fc3fb278df663de5"
species: "Carp"
children: ["fdcf35983bb496650e558a82e34c9935",
           "3e64e5c20fb742dd88dac1032749c2fd"]
ok</syntaxhighlight>

===With Lightweight Processes===
<syntaxhighlight lang="lisp">(defmodule object
 (export all))

(defun fish-class (species)
  "
  This is the constructor that will be used most often, only requiring that
  one pass a 'species' string.

  When the children are not defined, simply use an empty list.
  "
  (fish-class species ()))

(defun fish-class (species children)
  "
  This constructor is useful for two reasons: 
    1) as a way of abstracting out the id generation from the 
       larger constructor, and
    2) spawning the 'object loop' code (fish-class/3).
  "
  (let* (((binary (id (size 128))) (: crypto rand_bytes 16))
         (formatted-id (car
                         (: io_lib format
                           '"~32.16.0b" (list id)))))
    (spawn 'object
           'fish-class
           (list species children formatted-id))))

(defun fish-class (species children id)
  "
  This function is intended to be spawned as a separate process which is
  used to track the state of a fish. In particular, fish-class/2 spawns
  this function (which acts as a loop, pattern matching for messages).
  "
  (let ((move-verb '"swam"))
    (receive
      ((tuple caller 'move distance)
        (! caller (list species move-verb distance))
        (fish-class species children id))
      ((tuple caller 'species)
        (! caller species)
        (fish-class species children id))
      ((tuple caller 'children)
        (! caller children)
        (fish-class species children id))
      ((tuple caller 'children-count)
        (! caller (length children))
        (fish-class species children id))
      ((tuple caller 'id)
        (! caller id)
        (fish-class species children id))
      ((tuple caller 'info)
        (! caller (list id species children))
        (fish-class species children id))
      ((tuple caller 'reproduce)
        (let* ((child (fish-class species))
               (child-id (get-id child))
               (children-ids (: lists append
                               (list children (list child-id)))))
        (! caller child)
        (fish-class species children-ids id))))))

(defun call-method (object method-name)
  "
  This is a generic function, used to call into the given object (class
  instance).
  "
  (! object (tuple (self) method-name))
  (receive
    (data data)))

(defun call-method (object method-name arg)
  "
  Same as above, but with an additional argument.
  "
  (! object (tuple (self) method-name arg))
  (receive
    (data data)))

; define object methods
(defun get-id (object)
  (call-method object 'id))

(defun get-species (object)
  (call-method object 'species))

(defun get-info (object)
  (let ((data (call-method object 'info)))
    (: io format '"id: ~s~nspecies: ~s~nchildren: ~p~n" data)))

(defun move (object distance)
  (let ((data (call-method object 'move distance)))
    (: io format '"The ~s ~s ~p feet!~n" data)))

(defun reproduce (object)
  (call-method object 'reproduce))

(defun get-children (object)
  (call-method object 'children))

(defun get-children-count (object)
  (call-method object 'children-count))</syntaxhighlight>

Here is some usage from the LFE REPL:
<syntaxhighlight lang="lisp">; Load the file and create a fish-class instance:

> (slurp '"object.lfe")
#(ok object)
> (set mommy-fish (fish-class '"Carp"))
<0.33.0>

; Execute some of the basic methods:

> (get-species mommy-fish)
"Carp"
> (move mommy-fish 17)
The Carp swam 17 feet!
ok
> (get-id mommy-fish)
"47eebe91a648f042fc3fb278df663de5"

; Now let's look at modifying state data:

> (get-children mommy-fish)
()
> (get-children-count mommy-fish)
0
> (set baby-fish-1 (reproduce mommy-fish))
<0.34.0>
> (get-id mommy-fish)
"47eebe91a648f042fc3fb278df663de5"
> (get-id baby-fish-1)
"fdcf35983bb496650e558a82e34c9935"
> (get-children-count mommy-fish)
1
> (set baby-fish-2 (reproduce mommy-fish))
<0.35.0>
> (get-id mommy-fish)
"47eebe91a648f042fc3fb278df663de5"
> (get-id baby-fish-2)
"3e64e5c20fb742dd88dac1032749c2fd"
> (get-children-count mommy-fish)
2
> (get-info mommy-fish)
id: 47eebe91a648f042fc3fb278df663de5
species: Carp
children: ["fdcf35983bb496650e558a82e34c9935",
           "3e64e5c20fb742dd88dac1032749c2fd"]
ok</syntaxhighlight>
=={{header|Lingo}}==
<syntaxhighlight lang="lingo">-- call static method
script("MyClass").foo()

-- call instance method
obj = script("MyClass").new()
obj.foo()</syntaxhighlight>
=={{header|Logtalk}}==
In Logtalk, class or instance are ''roles'' that an object can play depending on the relations in other objects. Thus, a "class" can be defined by having an object specializing another object and an instance can be defined by having an object instantiating another object. Metaclasses are easily defined and thus a class method is just an instance method defined in the class metaclass.
<syntaxhighlight lang="logtalk">
% avoid infinite metaclass regression by
% making the metaclass an instance of itself
:- object(metaclass,
    instantiates(metaclass)).

    :- public(me/1).
    me(Me) :-
        self(Me).
 
:- end_object.
</syntaxhighlight>
<syntaxhighlight lang="logtalk">
:- object(class,
    instantiates(metaclass)).

    :- public(my_class/1).
    my_class(Class) :-
        self(Self),
        instantiates_class(Self, Class).
 
:- end_object.
</syntaxhighlight>
<syntaxhighlight lang="logtalk">
:- object(instance,
    instantiates(class)).

:- end_object.
</syntaxhighlight>
Testing:
<syntaxhighlight lang="logtalk">
| ?- class::me(Me).
Me = class
yes

| ?- instance::my_class(Class).
Class = class
yes
</syntaxhighlight>
=={{header|Lua}}==
Lua does not provide a specific OO implementation, but its metatable mechanism and sugar for method-like calls does make it easy to implement and use such as system, as evidenced by its multitude of class libraries in particular.

Instance methods, in their most basic form, are simply function calls where the calling object reference is duplicated and passed as the first argument. Lua offers some syntactical sugar to facilitate this, via the colon operator:
<syntaxhighlight lang="lua">local object = { name = "foo", func = function (self) print(self.name) end }

object:func() -- with : sugar
object.func(object) -- without : sugar</syntaxhighlight>

Using metatables, and specifically the __index metamethod, it is possible to call a method stored in an entirely different table, while still passing the object used for the actual call:
<syntaxhighlight lang="lua">local methods = { }
function methods:func () -- if a function is declared using :, it is given an implicit 'self' parameter
    print(self.name)
end

local object = setmetatable({ name = "foo" }, { __index = methods })

object:func() -- with : sugar
methods.func(object) -- without : sugar</syntaxhighlight>

Lua does not have a specific way of handling static methods, but similarly to Go, they could simply be implemented as regular functions inside of a module.

Example module, named <code>box.lua</code>:
<syntaxhighlight lang="lua">local count = 0 
local box = { }
local boxmt = { __index = box }
function box:tellSecret ()
    return self.secret
end

local M = { }
function M.new () 
    count = count + 1
    return setmetatable({ secret = count, contents = count % 2 == 0 and "rabbit" or "rock" }, boxmt)
end
function M.count () 
    return count
end
return M</syntaxhighlight> 

Example use:
<syntaxhighlight lang="lua">local box = require 'box'

local b = box.new()

print(b:tellSecret())
print(box.count())</syntaxhighlight>
=={{header|M2000 Interpreter}}==
In M2000 there are some kinds of objects. Group is an object. We can compose members to groups, with functions, operators, modules, events, and inner groups, among other members of type pointer to object. Another type is the COM type. Here we see the Group object
<syntaxhighlight lang="m2000 interpreter">
Module CheckIt {
      \\ A class definition is a function which return a Group
      \\ We can make groups and we can alter them using Group statement
      \\ Groups may have other groups inside
      
      Group Alfa {
      Private:
            myvalue=100
      Public:
            Group SetValue {
                  Set (x) {
                        Link parent myvalue to m
                        m<=x
                  }
            }
            Module MyMethod {
                 Read x
                 Print x*.myvalue 
            }
      }
      
      Alfa.MyMethod 5 '500
      Alfa.MyMethod %x=200   ' 20000
      \\ we can copy Alfa to Z
      Z=Alfa
      Z.MyMethod 5
      Z.SetValue=300
      Z.MyMethod 5 ' 1500     
      Alfa.MyMethod 5    ' 500
      Dim A(10)
      A(3)=Z
      A(3).MyMethod 5 '1500
      A(3).SetValue=200
      A(3).MyMethod 5 '1000
      \\ get a pointer of group in A(3)
      k->A(3)
      k=>SetValue=100
      A(3).MyMethod 5 '500
      \\ k get pointer to Alfa
      k->Alfa
      k=>SetValue=500
      Alfa.MyMethod 5 '2500
      k->Z
      k=>MyMethod 5 ' 1500
      Z.SetValue=100
      k=>MyMethod 5 ' 500
}
Checkit
</syntaxhighlight>

=={{header|Maple}}==
There is no real difference in how you call a static or instance method.
<syntaxhighlight lang="maple"># Static
Method( obj, other, arg );</syntaxhighlight>
<syntaxhighlight lang="maple"># Instance
Method( obj, other, arg );</syntaxhighlight>
=={{header|MiniScript}}==
MiniScript uses prototype-based inheritance, so the only difference between a static method and an instance method is in whether it uses the <code>self</code> pseudo-keyword.
<syntaxhighlight lang="miniscript">Dog = {}
Dog.name = ""
Dog.help = function()
    print "This class represents dogs."
end function
Dog.speak = function()
    print self.name + " says Woof!"
end function

fido = new Dog
fido.name = "Fido"

Dog.help    // calling a "class method"
fido.speak  // calling an "instance method"</syntaxhighlight>

{{out}}
<pre>This class represents dogs.
Fido says Woof!</pre>
=={{header|Nanoquery}}==
<syntaxhighlight lang="nanoquery">class MyClass
	declare static id = 5
	declare MyName

	// constructor
	def MyClass(MyName)
		this.MyName = MyName
	end

	// class method
	def getName()
		return this.MyName
	end

	// static method
	def static getID()
		return id
	end
end

// call the static method
println MyClass.getID()

// instantiate a new MyClass object with the name "test"
// and call the class method
myclass = new(MyClass, "test")
println myclass.getName()</syntaxhighlight>
{{out}}
<pre>5
test</pre>
=={{header|Nemerle}}==
<syntaxhighlight lang="nemerle">// Static
MyClass.Method(someParameter);
 
// Instance
myInstance.Method(someParameter);</syntaxhighlight>
=={{header|NetRexx}}==
Like [[#Java|Java]], static methods in NetRexx are called by using the dot operator on a class name:
<syntaxhighlight lang="netrexx">SomeClass.staticMethod()</syntaxhighlight>
Instance methods are called by using the dot operator on an instance:
<syntaxhighlight lang="netrexx">objectInstance = SomeClass() -- create a new instance of the class
objectInstance.instanceMethod() -- call the instance method

SomeClass().instanceMethod() -- same as above; create a new instance of the class and call the instance method immediately</syntaxhighlight>
=={{header|Nim}}==
In Nim there are no object methods, but regular procedures can be called with method call syntax:
<syntaxhighlight lang="nim">var x = @[1, 2, 3]
add(x, 4)
x.add(5)</syntaxhighlight>
=={{header|OASYS Assembler}}==
The OASYS runtime is strange; all classes share the same methods and properties, there are no static methods and properties, and there are no procedures/functions other than methods on objects. However, the initialization method can be called on a null object (no other method has this possibility).

The following code calls a method called <tt>&amp;GO</tt> on the current object:
<syntaxhighlight lang="oasys_oaa">+&GO</syntaxhighlight>
=={{header|Objeck}}==
<syntaxhighlight lang="objeck">
ClassName->some_function(); # call class function
instance->some_method(); # call instance method</syntaxhighlight>
Objeck uses the same syntax for instance and class method calls. In Objeck, functions are the equivalent of public static methods.
=={{header|Object Pascal}}==

Object Pascal as implemented in Delphi and Free Pascal supports both static (known in Pascal as class method) and instance methods. Free Pascal has two levels of static methods, one using the class keyword and one using both the class and the static keywords. A class method can be called in Pascal, while a static class method could be called even from C, that's the main difference.

<syntaxhighlight lang="pascal">// Static (known in Pascal as class method)
MyClass.method(someParameter);

// Instance
myInstance.method(someParameter);
</syntaxhighlight>
=={{header|Objective-C}}==
In Objective-C, calling an instance method is sending a message to an instance, and calling a class method is sending a message to a class object. Class methods are inherited through inheritance of classes. All messages (whether sent to a normal object or class object) are resolved dynamically at runtime, hence there are no "static" methods (see also: Smalltalk).
<syntaxhighlight lang="objc">// Class
[MyClass method:someParameter];
// or equivalently:
id foo = [MyClass class];
[foo method:someParameter];

// Instance
[myInstance method:someParameter];

// Method with multiple arguments
[myInstance methodWithRed:arg1 green:arg2 blue:arg3];

// Method with no arguments
[myInstance method];</syntaxhighlight>
=={{header|OCaml}}==

We can only call the method of an instantiated object:

<syntaxhighlight lang="ocaml">my_obj#my_meth params</syntaxhighlight>
=={{header|Oforth}}==
When a method is called, the top of the stack is used as the object on which the method will be applyed : 
<syntaxhighlight lang="oforth">1.2 sqrt</syntaxhighlight>

For class methods, the top of the stack must be a class (which is also an object of Class class) : 
<syntaxhighlight lang="oforth">Date now</syntaxhighlight>
=={{header|ooRexx}}==
<syntaxhighlight lang="oorexx">say "pi:" .circle~pi
c=.circle~new(1)
say "c~area:" c~area
Do r=2 To 10
 c.r=.circle~new(r)
 End
say .circle~instances('') 'circles were created'

::class circle
::method pi class -- a class method
  return 3.14159265358979323

::method instances class -- another class method
  expose in
  use arg a
  If datatype(in)<>'NUM' Then in=0
  If a<>'' Then
    in+=1
  Return in

::method init
  expose radius
  use arg radius
  self~class~instances('x')

::method area     -- an instance method
  expose radius
  Say self~class
  Say self
  return self~class~pi * radius * radius        </syntaxhighlight>
'''Output:'''
<pre>pi: 3.14159265358979323
The CIRCLE class
a CIRCLE
c~area: 3.14159265
10 circles were created</pre>
=={{header|PascalABC.NET}}==
<syntaxhighlight lang="delphi">
type 
  Point = auto class // class with autogenerated constructor
    x,y: real;
    static function RandomPoint := new Point(Random(-10..10),Random(-10..10));
    procedure Print;
    begin
      Writeln($'{x} {y}');
    end;
  end;

begin
  var p := new Point(2,3);
  p.Print; // instance method call
  p := Point.RandomPoint; // static method call
  p.Print;
end.
</syntaxhighlight>


=={{header|Perl}}==
<syntaxhighlight lang="perl"># Class method
MyClass->classMethod($someParameter);
# Equivalently using a class name
my $foo = 'MyClass';
$foo->classMethod($someParameter);


# Instance method
$myInstance->method($someParameter);

# Calling a method with no parameters
$myInstance->anotherMethod;

# Class and instance method calls are made behind the scenes by getting the function from
# the package and calling it on the class name or object reference explicitly
MyClass::classMethod('MyClass', $someParameter);
MyClass::method($myInstance, $someParameter);</syntaxhighlight>

=={{header|Phix}}==
{{libheader|Phix/Class}}
Class methods are only "static" (not really a Phix term) if you don't override them.<br>
Phix does not demand that all routines be inside classes; traditional standalone routines are "static" in every sense.<br>
There is no way to call a class method without an instance, since "this" will typecheck even if not otherwise used.
<!--<syntaxhighlight lang="phix">(notonline)-->
 <span style="color: #008080;">without</span> <span style="color: #008080;">js</span> <span style="color: #000080;font-style:italic;">-- (no class in p2js)</span>
 <span style="color: #008080;">class</span> <span style="color: #000000;">test</span>
     <span style="color: #004080;">string</span> <span style="color: #000000;">msg</span> <span style="color: #0000FF;">=</span> <span style="color: #008000;">"this is a test"</span>
     <span style="color: #008080;">procedure</span> <span style="color: #000000;">show</span><span style="color: #0000FF;">()</span> <span style="color: #0000FF;">?</span><span style="color: #7060A8;">this</span><span style="color: #0000FF;">.</span><span style="color: #000000;">msg</span> <span style="color: #008080;">end</span> <span style="color: #008080;">procedure</span>
     <span style="color: #008080;">procedure</span> <span style="color: #000000;">inst</span><span style="color: #0000FF;">()</span> <span style="color: #0000FF;">?</span><span style="color: #008000;">"this is dynamic"</span> <span style="color: #008080;">end</span> <span style="color: #008080;">procedure</span>
 <span style="color: #008080;">end</span> <span style="color: #008080;">class</span>
 <span style="color: #000000;">test</span> <span style="color: #000000;">t</span> <span style="color: #0000FF;">=</span> <span style="color: #7060A8;">new</span><span style="color: #0000FF;">()</span>
 <span style="color: #000000;">t</span><span style="color: #0000FF;">.</span><span style="color: #000000;">show</span><span style="color: #0000FF;">()</span>            <span style="color: #000080;font-style:italic;">-- prints "this is a test"</span>
 <span style="color: #000000;">t</span><span style="color: #0000FF;">.</span><span style="color: #000000;">inst</span><span style="color: #0000FF;">()</span>            <span style="color: #000080;font-style:italic;">-- prints "this is dynamic"</span>
 <span style="color: #000000;">t</span><span style="color: #0000FF;">.</span><span style="color: #000000;">inst</span> <span style="color: #0000FF;">=</span> <span style="color: #000000;">t</span><span style="color: #0000FF;">.</span><span style="color: #000000;">show</span>
 <span style="color: #000000;">t</span><span style="color: #0000FF;">.</span><span style="color: #000000;">inst</span><span style="color: #0000FF;">()</span>            <span style="color: #000080;font-style:italic;">-- prints "this is a test"</span>
<!--</syntaxhighlight>-->
=={{header|PHP}}==
<syntaxhighlight lang="php">// Static method
MyClass::method($someParameter);
// In PHP 5.3+, static method can be called on a string of the class name
$foo = 'MyClass';
$foo::method($someParameter);


// Instance method
$myInstance->method($someParameter);</syntaxhighlight>
=={{header|PicoLisp}}==
Method invocation is syntactically equivalent to normal function calls. Method names have a trailing '>' by convention.
<syntaxhighlight lang="picolisp">(foo> MyClass)
(foo> MyObject)</syntaxhighlight>
=={{header|Pike}}==
Pike does not have static methods. (the <code>static</code> modifier in Pike is similar to <code>protected</code> in C++).

regular methods can be called in these ways:
<syntaxhighlight lang="pike">obj->method();
obj["method"]();
call_function(obj->method);
call_function(obj["method"]);</syntaxhighlight>
<code>call_function()</code> is rarely used anymore.

because <code>()</code> is actually an operator that is applied to a function reference, the following is also possible:
<syntaxhighlight lang="pike">function func = obj->method;
func();</syntaxhighlight>
as alternative to static function, modules are used. a module is essentially a static class. a function in a module can be called like this:
<syntaxhighlight lang="pike">module.func();
module["func"]();</syntaxhighlight>
it should be noted that <code>module.func</code> is resolved at compile time while <code>module["func"]</code> is resolved at runtime.
=={{header|PL/SQL}}==
<syntaxhighlight lang="plsql">create or replace TYPE myClass AS OBJECT (
    -- A class needs at least one member even though we don't use it
    dummy NUMBER,
    STATIC FUNCTION static_method RETURN VARCHAR2,
    MEMBER FUNCTION instance_method RETURN VARCHAR2
);
/
CREATE OR REPLACE TYPE BODY myClass AS
    STATIC FUNCTION static_method RETURN VARCHAR2 IS
    BEGIN
        RETURN 'Called myClass.static_method';
    END static_method;
    
    MEMBER FUNCTION instance_method RETURN VARCHAR2 IS
    BEGIN
        RETURN 'Called myClass.instance_method';
    END instance_method;
END;
/

DECLARE
    myInstance myClass;
BEGIN
    myInstance := myClass(null);
    DBMS_OUTPUT.put_line( myClass.static_method() );
    DBMS_OUTPUT.put_line( myInstance.instance_method() );
END;/</syntaxhighlight>
=={{header|PowerShell}}==
<syntaxhighlight lang="powershell">$Date = Get-Date
$Date.AddDays( 1 )
[System.Math]::Sqrt( 2 )</syntaxhighlight>
=={{header|Processing}}==
<syntaxhighlight lang="processing">// define a rudimentary class
class HelloWorld
{
    public static void sayHello()
    {
        println("Hello, world!");
    }
    public void sayGoodbye()
    {
        println("Goodbye, cruel world!");
    }
}

// call the class method
HelloWorld.sayHello();

// create an instance of the class
HelloWorld hello = new HelloWorld();

// and call the instance method
hello.sayGoodbye();</syntaxhighlight>
=={{header|Python}}==
<syntaxhighlight lang="python">class MyClass(object):
	@classmethod
	def myClassMethod(self, x):
		pass
	@staticmethod
	def myStaticMethod(x):
		pass
	def myMethod(self, x):
		return 42 + x

myInstance = MyClass()

# Instance method
myInstance.myMethod(someParameter)
# A method can also be retrieved as an attribute from the class, and then explicitly called on an instance:
MyClass.myMethod(myInstance, someParameter)


# Class or static methods
MyClass.myClassMethod(someParameter)
MyClass.myStaticMethod(someParameter)
# You can also call class or static methods on an instance, which will simply call it on the instance's class
myInstance.myClassMethod(someParameter)
myInstance.myStaticMethod(someParameter)</syntaxhighlight>
=={{header|Quackery}}==

Quackery is not an Object Oriented language. However it is possible to create a zen-like "distilled essence of object-orientation" in just a few lines of code.

Note that Quackery also does not have operator overloading (but see  
[https://rosettacode.org/wiki/Modular_arithmetic3Quackery Modular arithmetic#Quackery] for an illustration of how this can be achieved) so there is limited inheritance of methods possible - here only the methods <code>localise</code> and <code>delocalise</code> are common to all object types.

(It would be possible to extend this technique to a more fully-fledged object oriented system. See Dick Pountain's slim volume "Object Oriented FORTH: Implementation of Data Structures" (pub. 1987) for an example of doing so in Forth; a language to which Quackery is related, but slightly less amenable to such shenanigans.)

<syntaxhighlight lang="quackery">( ---------------- zen object orientation -------------- )
 
[ immovable 
  ]this[ swap do ]done[ ] is object            (   -->   )
 
[ ]'[ ]                   is method            (   --> [ )
 
[ method 
    [ dup share
      swap put ] ]        is localise          (   --> [ )
 
[ method [ release ] ]    is delocalise        (   --> [ )
 
 
( -------------- example: counter methods -------------- )

( to create a counter object, use: 
           "[ object 0 ]  is 'name' ( [ -->   )"         )
  
[ method 
    [ 0 swap replace ] ]  is reset-counter     (   --> [ )
 
[ method  
    [ 1 swap tally ] ]    is increment-counter (   --> [ )
 
[ method [ share ] ]      is report-counter    (   --> [ )
 
 
( -------------------- demonstration ------------------- )
 
say 'Creating counter object: "mycounter".' cr cr 
[ object 0 ]              is mycounter         ( [ -->   )
 
say "Initial value of mycounter: "
report-counter mycounter echo cr cr
 
say "Incrementing mycounter three times." cr
3 times [ increment-counter mycounter ]
 
say "Current value of mycounter: "
report-counter mycounter echo cr cr
 
say "Localising mycounter." cr cr
localise mycounter
 
say "    Current value of mycounter: "
report-counter mycounter echo cr cr
 
say "    Resetting mycounter." cr
reset-counter mycounter
 
say "    Current value of mycounter: "
report-counter mycounter echo cr cr
 
say "    Incrementing mycounter six times." cr
6 times [ increment-counter mycounter ]
 
say "    Current value of mycounter: "
report-counter mycounter echo cr cr
 
say "Delocalising mycounter." cr cr
delocalise mycounter
 
say "Current value of mycounter: "
report-counter mycounter echo cr cr
 
say "Resetting mycounter." cr
reset-counter mycounter
 
say "Current value of mycounter: "
report-counter mycounter echo cr cr</syntaxhighlight>

{{out}}

<pre>Creating counter object: "mycounter".

Initial value of mycounter: 0

Incrementing mycounter three times.
Current value of mycounter: 3

Localising mycounter.

    Current value of mycounter: 3

    Resetting mycounter.
    Current value of mycounter: 0

    Incrementing mycounter six times.
    Current value of mycounter: 6

Delocalising mycounter.

Current value of mycounter: 3

Resetting mycounter.
Current value of mycounter: 0</pre>
=={{header|Racket}}==

The following snippet shows a call to the <tt>start</tt> method of the <tt>timer%</tt> class.

<syntaxhighlight lang="racket">#lang racket/gui

(define timer (new timer%))
(send timer start 100)</syntaxhighlight>
=={{header|Raku}}==
(formerly Perl 6)
{{works with|Rakudo|2015.12}}
=== Basic method calls ===
<syntaxhighlight lang="raku" line>class Thing { 
  method regular-example() { say 'I haz a method' }

  multi method multi-example() { say 'No arguments given' }
  multi method multi-example(Str $foo) { say 'String given' }
  multi method multi-example(Int $foo) { say 'Integer given' }
};

# 'new' is actually a method, not a special keyword:
my $thing = Thing.new;

# No arguments: parentheses are optional
$thing.regular-example;
$thing.regular-example();
$thing.multi-example;
$thing.multi-example();

# Arguments: parentheses or colon required
$thing.multi-example("This is a string");
$thing.multi-example: "This is a string";
$thing.multi-example(42);
$thing.multi-example: 42;

# Indirect (reverse order) method call syntax: colon required
my $foo = new Thing: ;
multi-example $thing: 42;
</syntaxhighlight>

=== Meta-operators ===

The <code>.</code> operator can be decorated with meta-operators.

<syntaxhighlight lang="raku" line>
my @array = <a z c d y>;
@array .= sort;  # short for @array = @array.sort;

say @array».uc;  # uppercase all the strings: A C D Y Z
</syntaxhighlight>

=== Classless methods ===

A method that is not in a class can be called by using the <code>&</code> sigil explicitly.

<syntaxhighlight lang="raku" line>
my $object = "a string";  # Everything is an object.
my method example-method {
    return "This is { self }.";
}

say $object.&example-method;  # Outputs "This is a string."
</syntaxhighlight>
=={{header|Ring}}==
<syntaxhighlight lang="ring">
new point { print() }
Class Point
        x = 10  y = 20  z = 30
        func print see x + nl + y + nl + z + nl
</syntaxhighlight>
<syntaxhighlight lang="ring">
o1 = new System.output.console
o1.print("Hello World")

Package System.Output
        Class Console
                Func Print cText
                        see cText + nl
</syntaxhighlight>
=={{header|Ruby}}==
<syntaxhighlight lang="ruby"># Class method
MyClass.some_method(some_parameter)

# Class may be computed at runtime
foo = MyClass
foo.some_method(some_parameter)


# Instance method
my_instance.a_method(some_parameter)

# The parentheses are optional
my_instance.a_method some_parameter

# Calling a method with no parameters
my_instance.another_method</syntaxhighlight>
=={{header|Rust}}==
<syntaxhighlight lang="rust">struct Foo;

impl Foo {
    // implementation of an instance method for struct Foo
    // returning the answer to life
    fn get_the_answer_to_life(&self) -> i32 {
        42
    }

    // implementation of a static method for struct Foo
    // returning a new instance object
    fn new() -> Foo {
        println!("Hello, world!");
        Foo // returning the new Foo object
    }
}

fn main() {
    // create the instance object foo,
    // by calling the static method new of struct Foo
    let foo = Foo::new();

    // get the answer to life 
    // by calling the instance method of object foo
    println!("The answer to life is {}.", foo.get_the_answer_to_life());
    
    // Note that in Rust, methods still work on references to the object.
    // Rust will automatically do the appropriate dereferencing to get the method to work:
    let lots_of_references = &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&foo;
    println!("The answer to life is still {}." lots_of_references.get_the_answer_to_life());
}</syntaxhighlight>
=={{header|Scala}}==
<syntaxhighlight lang="scala">/* This class implicitly includes a constructor which accepts an Int and
 *  creates "val variable1: Int" with that value.
 */
class MyClass(val memberVal: Int) { // Acts like a getter, getter automatically generated.
  var variable2 = "asdf" // Another instance variable; a public mutable this time
  def this() = this(0) // An auxilliary constructor that instantiates with a default value
}

object HelloObject {
  val s = "Hello" // Not private, so getter auto-generated
}

/** Demonstrate use of our example class.
 */
object Call_an_object_method extends App {
  val s = "Hello"
  val m = new MyClass
  val n = new MyClass(3)

  assert(HelloObject.s == "Hello") // "Hello" by object getterHelloObject
  assert(m.memberVal == 0)
  assert(n.memberVal == 3)
  println("Successfully completed without error.")
}</syntaxhighlight>
=={{header|Sidef}}==
<syntaxhighlight lang="ruby">class MyClass {
    method foo(arg) { say arg }
}

var arg = 42;

# Call a class method
MyClass.foo(arg);

# Alternatively, using an expression for the method name
MyClass.(:foo)(arg);

# Create an instance
var instance = MyClass();

# Instance method
instance.foo(arg);

# Alternatively, by using an expression for the method name
instance.(:foo)(arg);

# Alternatively, by asking for a method
instance.method(:foo)(arg);</syntaxhighlight>
=={{header|Smalltalk}}==
In Smalltalk, calling an instance method is sending a message to an instance, and calling a class method is sending a message to a class object. Class methods are inherited through inheritance of classes. All messages (whether sent to a normal object or class object) are resolved dynamically at runtime, hence strictly speaking, there are no "static" methods. Often in literature, Smalltalk's class messages are described as synonymous to static function calls. This is wrong, because class methods can be overwritten in subclasses just as any other message. 
Classes are first class objects, meaning that references to them can be passed as argument, stored in other objects or returned as the result of a message send. This makes some of the common design patterns which deal with creation of objects trivial or even superfluous.  (see also: ObjectiveC)

<syntaxhighlight lang="smalltalk">" Class "
MyClass selector: someArgument .
" or equivalently "
foo := MyClass .
foo selector: someArgument.

" Instance "
myInstance selector: someArgument.

" Message with multiple arguments "
myInstance fooWithRed:arg1 green:arg2 blue:arg3 .

" Message with no arguments "
myInstance selector.

" Binary (operator) message"
myInstance + argument .</syntaxhighlight>


Example for dynamic class determination:
<syntaxhighlight lang="smalltalk">theCar := (someCondition ifTrue:[ Ford ] ifFalse: [ Jaguar ]) new.</syntaxhighlight>

Message names (selectors) can be chosen or constructed dynamically at runtime. For example:
<syntaxhighlight lang="smalltalk">whichMessage := #( #'red' #'green' #'blue') at: computedIndex.
foo perform: whichMessage</syntaxhighlight>

or:

<syntaxhighlight lang="smalltalk">theMessage := ('handleFileType' , suffix) asSymbol.
foo perform: theMessage.</syntaxhighlight>
This is often sometimes used as a dispatch mechanism (also, to implement state machines, for example).

Of course, especially with all that dynamics, a selector for an unimplemented message might be encountered. This raises a MessageNotUnderstood exception (runtime exception).
<syntaxhighlight lang="smalltalk">[
    foo perform: theMessage
] on: MessageNotUnderstood do:[
   Dialog information: 'sorry'
]</syntaxhighlight>
=={{header|SuperCollider}}==
In SuperCollider, classes are objects. To call a class or object method, a message is passed to the class or the object instance. In the implementation, class method names are prefixed with an asterix, all other methods are instance methods.
<syntaxhighlight lang="supercollider">
	SomeClass {
	
		*someClassMethod {
			
		}
		
		someInstanceMethod {
			
		}
		
	}
	
	SomeClass.someClassMethod;
	
	a = SomeClass.new;
	a.someInstanceMethod;
</syntaxhighlight>
=={{header|Swift}}==
In Swift, instance methods can be declared on structs, enums, and classes. "Type methods", which include static methods for structs and enums, and class methods for classes, can be called on the type. Class methods are inherited through inheritance of classes, and are resolved dynamically at runtime like instance methods. (see also: Smalltalk).
<syntaxhighlight lang="swift">// Class
MyClass.method(someParameter)
// or equivalently:
let foo = MyClass.self
foo.method(someParameter)

// Instance
myInstance.method(someParameter)

// Method with multiple arguments
myInstance.method(red:arg1, green:arg2, blue:arg3)</syntaxhighlight>
=={{header|Tcl}}==
<syntaxhighlight lang="tcl">package require Tcl 8.6
# "Static" (on class object)
MyClass mthd someParameter

# Instance
$myInstance mthd someParameter</syntaxhighlight>
=={{header|TXR}}==

TXR Lisp method invocation syntax is <code>obj.(method args...)</code>.

Static methods are just functions that don't take an object as an argument. The above notation, therefore, normally isn't used, rather the functional square brackets: <code>[obj.function args...]</code>.

The <code>defstruct</code> clause <code>:method</code> is equivalent to <code>:function</code> except that it requires at least one argument, the leftmost one denoting the object.

The <code>obj.(method args...)</code> could be used to call a static function; it would pass <code>obj</code> as the leftmost argument. Vice versa, the square bracket call notation can be used to invoke a method; the object has to be manually inserted: <code>[obj.function obj args...]</code>.

<syntaxhighlight lang="txrlisp">(defvarl thing-count 0)

(defstruct thing ()
  (call-count 0)

  (:init (me)
    (inc thing-count))
  (:function get-thing-count () thing-count)
  (:method get-call-count (me) (inc me.call-count)))

(let ((t1 (new thing))
      (t2 (new thing)))
  (prinl t1.(get-call-count)) ;; prints 1
  (prinl t1.(get-call-count)) ;; prints 2
  (prinl t1.(get-call-count)) ;; prints 3
  (prinl t2.(get-call-count)) ;; prints 1
  (prinl t2.(get-call-count)) ;; prints 2
  (prinl t2.(get-call-count)) ;; prints 3
  
  (prinl [t1.get-thing-count])  ;; prints 2
  (prinl [t2.get-thing-count])) ;; prints 2</syntaxhighlight>

{{out}}
<pre>1
2
3
1
2
3
2
2</pre>

=={{header|Ursa}}==
<syntaxhighlight lang="ursa"># create an instance of the built-in file class
decl file f

# call the file.open method
f.open "filename.txt"</syntaxhighlight>

=={{header|VBA}}==
First we have to create a class module named "myObject" :
<syntaxhighlight lang="vb">
Option Explicit

Sub Method_1(Optional myStr As String)
Dim strTemp As String
    If myStr <> "" Then strTemp = myStr
    Debug.Print strTemp
End Sub

Static Sub Method_2(Optional myStr As String)
Dim strTemp As String
    If myStr <> "" Then strTemp = myStr
    Debug.Print strTemp
End Sub</syntaxhighlight>
In a "standard" Module, the call should be :
<syntaxhighlight lang="vb">Option Explicit

Sub test()
Dim Obj As New myObject
    Obj.Method_1 "Hello to you"
    Obj.Method_2 "What is your name ?"
    Obj.Method_1
    Obj.Method_2
End Sub</syntaxhighlight>
{{out}}
<pre>Hello to you
What is your name ?

What is your name ?</pre>

=={{header|V (Vlang)}}==
Vlang uses objects without classes (sometimes known as class-free or classless):  

1) Structs can have methods assigned to them or be embedded in other structs.

2) Vlang also uses modules.  Functions and structs can be exported from a module, which works somewhat similar to the class method.

<syntaxhighlight lang="Zig">
// Assigning methods to structs
struct HelloWorld {}

// Method's in Vlang are functions with special receiver arguments at the front (between fn and method name)
fn (sh HelloWorld) say_hello() {
	 println("Hello, world!")
}

fn (sb HelloWorld) say_bye() {
	 println("Goodbye, world!")
}

fn main() {

	//  instantiate object
	hw := HelloWorld{}
	
	// call methods of object
	hw.say_hello()
	hw.say_bye()
}
</syntaxhighlight>

{{out}}
<pre>
Hello, world!
Goodbye, world!
</pre>

Exporting functions from modules:

Create a module:
<syntaxhighlight lang="Zig">
// myfile.v
module mymodule

// Use "pub" to export a function
pub fn say_hi() {
	println("hello from mymodule!")
}
</syntaxhighlight>

Import and use the module's function in your code:
<syntaxhighlight lang="Zig">
import mymodule

fn main() {
	mymodule.say_hi()
}
</syntaxhighlight>

{{out}}
<pre>
hello from mymodule!
</pre>

=={{header|Wren}}==
Note that it's possible in Wren for instance and static methods in the same class to share the same name. This is because static methods are considered to belong to a separate meta-class.
<syntaxhighlight lang="wren>class MyClass {
    construct new() {}
    method() { System.print("instance method called") }
    static method() { System.print("static method called") }
}

var mc = MyClass.new()
mc.method()
MyClass.method()</syntaxhighlight>

{{out}}
<pre>
instance method called
static method called
</pre>

=={{header|XBS}}==
You can call object methods using two types of structures. Classes and Objects.
===Classes===
<syntaxhighlight lang="xbs">class MyClass {
	construct=func(self,Props){
		self:Props=Props;
	}{Props={}}
	GetProp=func(self,Name){
		send self.Props[Name];
	}
}

set Class = new MyClass with [{Name="MyClass Name"}];
log(Class::GetProp("Name"));</syntaxhighlight>
{{out}}
<pre>
MyClass Name
</pre>
===Objects===
<syntaxhighlight lang="xbs">set MyObj = {
	a=10;
	AddA=func(self,x){
		send self.a+x;
	};
}

log(MyObj::AddA(2));</syntaxhighlight>
{{out}}
<pre>
12
</pre>
=={{header|XLISP}}==
Class methods and instance methods are defined using <tt>DEFINE-CLASS-METHOD</tt> and <tt>DEFINE-METHOD</tt> respectively. They are called by sending a message to the class or to an instance of it: the message consists of (<i>a</i>) the name of the object that will receive it, which may be a class; (<i>b</i>) the name of the method, as a quoted symbol; and (<i>c</i>) the parameters if any.
<syntaxhighlight lang="xlisp">(DEFINE-CLASS MY-CLASS)

(DEFINE-CLASS-METHOD (MY-CLASS 'DO-SOMETHING-WITH SOME-PARAMETER)
    (DISPLAY "I am the class -- ")
    (DISPLAY SELF)
    (NEWLINE)
    (DISPLAY "You sent me the parameter ")
    (DISPLAY SOME-PARAMETER)
    (NEWLINE))

(DEFINE-METHOD (MY-CLASS 'DO-SOMETHING-WITH SOME-PARAMETER)
    (DISPLAY "I am an instance of the class --  ")
    (DISPLAY SELF)
    (NEWLINE)
    (DISPLAY "You sent me the parameter ")
    (DISPLAY SOME-PARAMETER)
    (NEWLINE))

(MY-CLASS 'DO-SOMETHING-WITH 'FOO)

(DEFINE MY-INSTANCE (MY-CLASS 'NEW))

(MY-INSTANCE 'DO-SOMETHING-WITH 'BAR)</syntaxhighlight>
{{out}}
<pre>I am the class -- #<Class:MY-CLASS #x38994c8>
You sent me the parameter FOO
I am an instance of the class --  #<Object:MY-CLASS #x39979d0>
You sent me the parameter BAR</pre>
=={{header|Zig}}==
Zig does not have classes nor objects. Zig's structs, however, can have methods; but they are not special. They are only namespaced functions that can be called with dot syntax.

<syntaxhighlight lang="zig">const testing = @import("std").testing;

pub const ID = struct {
    name: []const u8,
    age: u7,

    const Self = @This();

    pub fn init(name: []const u8, age: u7) Self {
        return Self{
            .name = name,
            .age = age,
        };
    }

    pub fn getAge(self: Self) u7 {
        return self.age;
    }
};

test "call an object method" {
    // Declare an instance of a struct by using a struct method.
    const person1 = ID.init("Alice", 18);

    // Or by declaring it manually.
    const person2 = ID{
        .name = "Bob",
        .age = 20,
    };

    // test getAge() method call
    try testing.expectEqual(@as(u7, 18), person1.getAge());
    try testing.expectEqual(@as(u7, 20), ID.getAge(person2));
}</syntaxhighlight>

=={{header|zkl}}==
In zkl, a class can be static (there will only exist one instance of the class). A function is always a member of some class but will only be static if it does not refer to instance data.
<syntaxhighlight lang="zkl">class C{var v; fcn f{v}}
C.f() // call function f in class C
C.v=5; c2:=C();    // create new instance of C
println(C.f()," ",c2.f()) //-->5 Void
C.f.isStatic //--> False

class [static] D{var v=123; fcn f{v}}
D.f(); D().f(); // both return 123
D.f.isStatic //-->False

class E{var v; fcn f{}} E.f.isStatic //-->True</syntaxhighlight>

<!-- Same omits as Classes page -->
{{omit from|360 Assembly}}
{{omit from|6502 Assembly}}
{{omit from|8051 Assembly}}
{{omit from|8080 Assembly}}
{{omit from|8086 Assembly}}
{{omit from|68000 Assembly}}
{{omit from|AArch64 Assembly}}
{{omit from|ARM Assembly}}
{{omit from|AWK|not OO}}
{{omit from|BASIC|not OO}}
{{omit from|bc}}
{{omit from|dc}}
{{omit from|GUISS}}
{{omit from|Locomotive Basic}}
{{omit from|M4}}
{{omit from|Mathematica|Cannot create basic classes}}
{{omit from|Maxima}}
{{omit from|Metafont}}
{{omit from|MIPS Assembly}}
{{omit from|Octave}}
{{omit from|PARI/GP}}
{{omit from|Plain English|Plain English does not support objects.}}
{{omit from|Retro}}
{{omit from|REXX|not OO}}
{{omit from|Standard ML}}
{{omit from|TI-83 BASIC|not OO}}
{{omit from|TI-89 BASIC|Does not have user-defined types/classes}}
{{omit from|UNIX Shell}}
{{omit from|Vim Script}}
{{omit from|x86 Assembly}}
{{omit from|Z80 Assembly}}
{{omit from|ZX Spectrum Basic|not OO}}