- Pharo-dev - lists.pharo.org

Pharo VM Release - v10.0.0

by tesonep＠gmail.com

Hello, we have released a new version of the Pharo VM for Pharo 11. 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) OBS packages are still in work and will come later. This is the new VM that will be stable for Pharo 11 release, it is also compatible with Pharo 10 images but it is not the default for Pharo 10. It has a lot of changes and improvements, as it is the result of more than a year and a half of improvements, clean-ups, and bug fixes. Changelog v10.0.0 - Slang (Smalltalk to C Translator) - Introducing a C AST to ease the generation of C Code - Having a Pretty Printer for C AST - Translation Tests - Fixing Translation Issues - Clear separation between Slang and VM code - Improving Cast generation - Clean Up: - Remove Old Bytecode Set - Remove Old Block Implementation - Simplification of the Primitives - Removing Unused / Old Code / Dead Code - Cleanup / Removal of Old Unused primitives - Removing Old FFI Implementation - Removing MT Experiment from the code base (Kept in own branch) - Fixing Compilation Warnings - Improving Type annotations to fix bugs in the translation / compilation - Removing Conditional Code on Old Configurations / Features - Renaming Concepts to be inline with Common terminology - Remove Newspeak, Multiple Bytecode and Old Memory Managers - Removing Unused Plugins - Tests - GNUification Tests - Tests for Math primitives including overflow and conversion testing. - Tests for comparison primitives (Equals / Not Equals / Less than / Less or Equals / Greater Than / Greater or Equals) - Testing Primitives for objects Pinned in Memory - Testing Math Primitives for Immediate Classes (SmallFloats / SmallIntegers) - Improving Simulation Infrastructure - Using Sista Bytecode in all Tests - Updating Unicorn version - Improving Machine Code emulation - Testing Image Read / Image Write - Using the same memory map in Tests and Execution - Testing Ephemerons - Become Primitives - Ephemeron - Fix for large ammounts - Make it available - Testing Signal Finalizations - Fixing Become Errors. - Fixing XRay Primitive - Single-Instruction Multiple-Data (SIMD) initial Support: - Initialization of new objects using SIMD (ARM64) - Adding Bytecode Extensions to support SIMD instructions - Adding Vector Registers - Vector Register bytecodes - Auto Localization of Interpreter loop variables and edge detection simplifying development and minimizing code - ImageReader / ImageWriter reification needed for Permanent Space. - Improving the Memory Map of the VM (Using constant positions) - Dependencies Improvements Thanks a lot, and any doubt please let us know. Cheers, Pablo on behalf of the whole Pharo team -- Pablo Tesone. tesonep(a)gmail.com

March 1, 2023

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

by Marcus Denker

We merged 24 PRs this week: Compiler ======== - Improve faulty parsing #12778 https://github.com/pharo-project/pharo/pull/12778 - Improve faulty parsing of cascades #12816 https://github.com/pharo-project/pharo/pull/12816 - Improve faulty parsing of assigments #12815 https://github.com/pharo-project/pharo/pull/12815 Features ======== - Introducing a Color Palette to cache the allocation of Color objects by tht UITheme #12771 https://github.com/pharo-project/pharo/pull/12771 - Add #closeTo: on sequenceable collection #12800 https://github.com/pharo-project/pharo/pull/12800 - Filter on substrings in DrTest #12823 https://github.com/pharo-project/pharo/pull/12823 - load equals packages #12616 https://github.com/pharo-project/pharo/pull/12616 - Debugger configuration toolbar improvements #467 https://github.com/pharo-spec/NewTools/pull/467 Fixes ===== - Update Roassal version v0.9.9m #12792 https://github.com/pharo-project/pharo/pull/12792 - Sync Zinc 17 February 2023 #12794 https://github.com/pharo-project/pharo/pull/12794 - 1279 merge menu should indicate the sense of the action #1680 https://github.com/pharo-vcs/iceberg/pull/1680 - Fixes: Committing with empty description can lead to problems #1681 #1682 https://github.com/pharo-vcs/iceberg/pull/1682 - Fixes testInstanceSideInitializeMethodNeedsToBeInInitializationProtocol #12797 https://github.com/pharo-project/pharo/pull/12797 Cleanups ======== - Remove #wantsSteps from object and uses #respondsTo: in the system wiâ¦ #12793 https://github.com/pharo-project/pharo/pull/12793 - Remove old unicode initializer #12803 https://github.com/pharo-project/pharo/pull/12803 - Rename bootstrap 3rd step to be the 2nd now #12812 https://github.com/pharo-project/pharo/pull/12812 - AthensPathBuilder should be abstract #12827 https://github.com/pharo-project/pharo/pull/12827 - Fix typo #12801 https://github.com/pharo-project/pharo/pull/12801 - extract return. fix: #12809 #12810 https://github.com/pharo-project/pharo/pull/12810 - Remove depreceted class reference #12808 https://github.com/pharo-project/pharo/pull/12808 - Condensation of source 2 #12799 https://github.com/pharo-project/pharo/pull/12799 - Condensation of sources 3 #12802 https://github.com/pharo-project/pharo/pull/12802 - replace == nil with ifNil:ifNotNil: #12814 https://github.com/pharo-project/pharo/pull/12814 - Cleanup: Condense Zodiac packages #12762 https://github.com/pharo-project/pharo/pull/12762

