commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oliver Heger (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CONFIGURATION-485) Class fields set by ctors should be final if they don't need to be changed later
Date Thu, 24 Mar 2016 20:13:26 GMT

     [ https://issues.apache.org/jira/browse/CONFIGURATION-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Oliver Heger updated CONFIGURATION-485:
---------------------------------------
    Fix Version/s:     (was: 2.0)
                   2.x

> Class fields set by ctors should be final if they don't need to be changed later
> --------------------------------------------------------------------------------
>
>                 Key: CONFIGURATION-485
>                 URL: https://issues.apache.org/jira/browse/CONFIGURATION-485
>             Project: Commons Configuration
>          Issue Type: Improvement
>            Reporter: Sebb
>             Fix For: 2.x
>
>         Attachments: CONFIGURATION-485-2.patch, CONFIGURATION-485-3.patch, CONFIGURATION-485.patch
>
>
> Using final whereever possible simplifies testing (fewer possible states) and improves
thread-safety (final fields may not need synch.)
> Obviously changing public or protected fields to final may cause problems for binary
compatibility (if they form part of the public API), but for private/package variables that
is not a concern.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message