I don’t see how rounding errors could accumulate, if you keep the sum and not
the average.
The rounding errors should be neutral, because each element is added once and
subtracted once.
If + and – is symmetrical in this respect, rounding inaccuracies should balance
out.
Cheers,
I'd be very interested to hear how this ends up.
Parsing Outlook mails from Pharo may prove useful in my day job.
cheers -ben
On Wed, 8 Apr 2020 at 18:02, PBKResearch wrote:
> Hello Pablo
>
> Success! I have rerun one of the troublesome cases, with no problem. I
> then re-ran the test on the la
Hi Richard and Christian,
thanks for the comments/suggestions.
For the "self species ofSize… », I got inspiration from the image like with
#overlappingPairsCollect:
As for float rounding errors, that interesting to consider indeed. I’ll try a
buffer variant.
Some related questions for my OO
Dear all,
I'm thinking about implementing a software solution in Pharo (as one of
the candidate environments), it's a project that I'm dealing with
professionally. The goal is to develop a financial planning/simulation
application on the country level, which is at present developed as a set
o
Let's take the inheritance issue first.
Yes, Collection has some subclasses where #average makes no sense,
such as String. If any subclass of Collection should have #average, it is
Array, as #(1 2 3 4) average makes perfect sense.
BUT #($a $b $c $d) average makes exactly as much sense as 'abcd' av
