April 2018 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] 'Contribute a fix to Pharo' for new Iceberg ?

by Marcus Denker

> On 23 Apr 2018, at 11:38, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Hi, > > I got the new Iceberg working on the latest Pharo 7 (used it to commit something to P3) - authentication should be OK then I guess. It feels much better. > > I would like to try contributing to Pharo again. > > Has https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo been updated for the new Iceberg ? > No, not yetâ¦ > Have things become simpler ? > The ways that I found how to do it: no. But I need more input from Esteban, I am for sure doing things wrong. (this is why I did not start to update the tutorial with the way I am doing PRs now) Marcus

April 23, 2018

'Contribute a fix to Pharo' for new Iceberg ?

by Sven Van Caekenberghe

Hi, I got the new Iceberg working on the latest Pharo 7 (used it to commit something to P3) - authentication should be OK then I guess. It feels much better. I would like to try contributing to Pharo again. Has https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo been updated for the new Iceberg ? Have things become simpler ? I also forgot the easy/short git command to bring my fork up to date (if I have to do this myself). Sven

April 23, 2018

Using P3 to connect to CockroachDB

by Sven Van Caekenberghe

Hi, Just a quick note: it is possible to use P3 (the lean and mean PostgreSQL client for Pharo using frontend/backend protocol 3.0, https://github.com/svenvc/P3) to connect to CockroachDB (an SQL database for global cloud services, an open source clone of Google Spannner, https://www.cockroachlabs.com) as it supports the same line protocol. Just make sure to load the latest version of P3 (and ZTimestamp when you are on Pharo 7). If you do their tutorial, you can set up your connection as follows: P3Client url: 'psql://root@localhost:26257/bank'. Sven

April 23, 2018

Re: [Pharo-dev] [Pharo 7.0-dev] Build #796: 21761-change-asDoItIn-to-asDoItForContext

by Marcus Denker

For AST evaluation I continue to improve things step-by-step. e.g. this PR - improves the method that wraps ASTs into doit-methods in the case where we want to execute for a certain context (#asDoItForContext: does all the magic of rewriting temps and adding a return) - OpalCompiler>>#parse was radically simplifies by using asDoItForContext: and #asDoit. - I started to rewrite all users of the #translate method of the compiler which will be deprecated later (as you can either use #parse or #compile). More to come, step by stepâ¦ > On 23 Apr 2018, at 11:02, ci-pharo-ci-jenkins2(a)inria.fr wrote: > > There is a new Pharo build available! > > The status of the build #796 was: SUCCESS. > > The Pull Request #1241 was integrated: "21761-change-asDoItIn-to-asDoItForContext" > Pull request url: https://github.com/pharo-project/pharo/pull/1241 > > Issue Url: https://pharo.fogbugz.com/f/cases/21761 > Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

April 23, 2018

[Pharo 7.0-dev] Build #796: 21761-change-asDoItIn-to-asDoItForContext

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #796 was: SUCCESS. The Pull Request #1241 was integrated: "21761-change-asDoItIn-to-asDoItForContext" Pull request url: https://github.com/pharo-project/pharo/pull/1241 Issue Url: https://pharo.fogbugz.com/f/cases/21761 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

April 23, 2018

[Pharo 7.0-dev] Build #795: 21761-change-asDoItIn-to-asDoItForContext

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #795 was: FAILURE. The Pull Request #1241 was integrated: "21761-change-asDoItIn-to-asDoItForContext" Pull request url: https://github.com/pharo-project/pharo/pull/1241 Issue Url: https://pharo.fogbugz.com/f/cases/21761 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

April 23, 2018

[Pharo 7.0-dev] Build #794: 21753-Integrate-Calypso-0112

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #794 was: FAILURE. The Pull Request #1238 was integrated: "21753-Integrate-Calypso-0112" Pull request url: https://github.com/pharo-project/pharo/pull/1238 Issue Url: https://pharo.fogbugz.com/f/cases/21753 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

April 23, 2018

Esteban's ChangeLog week of 16 April 2018

by estebanlm＠gmail.com

Hello! This is my weekly ChangeLog, from 16 April 2018 to 22 April 2018. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=16/4/2018&to=22/4/2018 ChangeLog ========= 16 April 2018: -------------- * I finally updated Alien package into Pharo according to Torsten package modifications. This was [case: 20878](https://pharo.fogbugz.com/f/cases/20878) And PR can be seen here: [https://github.com/pharo-project/pharo/pull/1202](https://github.com/pharo-… cheers! Esteban

April 23, 2018

Re: [Pharo-dev] Do we kill the catalog?

by Stephan Eggermont

Thierry Goubier <thierry.goubier(a)gmail.com> wrote: >No +1 > > Just write that ston now for the current state of OSProcess (with all > versions and platforms supported). > > Or write that ston for a project that has stable branches for all pharo > versions, from say 1.3 to now. > > But, in a way, please do the way you like, and, well, a few years down > the line, we're back at the same situation as now. > > Not that I wish it, but I can see when someone is solving a problem with > yet another way of having the problem. Indeed. Stephan

April 23, 2018

Re: [Pharo-dev] learning about ClassTestCase

by Ben Coman

On 23 April 2018 at 00:48, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > No idea. May be people were thinking that printOn: were not worth tests. > Now I would like to revisit some unused features of Sunit such as the > history. > > On Sun, Apr 22, 2018 at 3:44 AM, Ben Coman <btc(a)openinworld.com> wrote: > > I bumped into ClassTestCase for the first time, with class comment... > > "This class is intended for unit tests of individual classes and their > > metaclasses. > > It provides methods to determine the coverage of the unit tests. > > > > Subclasses are expected to re-implement: > > #classesToBeTested and > > #selectorsToBeIgnored > btw, I see in Pharo6.1 that most implementors of #selectorsToBeIgnored are circa 2003 authored by "brb". Note it was useful to be able to see this info in "Versions" which is currently not available in Pharo 7. cheers -ben > > They should also implement to confirm that all methods have been tested. > > #testCoverage > > super testCoverage. > > " > > > > A few questions to improve my knowledge of how to use this... > > > > a. there are no implementors of #classesToBeTested but several of > > #classToBeTested. I presume the class comment is wrong? > > > > b. there are no implementors of #testCoverage, so I presume I can > ignore > > that? (and I've no example to work from) > > > > c. ClassTestCase is subclassed 73 times, but #selectorsToBeIgnored is > only > > implemented 9 times. So this seems not critical? But btw, every of > those at > > least ignores #printOn:. I'm curious why? These are tagged "private", > but > > is that a good reason not to test it? > > > > My purpose was to add a new class MagnitudeTest for a new > > new method to Magnitude in response to the recent #min:max: discussion. > > > > cheers -ben > >

April 22, 2018