February 2020 - Pharo-dev - lists.pharo.org

[Pharo 9.0] Build #54: redo-5464-Bug-Slot-template-add-variable-without-hash-Crash-on-accept

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

There is a new Pharo build available! The status of the build #54 was: FAILURE. The Pull Request #5660 was integrated: "redo-5464-Bug-Slot-template-add-variable-without-hash-Crash-on-accept" Pull request url: https://github.com/pharo-project/pharo/pull/5660 Issue Url: https://github.com/pharo-project/pharo/issues/redo Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 11, 2020

Re: [Pharo-dev] [Ann] Concurrent Programming in Pharo is available

by Eliot Miranda

Hi Stef, here's my review/feedback On Sun, Feb 9, 2020 at 5:05 AM StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > wrote: > > > > On http://books.pharo.org/booklet-ConcurrentProgramming/ > In fig 1.1 there needs to be a back arrow from Executing to Runnable which is labelled "Preempted by a higher priority process" or similar. In the label for fig 1.2 the word "pending" should be replaced with "runnable". Page 8, section "Process Priorities" "At any time only one process is executed." should read "At any time only one process is executing." The line starting "Next table lists..." in the last paragraph on page 8 should read "The following table lists...". The section might want to state some thing like "there that the current implementation of the Pharo scheduler has process priorities from 1 to 100. Only some of these are named. But the programmer is free to use any priority within that range that they see fit." It would be good to include examples which did things like "forkAt: Processor userPriority + 1", etc. In the label for Fig 2.1 "ressources" should read "resources". But throughout that section I would word it that "processes need to share resources", but "the process is waiting to acquire the resource". So use the plural for the general case and the singular for the specific case. Sentences such as this: "P0 has finished to use the resources." should read "P0 has finished using the resource." In Section 2.1 Conclusion "Semaphores are the lower synchronisation mechanisms." should read "Semaphores are the lowest level synchronisation mechanisms." Chapter 3, "Scheduler's Principles" should state that "The Smalltalk scheduler is a real-time, cooperative, preemptive across priorities, non-preemptive within priorities, scheduler." The title to Chapter 4.5 "ShareQueue: a nice semaphore example" should read "Share*d*Queue: a nice semaphore example" Most of the paragraphs on page 49 in section 4.5 are still in French and need translating. > S. > > -------------------------------------------- > StÃ©phane Ducasse > http://stephane.ducasse.free.fr / http://www.pharo.org > 03 59 35 87 52 > Assistant: Julie Jonas > FAX 03 59 57 78 50 > TEL 03 59 35 86 16 > S. Ducasse - Inria > 40, avenue Halley, > Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza > Villeneuve d'Ascq 59650 > France > > -- _,,,^..^,,,_ best, Eliot

Feb. 10, 2020

Re: [Pharo-dev] [Ann] Concurrent Programming in Pharo is available

by ducasse

You are welcome. This is really one of the few resources on the topic and at this level in the ecosystem. In the future I plan to learn and explain monitors because they are better than semaphores or mutexes but I have the learn about them before :). > On 10 Feb 2020, at 20:46, Todd Blanchard <tblanchard(a)mac.com> wrote: > > > From: Todd Blanchard <tblanchard(a)mac.com> > Subject: Re: [Pharo-dev] [Ann] Concurrent Programming in Pharo is available > Date: 10 February 2020 at 20:46:46 CET > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > Cc: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > > > I have wanted a clean explanation of semaphores and process scheduling for a long time. > > Thanks for this. > > >> On Feb 9, 2020, at 3:58 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr <mailto:stephane.ducasse@inria.fr>> wrote: >> >> On http://books.pharo.org/booklet-ConcurrentProgramming/ <http://books.pharo.org/booklet-ConcurrentProgramming/> >> >> >> S. >> >> -------------------------------------------- >> StÃ©phane Ducasse >> http://stephane.ducasse.free.fr <http://stephane.ducasse.free.fr/> / http://www.pharo.org <http://www.pharo.org/> >> 03 59 35 87 52 >> Assistant: Julie Jonas >> FAX 03 59 57 78 50 >> TEL 03 59 35 86 16 >> S. Ducasse - Inria >> 40, avenue Halley, >> Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza >> Villeneuve d'Ascq 59650 >> France >> > > >

