When should we make our methods static ?

Question

3.50/5 (2 votes)

See more:

when something should be implemented by a class with static operations and when by one or more objects from the same class

Posted 21-Mar-10 16:26pm

medoded2009

Updated 29-Mar-10 12:52pm

v3

Add a Solution

4 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

KenJohnson · Accepted Answer · 2010-03-28T19:54:00

The following are a bunch of the facts about static methods.

Static methods cannot be in interfaces, which can be a big deal.

They also cannot be abstract or virtual.

A static Class can only have static methods.

Static methods are faster though I have found the difference hard to measure.

Static constructors are called before regular constructors, which can be quite useful.

All extension Methods are static . They are very nice in that they let you add methods to classes that you have little control over. In particular you can add them to an enum which normally gets no methods at all. Note that you can do this to the class itself, without inheritance.

They are used in the creation of Dependency properties. DependencyProperty.Register is a good one.

My advice is as follows. When the above considerations make sense you are ready to start using static methods. Until then there are probably other more pressing issues.

Ps: To me the more interesting question is how one can best leverage static variables and collections, but that was not the question asked.

radix3 · Accepted Answer · 2010-03-29T03:17:00

use static keyword where u want to call a method directly without using the instance of the class,

the keyword static is used to make fields & methods which belong to the class rather than to its instance

example

C#

class B
{
static void fun()
{
System.out.println("Hello");
}
public static void main(String args [])
{
fun();
}
}

Thanks & Regards
Radix :rose:

Christian Graus · Accepted Answer · 2010-03-28T12:19:00

Solution 3

Well, any method that you may want to call where you don't have an object handy, and which has no state, should be static. If it can be static, then consider making it static.

Posted 28-Mar-10 12:19pm

Christian Graus

DaveyM69 · Accepted Answer · 2010-03-28T16:46:00

Solution 4

When the method is directly related to a class but doesn't act on an instance of it (aside from creating a new instance of it).

Posted 28-Mar-10 16:46pm

DaveyM69

When should we make our methods static ?

4 solutions

Solution 5

Solution 6

Solution 3

Solution 4

Add your solution here

Preview 0