- Pharo-dev - lists.pharo.org

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

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

by Marcus Denker

We merged 16 PRs this week: Fixes ===== - 11671-MetaLinks-on-methods-with-no-return-statement-implicit-self-are-called-twice #11759 https://github.com/pharo-project/pharo/pull/11759 - Fix "undo" operation erroneously removing the dirty flag when undo operation performed after saving #11655 https://github.com/pharo-project/pharo/pull/11655 - fix 11709: DTRFTPlugin class missing even though #11513 was merged #11736 https://github.com/pharo-project/pharo/pull/11736 - Remove unused refactor #11738 https://github.com/pharo-project/pharo/pull/11738 - Fix RefactoringChangeTests on fluid #11741 https://github.com/pharo-project/pharo/pull/11741 - Class definition popup uses the default class syntax (fluid with the new default) #11737 https://github.com/pharo-project/pharo/pull/11737 - Debugger selection messed up when using breakpoints in a block #11733 #11734 https://github.com/pharo-project/pharo/pull/11734 Features ======== - Add a browser tool to see package dependencies #11700 https://github.com/pharo-project/pharo/pull/11700 Speed ===== - Removing the reification of TFSameThreadCall #11739 https://github.com/pharo-project/pharo/pull/11739 Documentation ============= - Add executable comments on Collection for do: and stream related #11699 https://github.com/pharo-project/pharo/pull/11699 Cleanups ======== - Improve compiler plugin implementation for P11 #11761 https://github.com/pharo-project/pharo/pull/11761 - Rename AddClass refactoring/transformation to InsertClass and cleanup #11757 https://github.com/pharo-project/pharo/pull/11757 - 11753-Enhance-Breakpoint-API-with-enabled-method #11758 https://github.com/pharo-project/pharo/pull/11758 - Move nameToDisplay from Refactoring-Changes to Ring-Definitions-Core #11751 https://github.com/pharo-project/pharo/pull/11751 - Replace nested conditions with guard close #11754 https://github.com/pharo-project/pharo/pull/11754 - Refactoring engine small cleanup #11746 https://github.com/pharo-project/pharo/pull/11746

Oct. 10, 2022

Sponsoring our new mooc

by stephane ducasse

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 not focus on Pharo but on object-oriented design, tests, design patterns. It will present - Test and test-driven - Essential aspects of OOP - Basic and universal principles - Double dispatch - Case studies in Pharo - Some design patterns - Some coding idioms and we will composed of 8 modules Currently it has around 50 lectures and we expect around 60 + exercises. You can access some drafts of the support here: https://rmod-files.lille.inria.fr/?dir=DesignCoffeeClub <https://rmod-files.lille.inria.fr/?dir=DesignCoffeeClub> The production cost of this mooc is around 200 K Euros financed by Inria and it will be filmed in January. We hope to deploy it in April or May 2023. The mooc will be produced in english (and may be dub in french). It occurred to me in this difficult time to find good developers that some of you may want to sponsor this mooc\to get exposure. You can be associated with some of the best OO teachers: me, Guillermo Polito and Pablo Tesone. We have cumulated more than 40 years of teaching experience. Several books... Yes at the end of the day we should sale a bit our expertise - check below our track record with the previous mooc. As a sponsor you will get your logo and links on all the supports: Slides and videos. Note that this mooc is designated to have a live time of 10 years or more. It is teaching fundamental points of OOP. So this is a unique opportunity to market your company to people wanted to learn advanced OOP Note that there are no other lectures like this one. We have two levels of sponsoring: 2000 Euros for platinum sponsor 1000 Euros for plain sponsor Let us know. Just a little reminder of the previous Mooc on Pharo. It has more than 8 years. For the record, some youtube videos (that we published after 4 years of running the pharo mooc) got more than 6000 views and this is by developers. We got around 10000 followers not counting the people watching the mooc on youtube and here are some of the testimonies we collected over the years. J'ai trouvÃ© Ã§a trÃ¨s intÃ©ressant, beaucoup plus que prÃ©vu ! je regrette de ne pas m'y Ãªtre mis plus tÃ´t. J'ai enfin l'impression de vraiment faire de la POO ! Ou Ã l'inverse je me rend que je n'en faisais pas vraiment... - Anonymous, 2019 I have just completed week seven of the Pharo Mooc (beginner and object oriented tracks) I am starting a redo of the Mooc with the web track (TinyBlog project). I have already learned so much ! I have spent the last 20 years or so in software development and, following this Mooc, I realized I hadnât really grasped the essence of object oriented design. - Anonymous Â« Really one of the best mooc I have ever attended. And I have attended quite a few (openSAP, openHPI). As an old fashioned ABAP developer I want to be reborn as Pharo developer in my next life :-) Â» - Anonymous Hi! I finished the MOOC some weeks ago and I would like to congratulate everybody involved! After a decade+ of Python programming I think I found my new favorite language :). I'm making a small Teapot server for Slack command bots, I'm goona push it to Github (yay Iceberg), if anyone is interested. - EduardoPadoan I just completed the @pharoproject Mooc the best investment I have ever made of my time. MAQBOOL Hey all - I've just finished the Mooc - thanks for an excellent course and a thouroughly interesting look at a new way to program :smile: Looking forward to starting to play with Pharo on some upcoming ideas I've had. - Tieryn As much as I thought I understand object-orientation, it is very clear NOW that without a truly useable Smalltalk, which Pharo is, it is impossible to really understand and exercise object-orientation. Thank you all soooo much. - Mike D. 06/12/2020 I finished the Pharo MOOC a few days ago. Thank you very much to Damien, Stephane, and Luc for their work on the material! I enjoyed it very much - Anonymous Hey all - I've just finished the Mooc - thanks for an excellent course and a thouroughly interesting look at a new way to program :smile: Looking forward to starting to play with Pharo on some upcoming ideas I've had ð3 - Anonymous I already had previous Smalltalk experience, but yes, I'm extremely happy Chapter 7 has been extremely fulfilling - Anonymous A general comment I wanted to make is that the MOOC so far has been great. Impressed with the quality and content, and grateful that it is available and free. Many thanks! - Aryeh IMHO the videos were very well done. I would even say shockingly well doneâ¦ for a bunch of programmers who are supposed to be clueless about design - SeanDeNigris - 10/26/2017 The more I learning about @pharoproject the more I appreciate it's beauty and simplicity, finally, object-oriented programming is done right - MAQBOOL Mooc absolument remarquable. Superbe voyage autour de Pharo. Le paradigme objet qui (re)prend enfin du sens ! - Anonymous - 01/03/2019

Oct. 5, 2022

Re: Recommendation for password encryption?

by sean＠clipperadams.com

Chris Muller wrote: > Ron Teitelbaum made a clever solution to resisting memory-scanning attacks Wow, that sounds really interesting! Probably overkill for my current use case, but happy to know thatâs available in case I ever need it. Thanks for the tip :)

Sept. 30, 2022