The most straightforward way to think about it is to think in terms of what type of object the method needs in order to do its work. If your method needs access to an instance, make it a regular method. If it needs access to the class, make it a classmethod. If it doesn’t need … Read more
This is the correct way public static function userNameAvailibility() { $result = self::getsomthin(); } Use self:: instead of $this-> for static methods. See: PHP Static Methods Tutorial for more info 🙂
The basic paradigm in Java is that you write classes, and that those classes are instantiated. Instantiated objects (an instance of a class) have attributes associated with them (member variables) that affect their behavior; when the instance has its method executed it will refer to these variables. However, all objects of a particular type might … Read more
If you’re looking for a 1 liner that is equivalent to this.GetType() for static methods, try the following. Type t = MethodBase.GetCurrentMethod().DeclaringType Although this is likely much more expensive than just using typeof(TheTypeName).
You don’t need to wait for PHP 5.3 if you’re able to conceive of a way to do this outside of a static context. In php 5.2.9, in a non-static method of the parent class, you can do: get_class($this); and it will return the name of the child class as a string. i.e. class Parent() … Read more
Since getText() is non-static you cannot call it from a static method. To understand why, you have to understand the difference between the two. Instance (non-static) methods work on objects that are of a particular type (the class). These are created with the new like this: SomeClass myObject = new SomeClass(); To call an instance … Read more
Hans Passant’s answer is good. But I thought I would try and explain at a slightly more simple level for anybody who comes across this and is newish to Java. Here goes.. Memory in java is split up into two kinds – the heap and the stacks. The heap is where all the objects live … Read more
See this article for detailed explanation. TL;DR 1.It eliminates the use of self argument. 2.It reduces memory usage because Python doesn’t have to instantiate a bound-method for each object instiantiated: >>>RandomClass().regular_method is RandomClass().regular_method False >>>RandomClass().static_method is RandomClass().static_method True >>>RandomClass.static_method is RandomClass().static_method True 3.It improves code readability, signifying that the method does not depend on state … Read more
There are two kinds of common static methods: A “safe” static method will always give the same output for the same inputs. It modifies no globals and doesn’t call any “unsafe” static methods of any class. Essentially, you are using a limited sort of functional programming — don’t be afraid of these, they’re fine. An … Read more
In theory, a static method should perform slightly better than an instance method, all other things being equal, because of the extra hidden this parameter. In practice, this makes so little difference that it’ll be hidden in the noise of various compiler decisions. (Hence two people could “prove” one better than the other with disagreeing … Read more