- Pharo-dev - lists.pharo.org

This week (42/2022) on the Pharo Issue Tracker

by Marcus Denker

This week (42/2022) on the Pharo Issue Tracker We merged 9 PRs this week Features ======= - Add a shortcut to extract method refactoring #11814 https://github.com/pharo-project/pharo/pull/11814 Fixes ===== - Fix : missing isScripting method in LessonView #11815 https://github.com/pharo-project/pharo/pull/11815 - Update comment to reflect refactoring actions #11778 https://github.com/pharo-project/pharo/pull/11778 - CI: when getting pharo version/prefix on PR, do not use --first-parent #11780 https://github.com/pharo-project/pharo/pull/11780 - Pharo11: 6191 find between substrings freezes the image #11771 https://github.com/pharo-project/pharo/pull/11771 Cleanups ======== - 11792-FFIConstantHandleTest-calls-deprecated-method-FFIExternalReferencehandle #11793 https://github.com/pharo-project/pharo/pull/11793 - moved the condition creation from the calypso package to the breakpoint #11807 https://github.com/pharo-project/pharo/pull/11807 Tests ===== - This adds an example and a test for Fluid Slot definitions #11786 https://github.com/pharo-project/pharo/pull/11786 Pharo10 ======= - Pharo10: CI: when getting pharo version/prefix on PR, do not use --first-parent #11785 https://github.com/pharo-project/pharo/pull/11785

Oct. 24, 2022

dubbing & subtitles on new MOOC

by Siemen Baader

Hi Stef & everyone interested in the MOOC(s), On Wed, Oct 5, 2022 at 9:09 PM stephane ducasse <stephane.ducasse(a)inria.fr> wrote: > Since more than a year we have been working on a new mooc called: > âAdvanced Object-oriented Design and Developmentâ > > It will be quite good. We are bullet proofing it with a new lecture here > at Lille. > It will indeed - like the original one! ;) > The mooc will be produced in english (and may be dub in french). > Have you thought about using synthetic voices to autogenerate dubs in several languages from the subtitles? They have become quite good and it can be very seamless. Perhaps it will also be cheaper? cheers Siemen

Oct. 24, 2022

Re: About Bag API

by stephane ducasse

thanks clement. I was looking for at: while occurrencesOf: was it. Now I introduced removeKey: ifAbsent: and keys because they are missing. S > On 23 Oct 2022, at 16:49, ClÃ©ment Dutriez <dutriezcle(a)gmail.com> wrote: > > Hello Everyone, > > It also makes sense to me. > > the message `addAll: aCollection`, is defined in **Collection** object. > The behavior of addAll: is to add every object of the collection. > So every dev who learn pharo will understand `addAll: aCollection` message, add all object of the collection aCollection. > If you want to count a String just send an `add:` message to Bag object. > > Finally the behavior of the Pharo Bag seems similar to Python Counter Object [1]. > > I don't understand why you found this behavior strange. > > I hope it will help. > > [1] : https://docs.python.org/3/library/collections.html#collections.Counter <https://docs.python.org/3/library/collections.html#collections.Counter> > -- > Dutriez ClÃ©ment > > > Le dim. 23 oct. 2022 Ã 13:35, Sebastian Jordan Montano <sebastian.jordan(a)inria.fr <mailto:sebastian.jordan@inria.fr>> a Ã©crit : > For me it makes sense that in your example `aBag at: $a` returns `5` > > Because as you said, a Bag is for keeping occurrences. So, at: $a should return how many occurrences $a has > > Sebastian > > ----- Mail original ----- > > De: "Stephane Ducasse" <stephane.ducasse(a)inria.fr <mailto:stephane.ducasse@inria.fr>> > > Ã: "Pharo Development List" <pharo-dev(a)lists.pharo.org <mailto:pharo-dev@lists.pharo.org>> > > EnvoyÃ©: Dimanche 23 Octobre 2022 09:27:45 > > Objet: [Pharo-dev] Re: About Bag API > > > it is because at: is in fact occurrencesOf: > > > > S > > > >> On 23 Oct 2022, at 11:26, stephane ducasse <stephane.ducasse(a)inria.fr <mailto:stephane.ducasse@inria.fr>> wrote: > >> > >> Hi > >> > >> I wonder why I cannot get values of a entry using at: > >> > >> | aBag | > >> aBag := Bag new. > >> aBag addAll: âaabbbacacccaâ. > >> aBag at: $a > >>>>> 5 > >> > >> I have the impression that this is because Bag API never got the correct amount > >> of love > >> but may be Iâm wrong. > >> > >> What is your opinion? > >> > > > S

Oct. 23, 2022

Re: About Bag API

by ClÃ©ment Dutriez

