Edit - Software Engineering Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

Rev

3

I think you misunderstand final. If it was public yet constant, it wouldn't make sense for it to be able to declare a final within the scope of a method. It is not about performance (though that can be a nice side effect) but rather conveying the intent of the code clearly to the next programmer who has to read it - "This value is set once and only once here" and be able to guarantee that contract throughout the scope of the variable.

user40980
– user40980

2013-05-30 01:37:24 +00:00
Commented May 30, 2013 at 1:37
And some links for that opinion - SO Is it a good practice to declare variables “final” wherever possible?, Why My Variables Are Final, and Use final liberally

user40980
– user40980

2013-05-30 01:41:18 +00:00
Commented May 30, 2013 at 1:41

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »