January 2022 - Pharo-dev - lists.pharo.org

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

by Marcus Denker

For more infos, see https://github.com/pharo-project/pharo/pulse Fixes ===== - MC Warning - Add #versions Getter #10696 https://github.com/pharo-project/pharo/pull/10696 - Fixes #10702 Printing method selector in windows title only if the selector is not nil #10713 https://github.com/pharo-project/pharo/pull/10713 - Integrate Roassal3 v0.9.9d #10716 https://github.com/pharo-project/pharo/pull/10716 - 10703-Collectionflattened-changed-semantics #10705 https://github.com/pharo-project/pharo/pull/10705 - 10678-Step-Over-fails-for-leaving-simple-accessors #10707 https://github.com/pharo-project/pharo/pull/10707 - Fixes #10673 by adding missing method method to display a MessageTally identified #10682 https://github.com/pharo-project/pharo/pull/10682 - use DoubleByteLayout and DoubleWordLayout #9792 https://github.com/pharo-project/pharo/pull/9792 Image Building ============== - align commit of external projects with its merged version #10697 https://github.com/pharo-project/pharo/pull/10697 - Updating bootstrap image to v1.7.8 #10694 https://github.com/pharo-project/pharo/pull/10694 Cleanup ======= - Fix-deprecated-hostWindowTitle #10711 https://github.com/pharo-project/pharo/pull/10711 - 10331-No-need-to-refer-to-transcript-in-executable-comments #10706 https://github.com/pharo-project/pharo/pull/10706 Comments ======== - fixes #10704. changed Random>>nextInt: to nextInteger: in class comments #10710 https://github.com/pharo-project/pharo/pull/10710

Jan. 17, 2022

Re: Helping with documentation

by stephane ducasse

> > On 1/13/22 06:14, stephane ducasse wrote: >>> On 12 Jan 2022, at 02:03, Jimmie Houchin <jlhouchin(a)gmail.com <mailto:jlhouchin@gmail.com>> wrote: >>> >>> I am going to be working my way through some Pharo docs. >>> >>> As I read the books I sometimes see some English that can be improved. >> Yes I noticed it too but Iâm running too fast and my english is not my native language so >> it is not good. > > Your English is just fine. Probably better than half of Americans. :) > But there are probably things that are definitely more noticeable to native English speakers. > > > But it is easy to make mistakes and hard to see your own mistakes. I regularly create documents and then let the stakeholders review for any mistakes. Frequently the stakeholders will sign off on it. Then days later come back with corrections. Proofreading is hard. Yes now I was reading french documents for a native english with really good french and I often ended rewriting a lot of details. >>> What is the proper procedure for doing so? >>> >>> Any pointers to documents to help with this greatly appreciated. >> Oh this is easy just send small PRs and I will read and integrate them. >> Thanks in advance because this is important to get better documentation. > > I have been a lazy Pharo user for a long time. I always found the Pharo environment productive and easy to use and never pursued properly learning to be a good Pharo user. I want to remedy that and work my way through several of the books. go go go go! Learning is fun. BTW you should rerun your benches with the new VM since it has some plugins that were missing. > I figure that is a good time to contribute like this. Oh yes! > > I will keep them coming as I work my way through the books. > > Good to be a contributing citizen. :) And you can really have an impact and feel good about it. Did you read Pharo with Style? I would like to extend it. I should review again the Smalltalk with Style book (it is really nice).

Jan. 14, 2022

Re: Helping with documentation

by Jimmie Houchin

On 1/13/22 06:14, stephane ducasse wrote: >> On 12 Jan 2022, at 02:03, Jimmie Houchin <jlhouchin(a)gmail.com> wrote: >> >> I am going to be working my way through some Pharo docs. >> >> As I read the books I sometimes see some English that can be improved. > Yes I noticed it too but Iâm running too fast and my english is not my native language so > it is not good. Your English is just fine. Probably better than half of Americans. :) But there are probably things that are definitely more noticeable to native English speakers. But it is easy to make mistakes and hard to see your own mistakes. I regularly create documents and then let the stakeholders review for any mistakes. Frequently the stakeholders will sign off on it. Then days later come back with corrections. Proofreading is hard. >> What is the proper procedure for doing so? >> >> Any pointers to documents to help with this greatly appreciated. > Oh this is easy just send small PRs and I will read and integrate them. > Thanks in advance because this is important to get better documentation. I have been a lazy Pharo user for a long time. I always found the Pharo environment productive and easy to use and never pursued properly learning to be a good Pharo user. I want to remedy that and work my way through several of the books. I figure that is a good time to contribute like this. I will keep them coming as I work my way through the books. Good to be a contributing citizen. :) Jimmie > S >> >> Thanks. >> >> >> Jimmie

