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] Resolved: (BSF-17) Unnamed block in BSF_Log should be static?
Date Wed, 21 May 2008 22:49:55 GMT

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

Sebb resolved BSF-17.
---------------------

    Resolution: Fixed

Updated SVN trunk:

commit -m "BSF-17 - convert unnamed block to static initialiser; make all fields final so
class is now immutable" 
Committed revision 658912.


> Unnamed block in BSF_Log should be static?
> ------------------------------------------
>
>                 Key: BSF-17
>                 URL: https://issues.apache.org/jira/browse/BSF-17
>             Project: BSF
>          Issue Type: Bug
>            Reporter: Sebb
>
> There is an unnamed block in BSF_Log (starting at line 70) which looks as though it ought
to be a static block.
> If not, it should be given a name and/or be commented.
> If it is supposed to be a static block, then it would be sensible to make the static
fields final as far as possible.

-- 
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


Mime
View raw message