[ANN] Pharo Newsletter March 2020
The Pharo Newsletter March 2020 has been sent to subscribers last week:
https://mailchi.mp/pharo/pharo-newsletter-march-2020
To get it as soon as it is released, please subscribe here:
http://eepurl.com/bykqWn
I’m interested in exploring this - partly because it hit me and wasted my time
chasing down why we have a difference in #sum from other languages. It seems
that the implementation is trying to be very clever - I guess from the generic
usage of collections which don’t have to contain only
Like I said, we have had big discussions about this, I am not sure we want to
revisit them.
It is not just the problem that summing assumes the elements to be numbers
(whatever that it, let's say objects that can be added), it is also the
question what the additive identity should be (0 most
Hi Bob,
> El 21 mar 2020, a las 18:26, Rob Raisch escribió:
>
> I’ve noticed that the majority of projects in which I have an interest, from
> any repository, like Moose or PetitParser, fail to load into Pharo 8.0
> throwing errors related to missing requirements.
This is probably because
Am 23.03.20 um 14:45 schrieb James Foster:
On Mar 23, 2020, at 6:06 AM, Sven Van Caekenberghe wrote:
What you found out now is that the clever trick used to avoid picking an
additive identity (picking an element, counting it twice and then subtracting
it) leads to a loss of precision when
Both are excellent suggestions.
We have to think a bit about the consequences.
Still, both would not solve the problem of what to return when the collection
is empty.
> On 23 Mar 2020, at 15:47, Konrad Hinsen wrote:
>
> Am 23.03.20 um 14:45 schrieb James Foster:
>
>>> On Mar 23, 2020, at
> On Mar 23, 2020, at 8:14 AM, Sven Van Caekenberghe wrote:
>
> Both are excellent suggestions.
>
> We have to think a bit about the consequences.
>
> Still, both would not solve the problem of what to return when the collection
> is empty.
Zero?
>
>> On 23 Mar 2020, at 15:47, Konrad
> On Mar 23, 2020, at 6:06 AM, Sven Van Caekenberghe wrote:
>
> What you found out now is that the clever trick used to avoid picking an
> additive identity (picking an element, counting it twice and then subtracting
> it) leads to a loss of precision when floating point numbers are
I’m always impressed with the quality of answers that come out of these
discussions - inevitably I’m reminded that dispatching off the right parties is
ultimately where the power lies (when you cheat - it always seems to end up
with a gotcha).
Thanks guys.
Tim
> On 23 Mar 2020, at 15:15,
https://jrmpc.ca/2020/03/20/what-makes-learning-smalltalk-challenging/
FWIW, 95% of respondents pointed to the lack of reference documentation for
the class library as the major obstacle to learning Smalltalk/Pharo.
Richard
https://github.com/pharo-project/pharo/issues/2225
> On 23 Mar 2020, at 17:14, Tim Mackinnon wrote:
>
> I’m always impressed with the quality of answers that come out of these
> discussions - inevitably I’m reminded that dispatching off the right parties
> is ultimately where the power lies
Thanks for the git issue - and sadly this goes back a long way :(
I’ve added my example to the sad history… is there anyone that can rule on this?
> On 23 Mar 2020, at 21:23, Sven Van Caekenberghe wrote:
>
> https://github.com/pharo-project/pharo/issues/2225
>
>> On 23 Mar 2020, at 17:14, Tim
12 matches
Mail list logo
