Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Message-ID: <10692161.178361281007096337.JavaMail.jira@thor>
Date: Thu, 5 Aug 2010 07:18:16 -0400 (EDT)
From: "Phil Steitz (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Subject: [jira] Commented: (MATH-401) Policy concerning "null"
In-Reply-To: <25865696.178031281003796650.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/MATH-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12895647#action_12895647 ] 

Phil Steitz commented on MATH-401:
----------------------------------

Yes, these messages exist now and I would like to keep them.

> Policy concerning "null"
> ------------------------
>
>                 Key: MATH-401
>                 URL: https://issues.apache.org/jira/browse/MATH-401
>             Project: Commons Math
>          Issue Type: Improvement
>            Reporter: Gilles
>            Assignee: Gilles
>            Priority: Trivial
>             Fix For: 3.0
>
>
> Following the discussion on the "dev" ML, it appears that it would be fine to not check for {{null}} references within CM. The JVM will do it anyway so that it is redundant and not necessary most of the time (i.e. when usage is valid). When it happens, the problem is obvious enough that the standard {{NullPointerException}} fully describes it, without the need for additional specific and localized detailed messages.
> Hence we could remove all explicit checks for {{null}}. Or when early failure is preferred, make the check and throw {{NullPointerException}} (without a message argument).
> Since failed checks are currently reported with an {{IllegalArgumentException}}, the change is not backward-compatible.

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