Hi Tim,
Is not about subprojects, is about hot fixes :)
Pharo 7 will continue having some updates on critical bugs but it should not
include regular changes (like an update on Calypso).
In that sense, fix #2781 sneaked in and it shouldn’t, which means we still need
to adjust the process :P
This is great - I’m pleased we can get fixes like this (and keen to get passed
that font issue which was driving me crazy).
A small related question - how do ensure we get fixes from sub projects
considered too? I’d really like to see:
https://github.com/pharo-ide/Calypso/pull/451 as it’s
Hello Richard,
I do it afterwards the input looks like this :
#(0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 7 3 7).
and I solved it already like this :
scoreAfterRolling: aCollection
| score |
score := 0.
1
You wrote: "a frame is always two times a throw"
but the specification says "A frame is composed of one or two ball throws"
and later we learn that the 10th frame may have three throws.
There is an issue with your Smalltalk.
aCollection withIndexDo: [:index :item |
"You have the arguments in