Call an object method: Difference between revisions

 

=={{header|ActionScript}}==

MyClass.method(someParameter);

 

// Instance

 

=={{header|Ada}}==

 

Specify the class My_Class, with one primitive subprogram, one dynamic subprogram and a static subprogram:

type Object is tagged private;

procedure Primitive(Self: Object); -- primitive subprogram

private

type Object is tagged null record;

 

Implement the package:

procedure Primitive(Self: Object) is

begin

Put_Line("Greetings");

end Static;

 

Specify and implement a subclass of My_Class:

type Object is new My_Class.Object with null record;

overriding procedure Primitive(Self: Object);

Put_Line("Hello Universe!");

end Primitive;

 

The main program, making the dynamic and static calls:

 

 

procedure Call_Method is

Ob1.Dynamic;

Ob2.Dynamic;

 

{{out}}

 

=={{header|Apex}}==

MyClass.method(someParameter);

 

// Instance

 

=={{header|AutoHotkey}}==

{{works with|AutoHotkey_L}}

(AutoHotkey Basic does not have classes)

{

Method(someParameter){

myClass.method("hi")

myInstance := new myClass

 

=={{header|Bracmat}}==

 

Inside an object, the object is represented by <code>its</code>, comparable to <code>this</code> in other languages.

= (name=aClass)

( Method

& !MyObject:?Alias

& (Alias..Method)$"Example of calling an instance method from an alias"

Output:

<pre>Output from aClass: Example of calling a 'class' method

=={{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.

#include<stdlib.h>

#include<stdio.h>

return 0;

}

And yes, it works :

<pre>

 

=={{header|C++}}==

MyClass::method(someParameter);

 

// Pointer

MyPointer->method(someParameter);

 

=={{header|C_sharp|C#}}==

MyClass.Method(someParameter);

// Instance

 

=={{header|ChucK}}==

MyClass myClassObject;

myClassObject.myFunction(some parameter);

 

=={{header|Clojure}}==

(System/currentTimeMillis)

 

(.equals 1 2) ; use dot operator to call instance methods

 

=={{header|COBOL}}==

COBOL has two ways to invoke a method: the <code>INVOKE</code> statement and inline method invocation.

INVOKE FooClass "someMethod" RETURNING bar *> Factory object

INVOKE foo-instance "anotherMethod" RETURNING bar *> Instance object

*> Inline method invocation

MOVE FooClass::"someMethod" TO bar *> Factory object

 

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.

*> foo-factory can be treated like a normal object reference.

 

=={{header|CoffeeScript}}==

While CoffeeScript does provide a useful class abstraction around its prototype-based inheritance, there aren't any actual classes.

@staticMethod: -> 'Bar'

 

 

foo.instanceMethod() #=> 'Baz'

 

=={{header|Common Lisp}}==

In Common Lisp, classmethods are methods that apply to classes, rather than classes that contain methods.

((x

:accessor get-x ;; getter function

 

(format t "Value of x^2: ~a~%" (square-x *instance*))

Output (CLISP v2.49):

<pre>$ clisp object.cl

 

=={{header|D}}==

static int staticMethod() {

return 2;

d = new Dog;

assert(d.dynamicMethod() == "Woof!");

 

=={{header|Dragon}}==

Making an object of class and then calling it.

 

=={{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.

 

static func Integer.Div(x, y) {

x / y

print(Integer.Div(12, 3))

 

{{out}}

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.

 

 

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|Elena}}==

The message call:

console.printLine("Hello"," ","World!");

 

=={{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.

defmodule ObjectCall do

def new() do

 

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

 

=={{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.

 

IN: rosetta-code.call-a-method

 

0.75 <cat> speak

0.1 <cat> speak

{{out}}

<pre>

{{trans|D}}

There are numerous, mutually incompatible object oriented frameworks for Forth. This one works with the FOOS preprocessor extension of [[4tH]].

include 4pp/lib/foos.4pp

 

; \ same for dynamic methods

 

 

Works with any ANS Forth

Needs the FMS-SI (single inheritance) library code located here:

http://soton.mpeforth.com/flag/fms/index.html

 

:class animal

Frisky speak \ => meow ok

Sparky speak \ => woof ok

 

=={{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.

! type declaration

type my_type

mytype_object%method2() ! call method2 defined as function

 

 

=={{header|FreeBASIC}}==

' FB 1.05.0 Win64

 

Print "Press any key to quit the program"

Sleep

 

{{out}}

=={{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.

 

// method on the type itself; can be called on that type or its pointer

Foo.ValueMethod(myValue, someParameter)

(*Foo).PointerMethod(myPointer, someParameter)

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:

 

import "sync/atomic"

func Count() uint32 {

return atomic.LoadUint32(&sn)

Example use:

 

import "box"

// Call class method. In Go terms, another exported function.

box.Count()

 

==Icon and {{header|Unicon}}==

 

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.

 

bar := foo() # create instance

initially

L := [cp1]

 

=={{header|Haskell}}==

 

Dummy example:

 

-- smart constructor

-- adding method from a type class

instanse Show Obj where

 

<pre>*Main> let o1 = Obj 1 (*5)

Static:

 

 

and, given an object instance reference:

 

 

an instance invocation could be:

 

 

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.

 

or

 

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:

 

 

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

 

 

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:

Instance methods are called by using the dot operator on an instance:

varName.methodName(argument1, argument2);

//or

 

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-->

=={{header|JavaScript}}==

If you have a object called <tt>x</tt> and a method called <tt>y</tt> then you can write:

 

=={{header|Julia}}==

=={{header|Kotlin}}==

Kotlin does not have static methods as such but they can be easily simulated by 'companion object' methods :

fun instanceMethod(s: String) = println(s)

 

mc.instanceMethod("Hello instance world!")

MyClass.staticMethod("Hello static world!")

 

{{out}}

 

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.

The parentheses on the argument list may be omitted if there is at most one argument and the parse is unambiguous.

myObject someMethod (argument). ;; Parentheses are necessary here

Finally, a colon may be used instead of parentheses, in which case the rest of the line is considered to be the argument list.

 

=={{header|LFE}}==

 

===With Closures===

(export all))

 

(defun get-children-count (object)

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

 

With this done, one can create objects and interact with them. Here is some usage from the LFE REPL:

 

> (slurp '"object.lfe")

children: ["fdcf35983bb496650e558a82e34c9935",

"3e64e5c20fb742dd88dac1032749c2fd"]

 

===With Lightweight Processes===

(export all))

 

 

(defun get-children-count (object)

 

Here is some usage from the LFE REPL:

 

> (slurp '"object.lfe")

children: ["fdcf35983bb496650e558a82e34c9935",

"3e64e5c20fb742dd88dac1032749c2fd"]

 

=={{header|Lingo}}==

script("MyClass").foo()

 

-- call instance method

obj = script("MyClass").new()

 

=={{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.

% avoid infinite metaclass regression by

% making the metaclass an instance of itself

:- end_object.

:- object(class,

instantiates(metaclass)).

:- end_object.

:- object(instance,

instantiates(class)).

 

:- end_object.

Testing:

| ?- class::me(Me).

Me = class

Class = class

yes

 

=={{header|Lua}}==

 

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:

 

object:func() -- with : sugar

 

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:

function methods:func () -- if a function is declared using :, it is given an implicit 'self' parameter

print(self.name)

 

object:func() -- with : sugar

 

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>:

local box = { }

local boxmt = { __index = box }

return count

end

 

Example use:

 

local b = box.new()

 

print(b:tellSecret())

 

=={{header|M2000 Interpreter}}==

In M2000 there are some kinds of objects. Group is the one type 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

Module CheckIt {

\\ A class definition is a function which return a Group

}

Checkit

 

=={{header|Maple}}==

There is no real difference in how you call a static or instance method.

 

=={{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.

Dog.name = ""

Dog.help = function()

 

Dog.help // calling a "class method"

 

{{out}}

 

=={{header|Nanoquery}}==

declare static id = 5

declare MyName

// and call the class method

myclass = new(MyClass, "test")

{{out}}

<pre>5

 

=={{header|Nemerle}}==

MyClass.Method(someParameter);

// Instance

 

=={{header|NetRexx}}==

Like [[#Java|Java]], static methods in NetRexx are called by using the dot operator on a class name:

Instance methods are called by using the dot operator on an instance:

objectInstance.instanceMethod() -- call the instance method

 

 

=={{header|Nim}}==

In Nim there are no object methods, but regular procedures can be called with method call syntax:

add(x, 4)

 

=={{header|OASYS Assembler}}==

 

The following code calls a method called <tt>&amp;GO</tt> on the current object:

 

=={{header|Objeck}}==

ClassName->some_function(); # call class function

Objeck uses the same syntax for instance and class method calls. In Objeck, functions are the equivalent of public static methods.

 

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.

 

MyClass.method(someParameter);

 

// Instance

myInstance.method(someParameter);

 

=={{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).

[MyClass method:someParameter];

// or equivalently:

 

// Method with no arguments

 

=={{header|OCaml}}==

We can only call the method of an instantiated object:

 

 

=={{header|Oforth}}==

When a method is called, the top of the stack is used as the object on which the method will be applyed :

 

For class methods, the top of the stack must be a class (which is also an object of Class class) :

 

=={{header|ooRexx}}==

c=.circle~new(1)

say "c~area:" c~area

Say self~class

Say self

'''Output:'''

<pre>pi: 3.14159265358979323

 

=={{header|Perl}}==

MyClass->classMethod($someParameter);

# Equivalently using a class name

# the package and calling it on the class name or object reference explicitly

MyClass::classMethod('MyClass', $someParameter);

 

=={{header|Phix}}==

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.

<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: #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>

 

=={{header|PHP}}==

MyClass::method($someParameter);

// In PHP 5.3+, static method can be called on a string of the class name

 

// Instance method

 

=={{header|PicoLisp}}==

Method invocation is syntactically equivalent to normal function calls. Method names have a trailing '>' by convention.

 

=={{header|Pike}}==

 

regular methods can be called in these ways:

obj["method"]();

call_function(obj->method);

<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:

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:

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}}==

-- A class needs at least one member even though we don't use it

dummy NUMBER,

DBMS_OUTPUT.put_line( myClass.static_method() );

DBMS_OUTPUT.put_line( myInstance.instance_method() );

 

=={{header|PowerShell}}==

$Date.AddDays( 1 )

 

=={{header|Processing}}==

class HelloWorld

{

 

// and call the instance method

 

=={{header|Python}}==

@classmethod

def myClassMethod(self, x):

# You can also call class or static methods on an instance, which will simply call it on the instance's class

myInstance.myClassMethod(someParameter)

 

=={{header|Quackery}}==

(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.)

 

[ immovable

say "Current value of mycounter: "

 

{{out}}

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

 

 

(define timer (new timer%))

 

=={{header|Raku}}==

{{works with|Rakudo|2015.12}}

=== Basic method calls ===

method regular-example() { say 'I haz a method' }

 

my $foo = new Thing: ;

multi-example $thing: 42;

 

=== Meta-operators ===

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

 

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

 

=== Classless methods ===

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

 

my $object = "a string"; # Everything is an object.

my method example-method {

 

say $object.&example-method; # Outputs "This is a string."

 

=={{header|Ring}}==

new point { print() }

Class Point

x = 10 y = 20 z = 30

func print see x + nl + y + nl + z + nl

o1 = new System.output.console

o1.print("Hello World")

Func Print cText

see cText + nl

 

=={{header|Ruby}}==

MyClass.some_method(some_parameter)

 

 

# Calling a method with no parameters

 

=={{header|Rust}}==

 

impl Foo {

let lots_of_references = &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&foo;

println!("The answer to life is still {}." lots_of_references.get_the_answer_to_life());

 

=={{header|Scala}}==

* creates "val variable1: Int" with that value.

*/

assert(n.memberVal == 3)

println("Successfully completed without error.")

 

=={{header|Sidef}}==

method foo(arg) { say arg }

}

 

# Alternatively, by asking for a method

 

=={{header|Smalltalk}}==

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)

 

MyClass selector: someArgument .

" or equivalently "

 

" Binary (operator) message"

 

 

Example for dynamic class determination:

 

Message names (selectors) can be chosen or constructed dynamically at runtime. For example:

 

or:

 

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).

foo perform: theMessage

] on: MessageNotUnderstood do:[

Dialog information: 'sorry'

 

=={{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.

SomeClass {

a = SomeClass.new;

a.someInstanceMethod;

 

=={{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).

MyClass.method(someParameter)

// or equivalently:

 

// Method with multiple arguments

 

=={{header|Tcl}}==

# "Static" (on class object)

MyClass mthd someParameter

 

# Instance

 

=={{header|Ursa}}==

decl file f

 

# call the file.open method

 

=={{header|VBA}}==

First we have to create a class module named "myObject" :

Option Explicit

 

If myStr <> "" Then strTemp = myStr

Debug.Print strTemp

In a "standard" Module, the call should be :

 

Sub test()

Obj.Method_1

Obj.Method_2

{{out}}

<pre>Hello to you

=={{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.

construct new() {}

method() { System.print("instance method called") }

var mc = MyClass.new()

mc.method()

 

{{out}}

You can call object methods using two types of structures. Classes and Objects.

===Classes===

construct=func(self,Props){

self:Props=Props;

 

set Class = new MyClass with [{Name="MyClass Name"}];

{{out}}

<pre>

</pre>

===Objects===

a=10;

AddA=func(self,x){

}

 

{{out}}

<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.

 

(DEFINE-CLASS-METHOD (MY-CLASS 'DO-SOMETHING-WITH SOME-PARAMETER)

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

 

{{out}}

<pre>I am the class -- #<Class:MY-CLASS #x38994c8>

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.

 

 

pub const ID = struct {

assert(person1.getAge() == 18);

assert(ID.getAge(person2) == 20);

 

=={{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.

C.f() // call function f in class C

C.v=5; c2:=C(); // create new instance of C

D.f.isStatic //-->False

 

 

<!-- Same omits as Classes page -->