Feb. 10, 2020

Re: [Pharo-dev] [Ann] Concurrent Programming in Pharo is available

by Todd Blanchard

I have wanted a clean explanation of semaphores and process scheduling for a long time. Thanks for this. > On Feb 9, 2020, at 3:58 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > On http://books.pharo.org/booklet-ConcurrentProgramming/ <http://books.pharo.org/booklet-ConcurrentProgramming/> > > > S. > > -------------------------------------------- > StÃ©phane Ducasse > http://stephane.ducasse.free.fr <http://stephane.ducasse.free.fr/> / http://www.pharo.org <http://www.pharo.org/> > 03 59 35 87 52 > Assistant: Julie Jonas > FAX 03 59 57 78 50 > TEL 03 59 35 86 16 > S. Ducasse - Inria > 40, avenue Halley, > Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza > Villeneuve d'Ascq 59650 > France >

Feb. 10, 2020

Re: [Pharo-dev] [Ann] Concurrent Programming in Pharo is available

by ducasse

> On 10 Feb 2020, at 18:28, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Thanks! And thanks in general for your tireless documentation efforts. I know > it can be a lonely pursuit but is soooo important :) :) Just pay me in PRs :) Now working on the new Spec20 book. S. > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

Feb. 10, 2020

Re: [Pharo-dev] [Ann] Concurrent Programming in Pharo is available

by Sean P. DeNigris

Thanks! And thanks in general for your tireless documentation efforts. I know it can be a lonely pursuit but is soooo important :) ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Feb. 10, 2020

[Pharo 9.0] Build #53: 5650-Make-unclosable-in-SystemWindow-does-not-work-revert-PR-5552

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

There is a new Pharo build available! The status of the build #53 was: FAILURE. The Pull Request #5659 was integrated: "5650-Make-unclosable-in-SystemWindow-does-not-work-revert-PR-5552" Pull request url: https://github.com/pharo-project/pharo/pull/5659 Issue Url: https://github.com/pharo-project/pharo/issues/5650 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 10, 2020

[ANN] Pharo TechTalk Feb 20: The Colony

by Marcus Denker

A regular chat about Pharo. Happens on Discord. This month a bit a special TechTalk, not about Pharo but about a tool that might be interesting for us to use. Topic: The Colony https://colony.io Introduction to "The Colony", a new platform to Organize and Incentivize Collaborators, Contributors, and Communities. Short demo, followed by some Q&A, help to get people onboarded. https://association.pharo.org/event-3697011 20 Feb 2020 â¢ 1:30 PM - 2:30 PM (EST) NOTE: this is EST time, for Europe, this is 19:30 (the easiest is to download the calendar entry)

Feb. 10, 2020

Re: [Pharo-dev] [Mm10s] 2020-02-10

by ducasse

and we will start to write a booklet see https://github.com/SquareBracketAssociates/Booklet-PharoVirtualMachine S. >> >> Monday morning, time for the weekly mail meeting in 10 seconds! >> (just reply, inserting bullet points) >> >> ### Last week: >> >> - PharoVM wiki > > Is this publicly accessible? Can we have a link? > > Thanks! > Alistair >

Feb. 10, 2020

Re: [Pharo-dev] [Mm10s] 2020-02-10

by Alistair Grant

Thanks! On Mon, 10 Feb 2020 at 11:10, tesonep(a)gmail.com <tesonep(a)gmail.com> wrote: > > It's under construction, but here it is > https://github.com/pharo-project/opensmalltalk-vm/wiki > > On Mon, Feb 10, 2020 at 10:46 AM Alistair Grant <akgrant0710(a)gmail.com> wrote: > > > > Hi Pablo, > > > > > > On Mon, 10 Feb 2020 at 10:31, tesonep(a)gmail.com <tesonep(a)gmail.com> wrote: > > > > > > Monday morning, time for the weekly mail meeting in 10 seconds! > > > (just reply, inserting bullet points) > > > > > > ### Last week: > > > > > > - PharoVM wiki > > > > Is this publicly accessible? Can we have a link? > > > > Thanks! > > Alistair > > > > > -- > Pablo Tesone. > tesonep(a)gmail.com >

Feb. 10, 2020