May 2023 - Pharo-users - lists.pharo.org

[ANN] Willow-Bootstrap v14.0.0 [v14.0.0] released!

by Buenos Aires Smalltalk

May 29, 2023

[ANN] Willow v15.0.0 [v15.0.0] released!

by Buenos Aires Smalltalk

May 29, 2023

[ANN] RenoirSt v8.0.0 [v8.0.0] released!

by Buenos Aires Smalltalk

May 29, 2023

[ANN] Boardwalk v7.0.0 [v7.0.0] released!

by Buenos Aires Smalltalk

May 29, 2023

Re: Talk next wednesday

by Samuel Teixeira Santos

Hello everyone this talk will be recorded? Regards Em sÃ¡b., 27 de mai. de 2023 Ã s 15:34, stephane ducasse < stephane.ducasse(a)inria.fr> escreveu: > Hello > > I will give a presentation with discussion via the UK smalltalk online > gathering next wednesday. > > https://www.meetup.com/ukstug/events/293473947/ > > MeetupStephane Ducasse - Pharo: a vision implemented step by step, Wed, > M...For our May presentation, Stephane Ducasse will present the vision > behind Pharo and how that is been implemented incrementally across multiple > releases. In Stef's words: " > > For our May presentation, Stephane Ducasse will present the vision behind > Pharo and how that is been implemented incrementally across multiple > releases. In Stef's words: "The vision of Pharo is based on three pillars: > â¢ First we want to make sure that Pharo is used to develop complex and > robust systems (by complex we means multiple millions lines of code or > objects). > â¢ Second we want Pharo to be a modular system that can be versatile (Pharo > on iot, on large servers, in the web browserâ¦.) > â¢ Third Pharo should be an evolvable system that can adapt to new needs > (modular tools, first class slot, new debuggers, packagesâ¦). > > Stef -- At.te, *Samuel* Teixeira Santos

May 29, 2023

[ANN] Cannon v1.2.0 [v1.2.0] released!

by Buenos Aires Smalltalk

May 29, 2023

[ANN] Stargate-Consul v4.2.0 [v4.2.0] released!

by Buenos Aires Smalltalk

May 29, 2023

Talk next wednesday

by stephane ducasse

Hello I will give a presentation with discussion via the UK smalltalk online gathering next wednesday. https://www.meetup.com/ukstug/events/293473947/ MeetupStephane Ducasse - Pharo: a vision implemented step by step, Wed, M...For our May presentation, Stephane Ducasse will present the vision behind Pharo and how that is been implemented incrementally across multiple releases. In Stef's words: " For our May presentation, Stephane Ducasse will present the vision behind Pharo and how that is been implemented incrementally across multiple releases. In Stef's words: "The vision of Pharo is based on three pillars: â¢ First we want to make sure that Pharo is used to develop complex and robust systems (by complex we means multiple millions lines of code or objects). â¢ Second we want Pharo to be a modular system that can be versatile (Pharo on iot, on large servers, in the web browserâ¦.) â¢ Third Pharo should be an evolvable system that can adapt to new needs (modular tools, first class slot, new debuggers, packagesâ¦). Stef

May 27, 2023

This week (21/2023) on the Pharo Issue Tracker

by Marcus Denker