Hello Everyone, It also makes sense to me. the message `addAll: aCollection`, is defined in **Collection** object. The behavior of addAll: is to add every object of the collection. So every dev who learn pharo will understand `addAll: aCollection` message, add all object of the collection aCollection. If you want to count a String just send an `add:` message to Bag object. Finally the behavior of the Pharo Bag seems similar to Python Counter Object [1]. I don't understand why you found this behavior strange. I hope it will help. [1] : https://docs.python.org/3/library/collections.html#collections.Counter -- Dutriez ClÃ©ment Le dim. 23 oct. 2022 Ã 13:35, Sebastian Jordan Montano < sebastian.jordan(a)inria.fr> a Ã©crit : > For me it makes sense that in your example `aBag at: $a` returns `5` > > Because as you said, a Bag is for keeping occurrences. So, at: $a should > return how many occurrences $a has > > Sebastian > > ----- Mail original ----- > > De: "Stephane Ducasse" <stephane.ducasse(a)inria.fr> > > Ã: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > > EnvoyÃ©: Dimanche 23 Octobre 2022 09:27:45 > > Objet: [Pharo-dev] Re: About Bag API > > > it is because at: is in fact occurrencesOf: > > > > S > > > >> On 23 Oct 2022, at 11:26, stephane ducasse <stephane.ducasse(a)inria.fr> > wrote: > >> > >> Hi > >> > >> I wonder why I cannot get values of a entry using at: > >> > >> | aBag | > >> aBag := Bag new. > >> aBag addAll: âaabbbacacccaâ. > >> aBag at: $a > >>>>> 5 > >> > >> I have the impression that this is because Bag API never got the > correct amount > >> of love > >> but may be Iâm wrong. > >> > >> What is your opinion? > >> > > > S >

Oct. 23, 2022

Re: About Bag API

by Sebastian Jordan Montano

For me it makes sense that in your example `aBag at: $a` returns `5` Because as you said, a Bag is for keeping occurrences. So, at: $a should return how many occurrences $a has Sebastian ----- Mail original ----- > De: "Stephane Ducasse" <stephane.ducasse(a)inria.fr> > Ã: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > EnvoyÃ©: Dimanche 23 Octobre 2022 09:27:45 > Objet: [Pharo-dev] Re: About Bag API > it is because at: is in fact occurrencesOf: > > S > >> On 23 Oct 2022, at 11:26, stephane ducasse <stephane.ducasse(a)inria.fr> wrote: >> >> Hi >> >> I wonder why I cannot get values of a entry using at: >> >> | aBag | >> aBag := Bag new. >> aBag addAll: âaabbbacacccaâ. >> aBag at: $a >>>>> 5 >> >> I have the impression that this is because Bag API never got the correct amount >> of love >> but may be Iâm wrong. >> >> What is your opinion? >> > > S

Oct. 23, 2022

Re: About Bag API

by StÃ©phane Ducasse

it is because at: is in fact occurrencesOf: S > On 23 Oct 2022, at 11:26, stephane ducasse <stephane.ducasse(a)inria.fr> wrote: > > Hi > > I wonder why I cannot get values of a entry using at: > > | aBag | > aBag := Bag new. > aBag addAll: âaabbbacacccaâ. > aBag at: $a >>>> 5 > > I have the impression that this is because Bag API never got the correct amount of love > but may be Iâm wrong. > > What is your opinion? > > S

Oct. 23, 2022

About Bag API

by stephane ducasse

Hi I wonder why I cannot get values of a entry using at: | aBag | aBag := Bag new. aBag addAll: âaabbbacacccaâ. aBag at: $a >>> 5 I have the impression that this is because Bag API never got the correct amount of love but may be Iâm wrong. What is your opinion? S

Oct. 23, 2022

Re: This week (41/2022) on the Pharo Issue Tracker

by Martin Dias

On Tue, Oct 18, 2022 at 10:17 AM <sean(a)clipperadams.com> wrote: > > Go, go, go! > > Thanks for these updates, Marcus. Itâs great to have a concise summary of the progress easily available :) +1 thanks, I also find them very useful to do not loose track of changes. MartÃn

Oct. 18, 2022

Re: This week (41/2022) on the Pharo Issue Tracker

by sean＠clipperadams.com

Go, go, go! Thanks for these updates, Marcus. Itâs great to have a concise summary of the progress easily available :)

Oct. 18, 2022

This week (41/2022) on the Pharo Issue Tracker

by Marcus Denker

Fixes ===== - CopyClassRefactoring copies class comment as well #11789 https://github.com/pharo-project/pharo/pull/11789 - add missing utf8StringFromCString methods #11791 https://github.com/pharo-project/pharo/pull/11791 - Fixed resolving desktop file location #11768 https://github.com/pharo-project/pharo/pull/11768 Features ======== - 11775 feature request adding breakpoint groups and break on count breakpoints #11776 https://github.com/pharo-project/pharo/pull/11776 - Multiline Executable Comments #11774 https://github.com/pharo-project/pharo/pull/11774 CI == - Odd PR builds use the the latest VM, else use the stable VM #11678 https://github.com/pharo-project/pharo/pull/11678 Tests ===== - Reflectivity: more tests for multiple links #11782 https://github.com/pharo-project/pharo/pull/11782 Cleanups ======== - simplify Closure>>#arguments by using #collect: #11772 https://github.com/pharo-project/pharo/pull/11772 - Syntactic check a single >>> on executable comments #11784 https://github.com/pharo-project/pharo/pull/11784 - Remove obsolete code in RBCondition https://github.com/pharo-project/pharo/pull/11767 - Categorize refactorings and transformations #11783 https://github.com/pharo-project/pharo/pull/11783 - Cleanup-ClassParser-CDClassDefinitionModel #11787 https://github.com/pharo-project/pharo/pull/11787 - Move RBReplacePreview to NautilusRefactoring #11765 https://github.com/pharo-project/pharo/pull/11765 Comments ======== - Add more executable comments for Collection #11683 https://github.com/pharo-project/pharo/pull/11683

Oct. 14, 2022