<div>
The rules for static fields are exactly the same as for instance fields.<br />
Access restrictions and checking of set-values are just the same!<br />
<br />
;JOOP!
</div>


The rules for static fields are exactly the same as for instance fields.
Access restrictions and checking of set-values are just the same!

;JOOP!

<div>
<div class="content wysiwyg-content">
Dear Experts,<br />
<br />
Is there an &quot;industry standard&quot; for accessing static fields? &nbsp;I normally use private fields with getters and setters now. &nbsp;But in the case of static fields, is it worthwhile to bother? &nbsp;It seems a lot simpler to just do:<br />
<br />
String myString = MyClass.SOME_STATIC_FIELD;<wbr /><br />
<br />
and declare SOME_STATIC_FIELD to be public and final.<br />
<br />
Thanks,<br />
BrianMc1958
</div>
</div>


Dear Experts,

Is there an "industry standard" for accessing static fields?  I normally use private fields with getters and setters now.  But in the case of static fields, is it worthwhile to bother?  It seems a lot simpler to just do:

String myString = MyClass.SOME_STATIC_FIELD;

and declare SOME_STATIC_FIELD to be public and final.

Thanks,
BrianMc1958

Use getters and setters on static fields?

Java is a platform-independent, object-oriented programming language and run-time environment, designed to have as few implementation dependencies as possible such that developers can write one set of code across all platforms using libraries. Most devices will not run Java natively, and require a run-time component to be installed in order to execute a Java program.