- Pharo-dev - lists.pharo.org

[Pharo 9.0] Build #23: 5571-testDefaultImageDoesNotStoreAnySetting-failing-in-Pharo9-on-CI-all-plattforms
by ci-pharo-ci-jenkins2＠inria.fr Jan. 24, 2020

Jan. 24, 2020

There is a new Pharo build available! The status of the build #23 was: SUCCESS. The Pull Request #5572 was integrated: "5571-testDefaultImageDoesNotStoreAnySetting-failing-in-Pharo9-on-CI-all-plattforms" Pull request url: https://github.com/pharo-project/pharo/pull/5572 Issue Url: https://github.com/pharo-project/pharo/issues/5571 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Re: [Pharo-dev] Short Survey about automatic deprecation rewrites
by ducasse Jan. 24, 2020

Jan. 24, 2020

Thanks! Martin milton juraj should do it too :) S. > On 21 Jan 2020, at 21:34, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > > From: Alexandre Bergel <alexandre.bergel(a)me.com> > Subject: Re: [Pharo-dev] Short Survey about automatic deprecation rewrites > Date: 21 January 2020 at 21:34:58 CET > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > Cc: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > > > Just answered! > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >> On 21-01-2020, at 13:23, Guillermo Polito <guillermopolito(a)gmail.com> wrote: >> >> Hi all, >> >> We would like to share with you a short survey about the automatic deprecation rewrites that have been around since Pharo 6. >> It will be super useful for us to enhance the support for migrations. >> We estimate it will take ~< 3 minutes to fill. >> >> This survey is aimed at people both *using* Pharo, or writing libraries and frameworks for Pharo. >> If youâre a library/framework maintainer and you know people using your library, would you mind share it with them? >> >> Link to the survey: https://sondages.inria.fr/index.php/133442?lang=en >> >> Thanks a lot! >> Guille, in behalf of the Pharo consortium > > > >

3 2

[ANN] Pharo Consortium New Academic Member: ÃTS MontrÃ©al
by Marcus Denker Jan. 24, 2020

Jan. 24, 2020

The Pharo Consortium is very happy to announce that ÃTS MontrÃ©al has joined the Consortium as an Academic Member. About - ÃTS MontrÃ©al: https://www.etsmtl.ca/en/Home - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium is to allow companies and institutions to support the ongoing development and future of Pharo. Individuals can support Pharo via the Pharo Association: http://association.pharo.org

1 0

Reddit Request: Bootstrap Example/Tutorial
by Sean P. DeNigris Jan. 24, 2020

Jan. 24, 2020

>> Deployment - it is now possible to bootstrap an image containing exactly what you want > Where can I see examples of how to do that? (Genuine question) I replied with http://forum.world.st/Pharo-Bootstrap-tt5080441.html, but maybe there's something better? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

1 0

Bug report from HN: Windows - "Unsupported 16-bit Application"
by Sean P. DeNigris Jan. 24, 2020

Jan. 24, 2020

Quote: vm doesn't start on Windows - "Unsupported 16-bit Application"... I resolved the issue by navigating to the directory where it downloaded the vm's, deleting the folder and unzipping manually. Seems the launcher corrupts the files when it unzips them. https://news.ycombinator.com/item?id=22100514 ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

1 1

[TechTalk] Contributing to External Projects with Iceberg
by tesonep＠gmail.com Jan. 23, 2020

Jan. 23, 2020

Hi, I am sending the link of the video of today techtalk, maybe can be useful for someone. https://youtu.be/-jenQJp5m2U Cheers, Pablo -- Pablo Tesone. tesonep(a)gmail.com

1 0

[Pharo 9.0] Build #22: Adding setting for the limit of items in spotter
by ci-pharo-ci-jenkins2＠inria.fr Jan. 23, 2020

Jan. 23, 2020

There is a new Pharo build available! The status of the build #22 was: FAILURE. The Pull Request #5565 was integrated: "Adding setting for the limit of items in spotter" Pull request url: https://github.com/pharo-project/pharo/pull/5565 Issue Url: https://github.com/pharo-project/pharo/issues/5563 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #21: SUCCESS
by ci-pharo-ci-jenkins2＠inria.fr Jan. 23, 2020

Jan. 23, 2020

There is a new Pharo build available! The status of the build #21 was: SUCCESS. Could not extract further issue information from commit message: Updating the upload to handle 32 / 64 bits Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #20: FAILURE
by ci-pharo-ci-jenkins2＠inria.fr Jan. 23, 2020

Jan. 23, 2020

There is a new Pharo build available! The status of the build #20 was: FAILURE. Could not extract further issue information from commit message: Updating the upload to handle 32 / 64 bits Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Fed up
by ducasse Jan. 23, 2020

Jan. 23, 2020

Hi Iâm fed up. Why? Because I see lousy code in Pharo and that such lousy code in Pharo is slower, and sure that writing a type inferencer for pharo will be more complex, and probably will make sista more complex too. I asked the pharo consortium to take a clear position because I want a better Pharo not the inverse. So what is it. You can write in your code but not in Pharo. aCol do: #store in Pharo we should write aCol do: [ :each | each store ] Block argument should be blocks else any static analyser will have to check it is a block, it is a symbol, is it a RANDOM object that answer value. Seriously can be not make the life of people doing program analysis simpler? So now if Iâm wrong then I will shut up and Iâm really pissed that we do that without paying attention to the consequence. I asked the consortium to take position and to take action. We should have a better code review for REAL. S.

9 12