Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Message-ID: <1588679332.487751267003107988.JavaMail.jira@brutus.apache.org>
Date: Wed, 24 Feb 2010 09:18:27 +0000 (UTC)
From: "Henri Yandell (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Subject: [jira] Commented: (LANG-370) Document thread safety of classes
In-Reply-To: <17739973.1193766470666.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/LANG-370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12837708#action_12837708 ] 

Henri Yandell commented on LANG-370:
------------------------------------

My general view on this btw is that a class should say if it's not thread safe. Thread safe should be the default - especially in something like Lang.

> Document thread safety of classes
> ---------------------------------
>
>                 Key: LANG-370
>                 URL: https://issues.apache.org/jira/browse/LANG-370
>             Project: Commons Lang
>          Issue Type: Wish
>          Components: General
>            Reporter: Sebb
>             Fix For: 3.0
>
>
> Few if any of the LANG classes state whether they are intended to be thread-safe or not.
> As a library, such documentation is essential IMO.

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