Jan. 14, 2022

Re: Pharo VM Release - v9.0.11

by Tudor Girba

Awesome work! Thank you, Tudor > On Jan 13, 2022, at 5:44 PM, tesonep(a)gmail.com wrote: > > Hello, > I have released a new version of the Pharo VM for Pharo 9 and Pharo 10. This VM is accessible right now from Zero-Conf, updating it in the Pharo Launcher or using the usual downloads (as described in pharo.org/download) > > This version includes a series of minor bug fixes. > > Changelog: > > - Include FloatArrayPlugin in the build > - Updating SDL2 to 2.0.18 for OSX X86_64 > - Using Pharo 10 image as VMMaker image > - Fixing issue in message counting on non-JIT VM > > Thanks a lot, and any doubt please let me know. > Cheers, > > Pablo on behalf of the whole Pharo team. > > -- > Pablo Tesone. > tesonep(a)gmail.com -- feenk.com "To lead is not to demand things, it is to make them happen."

Jan. 13, 2022

Pharo VM Release - v9.0.11

by tesonep＠gmail.com

Hello, I have released a new version of the Pharo VM for Pharo 9 and Pharo 10. This VM is accessible right now from Zero-Conf, updating it in the Pharo Launcher or using the usual downloads (as described in pharo.org/download) This version includes a series of minor bug fixes. Changelog: - Include FloatArrayPlugin in the build - Updating SDL2 to 2.0.18 for OSX X86_64 - Using Pharo 10 image as VMMaker image - Fixing issue in message counting on non-JIT VM Thanks a lot, and any doubt please let me know. Cheers, Pablo on behalf of the whole Pharo team. -- Pablo Tesone. tesonep(a)gmail.com

Jan. 13, 2022

ESUG 2022 call for presentations & Call for student volunteers

by stephane ducasse

ESUG 2022 Novisad Serbia 22. â 26.8. https://esug.github.io/2022-Conference/call2022.html You can support the ESUG conference in many different ways: Sponsor the conference. New sponsoring packages are described at http://www.esug.org/supportesug/becomeasponsor/ <http://www.esug.org/supportesug/becomeasponsor/> Submit a talk, a software or a paper to one of the events. See below. Attend the conference. We'd like to beat the previous record of attendance (170 people at Amsterdam 2008)! Students can get free registration and hosting if they enroll into the the Student Volunteers program. See below. <>Developers Forum: International Smalltalk Developers Conference We are looking for YOUR experience on using Smalltalk. You will have 30 min for presentations and 45 min for hands-on tutorials. The list of topics for the normal talks and tutorials includes, but is not limited to the following: XP practices, Development tools, Experience reports Model driven development, Web development, Team management Meta-Modeling, Security, New libraries & frameworks Educational material, Embedded systems and robotics SOA and Web services, Interaction with other programming languages <>Teaching Pearls and Show us Your Business New this year!!! We added two types of sessions in addition to the regular talks and show us your projects sessions. Show your business 10 min session (Get prepared!!) Teaching pearls : we want some session on how to teach some design aspects. We want your tip and tricks to teach Smalltalk or OOP. We expect to have several 10 to 15 min sessions aggregated. <>How to submit? Make a Pull Request here https://github.com/ESUG/esug.github.io/tree/source/2022-Conference/talks Or but only if you are not connected to the worldâ¦ send an email to stephane.ducasse(a)inria.fr Title: [ESUG 2022] Please follow the template below the email will be automatically processed! Name: Email: Abstract: Bio: Call for Student Volunteers Student volunteers help keep the conference running smoothly; in return, they have free accommodations, while still having most of the time to enjoy the conference. Pay attention: the places are limited so do not wait till the last minute to apply. Conference details: Send an email to stephane.ducasse at inria.fr and serge.stinckwich at gmail.com with: title: [ESUG 2022 Student] name, gender, university/school, country, email address short description of you and why you are interested in participating For which period is accommodation covered? Accommodation is covered from Sunday 21 August until Friday 26 August 2022 (including nights from Sunday to Monday and from Thursday to Friday). Students will be hosted in student rooms. ESUG additionally covers for the lunches during the week and one dinner. Duties include handling registration as people arrive at the conference, filling coffee machines, collecting presentation slides for ESUG right after the presentation is given, being present at an information desk to answer questions, and generally being helpful. Student volunteering makes the conference better, takes a fairly small amount of time and doesn't significantly interfere with enjoying and learning from the conference. Please Note, this role requires discipline and constant attention to all attendees. Information about hotel Student Volunteer rooms are booked at (to be announced). If you are student volunteer, do not book yourself, we have arranged the booking already!

