[
https://issues.apache.org/jira/browse/MATH-859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13598535#comment-13598535
]
Phil Steitz commented on MATH-859:
----------------------------------
Personally, I think it is better to put fix version at the release that will
actually resolve the issue by removing the methods, as it is in this case (fix
version 4.0). When we decide to remove or refactor something, I think it is
best to keep the issue open until it is fully resolved, which to me means
deprecated methods have been removed. This helps us remember to actually do it
when we cut the major release and jogs memory when prepping that release what
exactly we had in mind / why methods were deprecated.
> Fix and then deprecate isSupportXxxInclusive in RealDistribution interface
> --------------------------------------------------------------------------
>
> Key: MATH-859
> URL: https://issues.apache.org/jira/browse/MATH-859
> Project: Commons Math
> Issue Type: Bug
> Affects Versions: 3.0
> Reporter: Phil Steitz
> Fix For: 4.0
>
>
> The conclusion from [1] was never implemented. We should deprecate these
> properties from the RealDistribution interface, but since removal
> will have to wait until 4.0, we should agree on a precise
> definition and fix the code to match it in the mean time.
> The definition that I propose is that isSupportXxxInclusive means
> that when the density function is applied to the upper or lower
> bound of support returned by getSupportXxxBound, a finite (i.e. not
> infinite), not NaN value is returned.
> [1] http://markmail.org/message/dxuxh7eybl7xejde
--
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
