commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From (O'brien, Tim)
Subject Re: [math] proposed ordering for task list, scope of initial release
Date Tue, 10 Jun 2003 21:33:27 GMT
On Tue, 2003-06-10 at 14:23, Phil Steitz wrote:
> Al Chou wrote:
> I actually was thinking the other way around.  If you feel strongly 
> about keeping these things in stat, we can create StatUtils.  The point 
> is to encapsulate these basic functions so that a) users can get them 
> immediately without thinking about our stat abstractions and b) we can 
> get the storage-based computations of the basic quantities in one place. 


>   When the UnivariateImpl window is finite, it should use the same 
> computations that AbstractStoreUnivariate does -- this is why we need to 
> encapsulate.


I agree with both of these ideas.  I think that putting everything in
MathUtil might become unwieldy - no problem with creating a StatUtil. 
(If that hasn't already been done, I'm checking my email for the first
time in days)


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message