Static x Private: Cost of visibility of values

Question

I was programming and I came across a question, is it more expensive for a system to have a static element? Does a private element generate a gain by being viewable only in its class? This came from thinking that something that was visible to the entire "static" system could be more costly than something internal "Private".

And then, is there any difference even if totally imperceptible?

Edit. When I refer to static I say something "static public" and when I say private it's just "private".

What sort of expense are you talking about? The two aren't interchangeable semantically. — chrylis -cautiouslyoptimistic-, May 28 '18 at 04:45
Expensive call? https://stackoverflow.com/questions/3805155/are-java-static-calls-more-or-less-expensive-than-non-static-calls? — ישו אוהב אותך, May 28 '18 at 04:50

score 1 · Accepted Answer · answered May 28 '18 at 04:50

1

ClassLoader loads all static elements with their owner classes, no problem their instances is created or not. I'm not really got your opinion but by some circumstances, your opinion is right.

answered May 28 '18 at 04:50

Johnny Ngo

104
4

Static x Private: Cost of visibility of values

1 Answers1