Jan. 13, 2022

Re: Helping with documentation

by stephane ducasse

> On 12 Jan 2022, at 02:03, Jimmie Houchin <jlhouchin(a)gmail.com> wrote: > > I am going to be working my way through some Pharo docs. > > As I read the books I sometimes see some English that can be improved. Yes I noticed it too but Iâm running too fast and my english is not my native language so it is not good. > > What is the proper procedure for doing so? > > Any pointers to documents to help with this greatly appreciated. Oh this is easy just send small PRs and I will read and integrate them. Thanks in advance because this is important to get better documentation. S > > > Thanks. > > > Jimmie

Jan. 13, 2022

Re: Array sum. is very slow

by Esteban Lorenzano

Nevertheless, I would like to stress that the usage of low level libraries to speed up what needs to fast is a correct approach in whatever language that exists, from old turbo pascal enabled an "asm" command to write directly assembly when needed to modern languages that implements their libraries in C and then use it... heck, even C libraries have parts written in assembly when needed! I do not see why we can not gain speed in the places where is needed through a primitive, a plugin or a FFI call. cheers! Esteban On Jan 12 2022, at 6:24 pm, tesonep(a)gmail.com wrote: > I have activated the plugin in the build for Pharo9, it will be available in the next release. > > It will be interesting to have a Float64 extension to it. > On Wed, Jan 12, 2022, 18:06 Marcus Denker <marcus.denker(a)inria.fr (mailto:marcus.denker@inria.fr)> wrote: > > > > > > > On 12 Jan 2022, at 17:38, Henrik Sperre Johansen <henrik.s.johansen(a)veloxit.no (mailto:henrik.s.johansen@veloxit.no)> wrote: > > > True! > > > Itâs a little bit of a naming conundrum, since the Â«FloatÂ» in Pharo is already 64-bit, but since weâre speaking Â«nativeÂ» arrays, > > > DoubleArray > > > would be the best, I guess. > > > > > > Speaking of, the related new (â¦ to me, anyways) DoubleByte/DoubleWordArray classes have incorrect definitions in Pharo 9 AFAICT- variableByte/WordSubclasses, instead of variableDoubleByte/variableDoubleWordSubclassesâ¦ > > > > We finally fixed this in Pharo10 2 days ago: https://github.com/pharo-project/pharo/pull/9792 > > > > Marcus

Jan. 12, 2022

Re: Array sum. is very slow

by tesonep＠gmail.com

I have activated the plugin in the build for Pharo9, it will be available in the next release. It will be interesting to have a Float64 extension to it. On Wed, Jan 12, 2022, 18:06 Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > On 12 Jan 2022, at 17:38, Henrik Sperre Johansen < > henrik.s.johansen(a)veloxit.no> wrote: > > True! > Itâs a little bit of a naming conundrum, since the Â«FloatÂ» in Pharo is > already 64-bit, but since weâre speaking Â«nativeÂ» arrays, > DoubleArray > would be the best, I guess. > > Speaking of, the related new (â¦ to me, anyways) DoubleByte/DoubleWordArray > classes have incorrect definitions in Pharo 9 AFAICT- > variableByte/WordSubclasses, instead of > variableDoubleByte/variableDoubleWordSubclassesâ¦ > > > > We finally fixed this in Pharo10 2 days ago: > https://github.com/pharo-project/pharo/pull/9792 > > Marcus >

Jan. 12, 2022

Re: Array sum. is very slow

by Marcus Denker

> On 12 Jan 2022, at 17:38, Henrik Sperre Johansen <henrik.s.johansen(a)veloxit.no> wrote: > > True! > Itâs a little bit of a naming conundrum, since the Â«FloatÂ» in Pharo is already 64-bit, but since weâre speaking Â«nativeÂ» arrays, > DoubleArray > would be the best, I guess. > > Speaking of, the related new (â¦ to me, anyways) DoubleByte/DoubleWordArray classes have incorrect definitions in Pharo 9 AFAICT- variableByte/WordSubclasses, instead of variableDoubleByte/variableDoubleWordSubclassesâ¦ We finally fixed this in Pharo10 2 days ago: https://github.com/pharo-project/pharo/pull/9792 <https://github.com/pharo-project/pharo/pull/9792> Marcus

Jan. 12, 2022