Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Comments on What are the disadvantages of using static methods in Java?

Parent

What are the disadvantages of using static methods in Java?

+2
−5

I was using static method few moments ago. But I noticed that I was returning a variable using that static method. According to the article,

Static is a keyword that identifies the class-related thing. It means the given Method or variable is not instance-related but Class related. It can be accessed without creating the instance of a Class.

I think I can access the static method without caring of class, isn't it? Is there something special of static method? static method can helps to decrease amount of source code. So Is it better to use static method? Or is there any limit of it?

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

I have changed the title to what I think is better summarising the content. Feel free to change somet... (2 comments)
Post
+3
−0

I think I can access the static method without caring of class, isn't it?

No. A static method is still a class method, and you still care about the class. The difference is that static methods aren't used with an instance of a class (an object).

static method can helps to decrease amount of source code.

True. As you pointed out in comment (putting it here too for better visibility): import static com.classes.Car.numCars(); means that you can simply invoke it as numCars();

So Is it better to use static method? Or is there any limit of it?

Opinions differ. The main thing is that you can't access object members in a static method, only static members.

For example, you might have a Car class, with a fuel member and a drive() method that makes fuel go down. You might also have a private static int numCars member, and a static printNumCars() method.

When accessing your static method, you still care about the class. It's still going to be Car.numCars(). numCars() has no way to access the fuel member, and that makes sense (which car's fuel would we be talking about?). On the other hand, "how many cars are there" isn't a property of any one specific car at all, it's a property of cars in general, as a whole category.

That's what static members are for - things that are relevant to the entire class, rather than any individual object.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

1 comment thread

decrease amount of source code (3 comments)
decrease amount of source code
Anonymous‭ wrote about 3 years ago · edited about 3 years ago

I don't see how...

Actually, it decreases I am not against your example. But we can call numCars() without adding Car before it. That moment you just have to add import static at top

import static com.classes.Car.numCars();
Hyperlynx‭ wrote about 3 years ago

Oh, right, that. True.

hkotsubo‭ wrote about 3 years ago · edited about 3 years ago

Anonymous‭ Less code != better. Just because you typed less characters, it doesn't necessarily mean it's "better" (BTW, most IDE's can autocomplete the imports for you, which makes this point even more irrelevant, IMO). What you should seek is clear, concise, semantic and correct code, regardless of its size (and if size is an issue, you can always refactor it later). The more important stuff of static vs non-static are those pointed in the answers, and code size isn't one of them.