On Fri, 22 Feb 2019 at 15:50, Esteban Maringolo wrote:
>
> El vie., 22 feb. 2019 a las 11:43, ducasse
> () escribió:
> > + 1
> > :)
>
> > But I’m an easy person when it is about cleaning.
>
> +1. That makes us two.
+1
Cheers,
Alistair
There is a new Pharo build available!
The status of the build #95 was: SUCCESS.
The Pull Request #2655 was integrated:
"1967-critiques-icons-are-not-managed-correctly"
Pull request url: https://github.com/pharo-project/pharo/pull/2655
Issue Url: https://pharo.fogbugz.com/f/cases/1967
Build
El vie., 22 feb. 2019 a las 11:43, ducasse
() escribió:
> + 1
> :)
> But I’m an easy person when it is about cleaning.
+1. That makes us two.
+ 1
:)
But I’m an easy person when it is about cleaning.
> On 22 Feb 2019, at 15:39, Sven Van Caekenberghe wrote:
>
> Hi,
>
> Did you know that both Stream and Collection respond to #write: (as an alias
> to #<< and #add: respectively) ? I sure did not (and I did quite a bit of
> stream
There is a new Pharo build available!
The status of the build #96 was: SUCCESS.
The Pull Request #2673 was integrated: "Small fix that slightly improves how
the removal caption is created…"
Pull request url: https://github.com/pharo-project/pharo/pull/2673
Issue Url:
Hi,
Did you know that both Stream and Collection respond to #write: (as an alias to
#<< and #add: respectively) ? I sure did not (and I did quite a bit of stream
hacking).
This selector is not used for these 2 receiver types in the standard image
(except for one unit test), I never saw it
There is a new Pharo build available!
The status of the build #94 was: SUCCESS.
The Pull Request #2686 was integrated:
"2683-Remove-deprecated-pragma-to-use-deprecated-method"
Pull request url: https://github.com/pharo-project/pharo/pull/2686
Issue Url: https://pharo.fogbugz.com/f/cases/2683
There is a new Pharo build available!
The status of the build #93 was: SUCCESS.
The Pull Request #2671 was integrated: "2670-Update-the-checkVMVersion-date"
Pull request url: https://github.com/pharo-project/pharo/pull/2671
Issue Url: https://pharo.fogbugz.com/f/cases/2670
Build Url:
https://github.com/pharo-project/pharo/issues/2701
> On 22 Feb 2019, at 15:57, Alistair Grant wrote:
>
> On Fri, 22 Feb 2019 at 15:50, Esteban Maringolo wrote:
>>
>> El vie., 22 feb. 2019 a las 11:43, ducasse
>> () escribió:
>>> + 1
>>> :)
>>
>>> But I’m an easy person when it is about
There is a new Pharo build available!
The status of the build #97 was: SUCCESS.
The Pull Request #2678 was integrated:
"2677-Add-a-setting-to-disable-the-world-menu"
Pull request url: https://github.com/pharo-project/pharo/pull/2678
Issue Url: https://pharo.fogbugz.com/f/cases/2677
Build
There is a new Pharo build available!
The status of the build #98 was: FAILURE.
The Pull Request #2698 was integrated:
"2680-Cleanup-and-streamline-semantics-of-WriteStream-and-putOn-"
Pull request url: https://github.com/pharo-project/pharo/pull/2698
Issue Url:
There is a new Pharo build available!
The status of the build #99 was: FAILURE.
The Pull Request #2662 was integrated:
"2645-Duplication-wrappingPolicyLabel-and-lineNumbersDisplayLabel-is-defined-4-times"
Pull request url: https://github.com/pharo-project/pharo/pull/2662
Issue Url:
Sven Van Caekenberghe wrote:
.
>
> So I propose to remove [Stream|Collection]>>#write:
>
> What say thou ?
Check the selectors used in the latest packages on squeaksource, ss3,
smalltalkhub and decide.
Stephan
> On 22 Feb 2019, at 19:39, Stephan Eggermont wrote:
>
> Sven Van Caekenberghe wrote:
> .
>>
>> So I propose to remove [Stream|Collection]>>#write:
>>
>> What say thou ?
>
> Check the selectors used in the latest packages on squeaksource, ss3,
> smalltalkhub and decide.
>
> Stephan
You
> Am 22.02.2019 um 19:45 schrieb Sven Van Caekenberghe :
>
>
>
>> On 22 Feb 2019, at 19:39, Stephan Eggermont wrote:
>>
>> Sven Van Caekenberghe wrote:
>> .
>>>
>>> So I propose to remove [Stream|Collection]>>#write:
>>>
>>> What say thou ?
>>
>> Check the selectors used in the latest
--- Begin Message ---
Trying to be *somewhat* compatible and verifying (even quickly) that
it's not breaking a gazillion things is the very least someone can
do... Backward compatibility is NOT a sin! ;)
On 2019-02-22 13:45, Sven Van Caekenberghe wrote:
On 22 Feb 2019, at 19:39, Stephan
Many system classes contain lots of methods that are confusing, duplicates of
similar functionality, bogus, old, unused, untested and undocumented . This
makes the system more complex, especially for newcomers, but also for everyone
else trying to make changes. This is often technical debt,
There is a new Pharo build available!
The status of the build #100 was: SUCCESS.
The Pull Request #2702 was integrated:
"2688-Remove-GLMExamplesBrowser-and-GLMExamples"
Pull request url: https://github.com/pharo-project/pharo/pull/2702
Issue Url: https://pharo.fogbugz.com/f/cases/2688
Build
18 matches
Mail list logo