Feb. 24, 2023

Re: Fwd: [Pharo-users] Pharo accepted to Google Summer of Code 2023

by sean＠clipperadams.com

Great news!

Feb. 24, 2023

Fwd: [Pharo-users] Pharo accepted to Google Summer of Code 2023

by Marcus Denker

> Begin forwarded message: > > From: Sebastian Jordan Montano <sebastian.jordan(a)inria.fr> > Subject: [Pharo-users] Pharo accepted to Google Summer of Code 2023 > Date: 23 February 2023 at 16:53:22 CET > To: pharo-users <pharo-users(a)lists.pharo.org> > Reply-To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > > Hello! > We are happy to announce that we got accepted for this year Google Summer of Code! > This is really good for us because it helps to expand the impact of our technologies and to have more people involved in our community. > > Please share it on your social medias. I will put some links > - GSoc website https://summerofcode.withgoogle.com/ > - Gsoc website of Pharo organisation: https://www.gsocorganizations.dev/organization/pharo-consortium/ > - our gsoc page https://gsoc.pharo.org/ideas > > Cheers, > Sebastian Jordan in regard of the Pharo Consortium

Feb. 23, 2023

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

by Marcus Denker

We merged 42 PRs and closed 66 issues Fixes ===== - Unnecessary characters rule should be an information and not a warning #12764 https://github.com/pharo-project/pharo/pull/12764 - FIx #wantsSteps deprecated calls #12782 https://github.com/pharo-project/pharo/pull/12782 - Removing the TStDebuggerExtension trait from the dummy debugger presenter #463 https://github.com/pharo-spec/NewTools/pull/463 Tests ===== - add some Duration tests #12777 https://github.com/pharo-project/pharo/pull/12777 - 11368-Failing-on-CI-random-CoNarrowHistoryFetcherTesttestNarrowingReturnsSameElementsThatCallingDirectly #12768 https://github.com/pharo-project/pharo/pull/12768 - categorization tests should print culprints if any #12780 https://github.com/pharo-project/pharo/pull/12780 Documentation ============= - Missing class comment: BaselineOfBeacon #12640 https://github.com/pharo-project/pharo/pull/12640 - Missing class comment BaselineOfClap and lint issue #12642 https://github.com/pharo-project/pharo/pull/12642 Cleanup ======= - Adjust #initialize categorization cases #12638 https://github.com/pharo-project/pharo/pull/12638 - Remove BlueInk packages #12612 https://github.com/pharo-project/pharo/pull/12612 - use String>>streamContens: and assert:equals: #12786 https://github.com/pharo-project/pharo/pull/12786 - 29 of the kind Cleanup: Condense SUnit packages #12630 https://github.com/pharo-project/pharo/pull/12630

Feb. 17, 2023

Re: PhEP: Underscores in Numeric Literals

by Noury Bouraqadi

I like it. I assume that the enhancement will include converting strings to numbers '10_000' asNumber = 10_000 Noury On Feb 14 2023, at 9:30 am, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > +1 > > > El 13 feb. 2023, a las 20:37, Daniel Slomovits <daniels220(a)gmail.com (mailto:daniels220@gmail.com)> escribiÃ³: > > Seems reasonable to me. I was just wishing for such a thing for exactly the reason you mention (keeping track of zeroes in large integer literals). AFAICT you've done a pretty good job laying out the possible error conditions. I think your option 1 makes senseâthe error-prone-ness is the sort of thing that could happen in theory, but I'm not too worried about in practice. Or option 2 is fine, I'm just not familiar enough with the parser to know how much harder it might be to implement. > > On Mon, Feb 13, 2023 at 1:54 PM Privat, Jean <privat.jean(a)uqam.ca (mailto:privat.jean@uqam.ca)> wrote: > > > This PhEP describes the extension of Pharo numeric literals to accepts (and ignore) underscore characters (`_` ASCII 95). > > > > > > Many languages (including Python https://peps.python.org/pep-0515/ , Java https://docs.oracle.com/javase/7/docs/technotes/guides/language/underscores… or Ruby) accept some forms of numeric literal that ignore _. > > > The idea is to permit long literals that are still readable, eg. `1_000_000_000` is easier for a human than `100000000` especially since in the previous literal a zero is missing (I'm a tricky deceitful fellow). > > > The details of the proposal are in the PR: https://github.com/pharo-project/pheps/pull/16 > > > -- > > > Jean Privat > > > > > > > >

