Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Message-ID: <31317771.519651286124213030.JavaMail.jira@thor>
Date: Sun, 3 Oct 2010 12:43:33 -0400 (EDT)
From: "Luc Maisonobe (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Subject: [jira] Resolved: (MATH-391) Inconsistent behaviour of constructors
 in ArrayRealVector class
In-Reply-To: <9625374.493091279702730362.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-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luc Maisonobe resolved MATH-391.
--------------------------------

    Resolution: Fixed

Fixed in subversion repository as of r1003993 for barnch 2.X and r1003994 for trunk.
Note that the same problem occurred also in ArrayFieldVector but the fix is different. For Field-based vectors, we need to get the field, so either we use a non-empty array and retrieve the field from the first array element or we add a parameter for the field and allow the array to be empty. The two choices are now possible, as new constructors have been added and the javadoc updated to explain this behavior.
Thanks for reporting the issue.

> Inconsistent behaviour of constructors in ArrayRealVector class
> ---------------------------------------------------------------
>
>                 Key: MATH-391
>                 URL: https://issues.apache.org/jira/browse/MATH-391
>             Project: Commons Math
>          Issue Type: Bug
>    Affects Versions: 2.1
>            Reporter: Roman Werpachowski
>             Fix For: 2.2
>
>
> ArrayRealVector(double[] d) allows to construct a zero-length vector, but ArrayRealVector(double[] d, boolean copyArray) doesn't. Both should allow this as zero-length vectors are mathematically well-defined objects and they are useful boundary cases in many algorithms.
> This breaks some arithmetic operators (addition) on zero-length real vectors which worked in 2.0 but don't work in 2.1

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