jakarta-bsf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <j...@apache.org>
Subject [jira] Commented: (BSF-14) BSFManager should use final fields where possible
Date Wed, 21 May 2008 09:55:55 GMT

    [ https://issues.apache.org/jira/browse/BSF-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12598609#action_12598609

Sebb commented on BSF-14:

Although API compatibilty is important in BSF, I don't think it's as important as in say a
Commons Library.

I would expect most users to just use the public methods, and probably never extend any of
its classes.

There is another reason for using final, and that is memory visibility across threads.

> BSFManager should use final fields where possible
> -------------------------------------------------
>                 Key: BSF-14
>                 URL: https://issues.apache.org/jira/browse/BSF-14
>             Project: BSF
>          Issue Type: Bug
>    Affects Versions: BSF-2.4
>            Reporter: Sebb
>            Priority: Minor
> BSFManager should use final fields where possible to avoid inadvertent changes.
> For example, version should be final. Likewise the HashTables.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail: bsf-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: bsf-dev-help@jakarta.apache.org

View raw message