Mark R. Diggory wrote:
I've got a design decision to make that I'd like to get others opinion
on. Currently, the strategy in UnivariateImpl is to calculate the
rudimentary building blocks of the statistics and then calculate the
statistics in the getters (getVariance, getSkewness, getKurtosis
On Mon, 16 Jun 2003, Mark R. Diggory wrote:
(1) Bean etiquette suggests getters are for bean properties, its
usually recommended that this means that they do nothing more than
return the value for a property. This is beneficial in our Univariate
case when calling a getter many times
--- Mark R. Diggory [EMAIL PROTECTED] wrote:
Andreou Andreas wrote:
Mark, I would go for the latter approach (the one on the p.s.) cause
it doesn't seem that complex to me...
Why not add a CachableUnivariateImpl class
that extends UnivariateImpl
and also keeps track in a cache the
On Mon, 16 Jun 2003, Mark R. Diggory wrote:
big snip
I'm talking strictly about UnivariateImpl at this time, I'm not quite
ready to delve into the Storage Implementations.
...another snip...
could be detected by the the Univariate
Implementation and such a
caching mechanism could be
