db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6083) Update minimum/maximum floating-point values to align with DERBY-3398 fixes
Date Fri, 22 Feb 2013 02:35:11 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583841#comment-13583841

Dag H. Wanvik commented on DERBY-6083:

Thanks, Kim! No, the precisions are not changed so the FLOAT section is fine as is. +1 to
changing the language on "smallest"; I used the same in the code. Nit: in the table in rrefnumericlimits.dita
the exponents "e" are given with varying case.
As for further changes, I haven't gone through all the manuals to look for occurrences of
the limits, but I imagine you did :)
If so, +1 to the patch!

> Update minimum/maximum floating-point values to align with DERBY-3398 fixes
> ---------------------------------------------------------------------------
>                 Key: DERBY-6083
>                 URL: https://issues.apache.org/jira/browse/DERBY-6083
>             Project: Derby
>          Issue Type: Task
>          Components: Documentation
>    Affects Versions:
>            Reporter: Kim Haase
>            Assignee: Kim Haase
>            Priority: Minor
>         Attachments: DERBY-6083.diff, DERBY-6083.stat, DERBY-6083.zip
> The limits for floating-point values have changed as a result of DERBY-3398 and should
be documented:
> Smallest DOUBLE: 4.9e-324 (aka Double.MIN_VALUE)
> Largest DOUBLE: 1.7976931348623157e+308 (aka Double.MAX_VALUE)
> Smallest positive DOUBLE: 2.2250738585072014E-308 (aka Double.MIN_NORMAL)
> Largest negative DOUBLE: -2.2250738585072014E-308
> Smallest REAL: 1.4e-45 (aka Float.MIN_VALUE)
> Largest REAL: 3.4028235e+38 (aka Float.MAX_VALUE)
> Smallest positive REAL: 1.17549435E-38 (aka Float.MIN_NORMAL)
> Largest negative REAL: -1.17549435E-38 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message