Feb. 14, 2023

Re: PhEP: Underscores in Numeric Literals

by Guillermo Polito

+1 > El 13 feb. 2023, a las 20:37, Daniel Slomovits <daniels220(a)gmail.com> escribiÃ³: > > Seems reasonable to me. I was just wishing for such a thing for exactly the reason you mention (keeping track of zeroes in large integer literals). AFAICT you've done a pretty good job laying out the possible error conditions. I think your option 1 makes senseâthe error-prone-ness is the sort of thing that could happen in theory, but I'm not too worried about in practice. Or option 2 is fine, I'm just not familiar enough with the parser to know how much harder it might be to implement. > > On Mon, Feb 13, 2023 at 1:54 PM Privat, Jean <privat.jean(a)uqam.ca <mailto:privat.jean@uqam.ca>> wrote: > This PhEP describes the extension of Pharo numeric literals to accepts (and ignore) underscore characters (`_` ASCII 95). > > Many languages (including Python https://peps.python.org/pep-0515/ <https://peps.python.org/pep-0515/> , Java https://docs.oracle.com/javase/7/docs/technotes/guides/language/underscores… <https://docs.oracle.com/javase/7/docs/technotes/guides/language/underscores…> or Ruby) accept some forms of numeric literal that ignore _. > > The idea is to permit long literals that are still readable, eg. `1_000_000_000` is easier for a human than `100000000` especially since in the previous literal a zero is missing (I'm a tricky deceitful fellow). > > The details of the proposal are in the PR: https://github.com/pharo-project/pheps/pull/16 <https://github.com/pharo-project/pheps/pull/16> > > -- > Jean Privat

Feb. 14, 2023

Re: PhEP: Underscores in Numeric Literals

by Daniel Slomovits

Seems reasonable to me. I was just wishing for such a thing for exactly the reason you mention (keeping track of zeroes in large integer literals). AFAICT you've done a pretty good job laying out the possible error conditions. I think your option 1 makes senseâthe error-prone-ness is the sort of thing that could happen in theory, but I'm not too worried about in practice. Or option 2 is fine, I'm just not familiar enough with the parser to know how much harder it might be to implement. On Mon, Feb 13, 2023 at 1:54 PM Privat, Jean <privat.jean(a)uqam.ca> wrote: > This PhEP describes the extension of Pharo numeric literals to accepts > (and ignore) underscore characters (`_` ASCII 95). > > Many languages (including Python https://peps.python.org/pep-0515/ , Java > https://docs.oracle.com/javase/7/docs/technotes/guides/language/underscores… > or Ruby) accept some forms of numeric literal that ignore _. > > The idea is to permit long literals that are still readable, eg. > `1_000_000_000` is easier for a human than `100000000` especially since in > the previous literal a zero is missing (I'm a tricky deceitful fellow). > > The details of the proposal are in the PR: > https://github.com/pharo-project/pheps/pull/16 > > -- > Jean Privat

Feb. 13, 2023

PhEP: Underscores in Numeric Literals

by Privat, Jean

This PhEP describes the extension of Pharo numeric literals to accepts (and ignore) underscore characters (`_` ASCII 95). Many languages (including Python https://peps.python.org/pep-0515/ , Java https://docs.oracle.com/javase/7/docs/technotes/guides/language/underscores… or Ruby) accept some forms of numeric literal that ignore _. The idea is to permit long literals that are still readable, eg. `1_000_000_000` is easier for a human than `100000000` especially since in the previous literal a zero is missing (I'm a tricky deceitful fellow). The details of the proposal are in the PR: https://github.com/pharo-project/pheps/pull/16 -- Jean Privat

Feb. 13, 2023

ESUG 2023 Call for participation

by stephane ducasse

ESUG 2023 Call for Presentations 28.8.2023 to 01.9.2023 Lyon France https://esug.github.io https://esug.github.io/2023-Conference/conf2023.html ESUG is the premium and fun conference around smalltalk technologies. 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/ - 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 (180 people at Koln 2019)! - 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/2023-Conference/talks [Or but only if you are not connected to the worldâ¦ send an email to stephane.ducasse(a)inria.fr] Title: [ESUG 2023] 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 Oleksandr Zaitsev <olk.zaytsev(a)gmail.com> with: Title: [ESUG 2023 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 27.8.2023 to 01.9.2023 (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!

Feb. 11, 2023