You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Sebb (JIRA)" <ji...@apache.org> on 2011/01/17 20:53:43 UTC

[jira] Created: (MATH-482) FastMath.max(50.0f, -50.0f) => -50.0f; should be +50.0f

FastMath.max(50.0f, -50.0f) => -50.0f; should be +50.0f
-------------------------------------------------------

                 Key: MATH-482
                 URL: https://issues.apache.org/jira/browse/MATH-482
             Project: Commons Math
          Issue Type: Bug
            Reporter: Sebb
            Assignee: Sebb


FastMath.max(50.0f, -50.0f) => -50.0f; should be +50.0f.

This is because the wrong variable is returned.

The bug was not detected by the test case "testMinMaxFloat()" because that has a bug too - it tests doubles, not floats.

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


[jira] Updated: (MATH-482) FastMath.max(50.0f, -50.0f) => -50.0f; should be +50.0f

Posted by "Sebb (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/MATH-482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sebb updated MATH-482:
----------------------

    Affects Version/s: 3.0
                       2.2

> FastMath.max(50.0f, -50.0f) => -50.0f; should be +50.0f
> -------------------------------------------------------
>
>                 Key: MATH-482
>                 URL: https://issues.apache.org/jira/browse/MATH-482
>             Project: Commons Math
>          Issue Type: Bug
>    Affects Versions: 2.2, 3.0
>            Reporter: Sebb
>            Assignee: Sebb
>             Fix For: 2.2, 3.0
>
>
> FastMath.max(50.0f, -50.0f) => -50.0f; should be +50.0f.
> This is because the wrong variable is returned.
> The bug was not detected by the test case "testMinMaxFloat()" because that has a bug too - it tests doubles, not floats.

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


[jira] [Closed] (MATH-482) FastMath.max(50.0f, -50.0f) => -50.0f; should be +50.0f

Posted by "Luc Maisonobe (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/MATH-482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luc Maisonobe closed MATH-482.
------------------------------


Closing issue as it was included in version 2.2, which has been released

> FastMath.max(50.0f, -50.0f) => -50.0f; should be +50.0f
> -------------------------------------------------------
>
>                 Key: MATH-482
>                 URL: https://issues.apache.org/jira/browse/MATH-482
>             Project: Commons Math
>          Issue Type: Bug
>    Affects Versions: 2.2, 3.0
>            Reporter: Sebb
>            Assignee: Sebb
>             Fix For: 2.2, 3.0
>
>
> FastMath.max(50.0f, -50.0f) => -50.0f; should be +50.0f.
> This is because the wrong variable is returned.
> The bug was not detected by the test case "testMinMaxFloat()" because that has a bug too - it tests doubles, not floats.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Resolved: (MATH-482) FastMath.max(50.0f, -50.0f) => -50.0f; should be +50.0f

Posted by "Sebb (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/MATH-482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sebb resolved MATH-482.
-----------------------

       Resolution: Fixed
    Fix Version/s: 3.0
                   2.2

> FastMath.max(50.0f, -50.0f) => -50.0f; should be +50.0f
> -------------------------------------------------------
>
>                 Key: MATH-482
>                 URL: https://issues.apache.org/jira/browse/MATH-482
>             Project: Commons Math
>          Issue Type: Bug
>            Reporter: Sebb
>            Assignee: Sebb
>             Fix For: 2.2, 3.0
>
>
> FastMath.max(50.0f, -50.0f) => -50.0f; should be +50.0f.
> This is because the wrong variable is returned.
> The bug was not detected by the test case "testMinMaxFloat()" because that has a bug too - it tests doubles, not floats.

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