# This week (21/2023) on the Pharo Issue Tracker. This we we merged all changes done during the last weeks in Pharo11 to Pharo12. ClassOrganization refactoring continues, we will soon be able to inline the class into ClassDescription. # Pharo 11 - Backport fix to calypso method search #13794 https://github.com/pharo-project/pharo/pull/13794 # Fixes - merge Pharo11 changes into Pharo12 #13784 https://github.com/pharo-project/pharo/pull/13784 - Fix reaction of Epicea to protocol removal #13801 https://github.com/pharo-project/pharo/pull/13801 - Migrate variables of VariableLayout only if old instance was also variable #13789 https://github.com/pharo-project/pharo/pull/13789 - Fix #13478: Filter on calypsoName instead of name #13778 https://github.com/pharo-project/pharo/pull/13778 - Fix: RBClassRegexRefactoring #13770 https://github.com/pharo-project/pharo/pull/13770 - Loading Pharo12 branch of Sindarin in BaselineOfNewTools for Pharo 12 #525 https://github.com/pharo-spec/NewTools/pull/525 - Add source folder of Sindarin #530 https://github.com/pharo-spec/NewTools/pull/530 # Protocols / ClassOrganizer - Remove user of #organization in Debugger #531 https://github.com/pharo-spec/NewTools/pull/531 - Method announcements should use real protocols #13730 https://github.com/pharo-project/pharo/pull/13730 - Inline ClassOrganization>>extensionProtocols #13783 https://github.com/pharo-project/pharo/pull/13783 - Reduce users of #organization #13785 https://github.com/pharo-project/pharo/pull/13785 - organization, not organisation #13782 https://github.com/pharo-project/pharo/pull/13782 - Remove dead method ClassDescription>>#zapOrganization #13774 https://github.com/pharo-project/pharo/pull/13774 - Inline ClassOrganization>>#hasProtocol: #13776 https://github.com/pharo-project/pharo/pull/13776 # Tests - Add tests for Calypso's item filter #13786 https://github.com/pharo-project/pharo/pull/13786 - FIx DebugSession test #13811 https://github.com/pharo-project/pharo/pull/13811 - Fix completion tests after p11 synch #13809 https://github.com/pharo-project/pharo/pull/13809 - Improve CoverageCollectorTest assertions #13787 https://github.com/pharo-project/pharo/pull/13787 - fix-testConstantBlockClosure-CleanBlocks #13781 https://github.com/pharo-project/pharo/pull/13781 # Cleanup - Remove unimplemented code StSpotterQuery.class.st #528 https://github.com/pharo-spec/NewTools/pull/528 - Remove Deprecated Package Spec2-ObservableSlot #1396 https://github.com/pharo-spec/Spec/pull/1396 - Merge SHTextStyler and SHRBTextStyler #13756 https://github.com/pharo-project/pharo/pull/13756 - Cleanup dead code in RubShoutStylerDecorator #13771 https://github.com/pharo-project/pharo/pull/13771 - Update StGenericGenerator.class.st #526 https://github.com/pharo-spec/NewTools/pull/526

May 26, 2023

Re: Exception handler chaining

by Richard Sargent

#, will do the trick. ExceptionOne, ExceptionTwo Nesting the #on:do: messages is probably the more correct approach, since each one would be catching just one family of exceptions and not require class testing. Unfortunately, nested #on:do: messages are terribly ugly. Many people (I hate that phrase!) tend to isolate the protected implementation from the protecting code. e.g. the implementation of #doSomething wraps a message send to #doSomethingProtected in the exception handlers. On Thu, May 25, 2023 at 9:45â¯AM James Foster via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > Rather than âArray with:with:â it probably should be âExceptionSet > with:with:â. > > On May 25, 2023, at 9:19 AM, James Foster via Pharo-users < > pharo-users(a)lists.pharo.org> wrote: > > The #âon:do:â implementation in Block accepts either an Exception or an > ExceptionSet as the first parameter. So you can do something like the > following (Iâm typing from memory without trying so may have syntax > errrors): > > [ âtryBlockâ ] on: (Array with: ExceptionOne with: ExceptionTwo) do: [:ex > | > (ex isKindOf: ExceptionOne) ifTrue: [ âhandleOneâ ]. > (ex isKindOf: ExceptionTwo) ifTrue: [ âhandleTwoâ ]. > ]. > > The above code can be improved in a variety of ways, but it should get you > started. Note also that since Smalltalk allows you to modify base classes, > you could add #âon:do:on:do:â to Block. > > James > > On May 25, 2023, at 8:24 AM, mlntdrv(a)gmail.com wrote: > > In other languages there is the possibility to chain exception handlers > like this: > > try { doOne(); doTwo(); doThree(); } > > catch(ExceptionOne ex){ > > handleOne(); > > } > > catch(ExceptionTwo ex) { > > handleTwo(); > > } > > catch(ExceptionThree ex) { > > handleThree(); > > } > > catch(Exception ex) { > > handleRest(); > > } > > Is this possible in Pharo? Iâve tried > > [ block ] > > on: ExceptionOne do: [ handleOne ] > > on: ExceptionTwo do: [ handleTwo ] > > but it is invalid syntax. > > > >

May 25, 2023