- Pharo-dev - lists.pharo.org

Re: [ANN] Pharo 11 Released !

by Guillermo Polito

++1 !! :) > El 11 may. 2023, a las 14:02, Gabriel Cotelli <g.cotelli(a)gmail.com> escribiÃ³: > > Congratulations on the new release. Now it's time to adapt the libraries and check that continue working with this version :P > > I think you need to update also https://github.com/pharo-project/pharo/releases <https://github.com/pharo-project/pharo/releases> to tag the commit used to produce the released image. > > Regards, > Gabriel > > On Thu, May 11, 2023 at 8:39â¯AM Esteban Lorenzano <estebanlm(a)netc.eu <mailto:estebanlm@netc.eu>> wrote: > Dear Pharo users and dynamic language lovers: > > We have released Pharo <https://pharo.org/> version 11! > What is Pharo? > > Pharo is a pure object-oriented programming language and a powerful environment focused on simplicity and immediate feedback. > > > > Simple & powerful language: No constructors, no types declaration, no interfaces, no primitive types. Yet a powerful and elegant language with a full syntax fitting in one postcard! Pharo is objects and messages all the way down. > Live, immersive environment: Immediate feedback at any moment of your development: Developing, testing, debugging. Even in production environments, you will never be stuck in compiling and deploying steps again! > Amazing debugging experience: Pharo environment includes a debugger unlike anything you've seen before. It allows you to step through code, restart the execution of methods, create methods on the fly, and much more! > Pharo is yours: Pharo is made by an incredible community, with more than 100 contributors for the last revision of the platform and hundreds of people constantly contributing with frameworks and libraries. > Fully open-source: Pharo full stack is released under MIT <https://opensource.org/licenses/MIT> License and available on GitHub <https://github.com/pharo-project/pharo> > ... more on the Pharo Features page <http://www.pharo.org/features>. > > In this iteration of Pharo, we continue working on our objectives of improvement, clean-up and modularization. Also, we included a number of usability and speed improvements. A complete list of changes and improvements is available in our Changelog <https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo110Chang…> > Some highlights of this amazing version: > Highlights > > Tools > Iceberg (the git client/VCS control tool) has received a lot of tweaks and fixes to work better with GitHub and other Git services. > Our debugger now incorporates lots of tweaks and notably the capability of adding bindings in the context interaction model. > The is a new implementation of rewrite tools and improved refactoring support. > There is a new tool: The Document Browser, which presents Microdown (markdown compatible) documents placed on the web or locally. > New Tools presented in Calypso (the System Browser) and additional extended Inspectors. > All versions of NewTools, Spec, Roassal and Microdown have been updated with their respective bug fixes and improvements. > System > Extended Full Blocks and Constant Clock closures support. > Additional Inlining and optimizations > Bug Fixes and Clean up. > Ephemeron Finalization support. > Virtual machine > Ephemerons Production Ready. > Initial support for Single-Instruction Multiple-Data (SIMD). > Third-Party Dependency Update (Newer versions, Graphic Libraries using Hardware Acceleration). > Clean Ups: Remove lots of old code, notably old experiments, and dead code. > Development Effort > > This new version is the result of 1412 Pull Requests integrated just in the Pharo repository. We have closed 972 issues and received contributions from more than 70 different contributors. We have also a lot of work in the separate projects that are included in each Pharo release: > > http://github.com/pharo-spec/NewTools <https://github.com/pharo-spec/NewTools> > http://github.com/pharo-spec/NewTools-DocumentBrowser <https://github.com/pharo-spec/NewTools-DocumentBrowser> > http://github.com/pharo-spec/Spec <https://github.com/pharo-spec/Spec> > http://github.com/pharo-vcs/Iceberg <https://github.com/pharo-vcs/Iceberg> > http://github.com/ObjectProfile/Roassal3 <https://github.com/ObjectProfile/Roassal3> > http://github.com/pillar-markup/Microdown <https://github.com/pillar-markup/Microdown> > http://github.com/pillar-markup/BeautifulComments <https://github.com/pillar-markup/BeautifulComments> > http://github.com/pharo-project/pharo-vm <https://github.com/pharo-project/pharo-vm> > Contributors > > We always say Pharo is yours. It is yours because we made it for you, but most importantly because it is made by the invaluable contributions of our great community (yourself). A large community of people from all around the world contributed to Pharo 11.0 by making pull requests, reporting bugs, participating in discussion threads, providing feedback, and a lot of helpful tasks in all our community channels. Thank you all for your contributions. > > The Pharo Team > > Discover Pharo: https://pharo.org/features <https://pharo.org/features> > Try Pharo: http://pharo.org/download <http://pharo.org/download> > Learn Pharo: http://pharo.org/documentation <http://pharo.org/documentation>

May 12, 2023

Re: [ANN] Pharo 11 Released !

by Gabriel Cotelli

Congratulations on the new release. Now it's time to adapt the libraries and check that continue working with this version :P I think you need to update also https://github.com/pharo-project/pharo/releases to tag the commit used to produce the released image. Regards, Gabriel On Thu, May 11, 2023 at 8:39â¯AM Esteban Lorenzano <estebanlm(a)netc.eu> wrote: > Dear Pharo users and dynamic language lovers: > > We have released Pharo <https://pharo.org/> version 11! > What is Pharo? > Pharo is a pure object-oriented programming language and a powerful > environment focused on simplicity and immediate feedback. > > > > - Simple & powerful language: No constructors, no types declaration, > no interfaces, no primitive types. Yet a powerful and elegant language with > a full syntax fitting in one postcard! Pharo is objects and messages all > the way down. > - Live, immersive environment: Immediate feedback at any moment of > your development: Developing, testing, debugging. Even in production > environments, you will never be stuck in compiling and deploying steps > again! > - Amazing debugging experience: Pharo environment includes a debugger > unlike anything you've seen before. It allows you to step through code, > restart the execution of methods, create methods on the fly, and much more! > - Pharo is yours: Pharo is made by an incredible community, with more > than 100 contributors for the last revision of the platform and hundreds of > people constantly contributing with frameworks and libraries. > - Fully open-source: Pharo full stack is released under MIT > <https://opensource.org/licenses/MIT> License and available on GitHub > <https://github.com/pharo-project/pharo> > > ... more on the Pharo Features page <http://www.pharo.org/features>. > > In this iteration of Pharo, we continue working on our objectives of > improvement, clean-up and modularization. Also, we included a number of > usability and speed improvements. A complete list of changes and > improvements is available in our Changelog > <https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo110Chang…> > > Some highlights of this amazing version: > Highlights > Tools > > - Iceberg (the git client/VCS control tool) has received a lot of > tweaks and fixes to work better with GitHub and other Git services. > - Our debugger now incorporates lots of tweaks and notably the > capability of adding bindings in the context interaction model. > - The is a new implementation of rewrite tools and improved > refactoring support. > - There is a new tool: The Document Browser, which presents Microdown > (markdown compatible) documents placed on the web or locally. > - New Tools presented in Calypso (the System Browser) and additional > extended Inspectors. > - All versions of NewTools, Spec, Roassal and Microdown have been > updated with their respective bug fixes and improvements. > > System > > - Extended Full Blocks and Constant Clock closures support. > - Additional Inlining and optimizations > - Bug Fixes and Clean up. > - Ephemeron Finalization support. > > Virtual machine > > - Ephemerons Production Ready. > - Initial support for Single-Instruction Multiple-Data (SIMD). > - Third-Party Dependency Update (Newer versions, Graphic Libraries > using Hardware Acceleration). > - Clean Ups: Remove lots of old code, notably old experiments, and > dead code. > > Development Effort > This new version is the result of 1412 Pull Requests integrated just in > the Pharo repository. We have closed 972 issues and received contributions > from more than 70 different contributors. We have also a lot of work in the > separate projects that are included in each Pharo release: > > > - http://github.com/pharo-spec/NewTools > <https://github.com/pharo-spec/NewTools> > - http://github.com/pharo-spec/NewTools-DocumentBrowser > <https://github.com/pharo-spec/NewTools-DocumentBrowser> > - http://github.com/pharo-spec/Spec > <https://github.com/pharo-spec/Spec> > - http://github.com/pharo-vcs/Iceberg > <https://github.com/pharo-vcs/Iceberg> > - http://github.com/ObjectProfile/Roassal3 > <https://github.com/ObjectProfile/Roassal3> > - http://github.com/pillar-markup/Microdown > <https://github.com/pillar-markup/Microdown> > - http://github.com/pillar-markup/BeautifulComments > <https://github.com/pillar-markup/BeautifulComments> > - http://github.com/pharo-project/pharo-vm > <https://github.com/pharo-project/pharo-vm> > > Contributors > We always say Pharo is yours. It is yours because we made it for you, but > most importantly because it is made by the invaluable contributions of our > great community (yourself). A large community of people from all around the > world contributed to Pharo 11.0 by making pull requests, reporting bugs, > participating in discussion threads, providing feedback, and a lot of > helpful tasks in all our community channels. Thank you all for your > contributions. > > The Pharo Team > > Discover Pharo: https://pharo.org/features > Try Pharo: http://pharo.org/download > Learn Pharo: http://pharo.org/documentation >

May 11, 2023

Re: [ANN] Pharo 11 Released !

by Santiago Bragagnolo

Partyyy! Thanks to all who made this new release possible! [image: image.png] El jue, 11 may 2023 a las 13:39, Esteban Lorenzano (<estebanlm(a)netc.eu>) escribiÃ³: > Dear Pharo users and dynamic language lovers: > > We have released Pharo <https://pharo.org/> version 11! > What is Pharo? > Pharo is a pure object-oriented programming language and a powerful > environment focused on simplicity and immediate feedback. > > > > - Simple & powerful language: No constructors, no types declaration, > no interfaces, no primitive types. Yet a powerful and elegant language with > a full syntax fitting in one postcard! Pharo is objects and messages all > the way down. > - Live, immersive environment: Immediate feedback at any moment of > your development: Developing, testing, debugging. Even in production > environments, you will never be stuck in compiling and deploying steps > again! > - Amazing debugging experience: Pharo environment includes a debugger > unlike anything you've seen before. It allows you to step through code, > restart the execution of methods, create methods on the fly, and much more! > - Pharo is yours: Pharo is made by an incredible community, with more > than 100 contributors for the last revision of the platform and hundreds of > people constantly contributing with frameworks and libraries. > - Fully open-source: Pharo full stack is released under MIT > <https://opensource.org/licenses/MIT> License and available on GitHub > <https://github.com/pharo-project/pharo> > > ... more on the Pharo Features page <http://www.pharo.org/features>. > > In this iteration of Pharo, we continue working on our objectives of > improvement, clean-up and modularization. Also, we included a number of > usability and speed improvements. A complete list of changes and > improvements is available in our Changelog > <https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo110Chang…> > > Some highlights of this amazing version: > Highlights > Tools > > - Iceberg (the git client/VCS control tool) has received a lot of > tweaks and fixes to work better with GitHub and other Git services. > - Our debugger now incorporates lots of tweaks and notably the > capability of adding bindings in the context interaction model. > - The is a new implementation of rewrite tools and improved > refactoring support. > - There is a new tool: The Document Browser, which presents Microdown > (markdown compatible) documents placed on the web or locally. > - New Tools presented in Calypso (the System Browser) and additional > extended Inspectors. > - All versions of NewTools, Spec, Roassal and Microdown have been > updated with their respective bug fixes and improvements. > > System > > - Extended Full Blocks and Constant Clock closures support. > - Additional Inlining and optimizations > - Bug Fixes and Clean up. > - Ephemeron Finalization support. > > Virtual machine > > - Ephemerons Production Ready. > - Initial support for Single-Instruction Multiple-Data (SIMD). > - Third-Party Dependency Update (Newer versions, Graphic Libraries > using Hardware Acceleration). > - Clean Ups: Remove lots of old code, notably old experiments, and > dead code. > > Development Effort > This new version is the result of 1412 Pull Requests integrated just in > the Pharo repository. We have closed 972 issues and received contributions > from more than 70 different contributors. We have also a lot of work in the > separate projects that are included in each Pharo release: > > > - http://github.com/pharo-spec/NewTools > <https://github.com/pharo-spec/NewTools> > - http://github.com/pharo-spec/NewTools-DocumentBrowser > <https://github.com/pharo-spec/NewTools-DocumentBrowser> > - http://github.com/pharo-spec/Spec > <https://github.com/pharo-spec/Spec> > - http://github.com/pharo-vcs/Iceberg > <https://github.com/pharo-vcs/Iceberg> > - http://github.com/ObjectProfile/Roassal3 > <https://github.com/ObjectProfile/Roassal3> > - http://github.com/pillar-markup/Microdown > <https://github.com/pillar-markup/Microdown> > - http://github.com/pillar-markup/BeautifulComments > <https://github.com/pillar-markup/BeautifulComments> > - http://github.com/pharo-project/pharo-vm > <https://github.com/pharo-project/pharo-vm> > > Contributors > We always say Pharo is yours. It is yours because we made it for you, but > most importantly because it is made by the invaluable contributions of our > great community (yourself). A large community of people from all around the > world contributed to Pharo 11.0 by making pull requests, reporting bugs, > participating in discussion threads, providing feedback, and a lot of > helpful tasks in all our community channels. Thank you all for your > contributions. > > The Pharo Team > > Discover Pharo: https://pharo.org/features > Try Pharo: http://pharo.org/download > Learn Pharo: http://pharo.org/documentation >

May 11, 2023

[ANN] Pharo 11 Released !

by Esteban Lorenzano

Dear Pharo users and dynamic language lovers: We have released Pharo (https://pharo.org/) version 11! What is Pharo? Pharo is a pure object-oriented programming language and a powerful environment focused on simplicity and immediate feedback. Simple & powerful language: No constructors, no types declaration, no interfaces, no primitive types. Yet a powerful and elegant language with a full syntax fitting in one postcard! Pharo is objects and messages all the way down. Live, immersive environment: Immediate feedback at any moment of your development: Developing, testing, debugging. Even in production environments, you will never be stuck in compiling and deploying steps again! Amazing debugging experience: Pharo environment includes a debugger unlike anything you've seen before. It allows you to step through code, restart the execution of methods, create methods on the fly, and much more! Pharo is yours: Pharo is made by an incredible community, with more than 100 contributors for the last revision of the platform and hundreds of people constantly contributing with frameworks and libraries. Fully open-source: Pharo full stack is released under MIT (https://opensource.org/licenses/MIT) License and available on GitHub (https://github.com/pharo-project/pharo) ... more on the Pharo Features page (http://www.pharo.org/features) In this iteration of Pharo, we continue working on our objectives of improvement, clean-up and modularization. Also, we included a number of usability and speed improvements. A complete list of changes and improvements is available in our Changelog (https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo110Chang…) Some highlights of this amazing version: Highlights Tools Iceberg (the git client/VCS control tool) has received a lot of tweaks and fixes to work better with GitHub and other Git services. Our debugger now incorporates lots of tweaks and notably the capability of adding bindings in the context interaction model. The is a new implementation of rewrite tools and improved refactoring support. There is a new tool: The Document Browser, which presents Microdown (markdown compatible) documents placed on the web or locally. New Tools presented in Calypso (the System Browser) and additional extended Inspectors. All versions of NewTools, Spec, Roassal and Microdown have been updated with their respective bug fixes and improvements. System Extended Full Blocks and Constant Clock closures support. Additional Inlining and optimizations Bug Fixes and Clean up. Ephemeron Finalization support. Virtual machine Ephemerons Production Ready. Initial support for Single-Instruction Multiple-Data (SIMD). Third-Party Dependency Update (Newer versions, Graphic Libraries using Hardware Acceleration). Clean Ups: Remove lots of old code, notably old experiments, and dead code. Development Effort This new version is the result of 1412 Pull Requests integrated just in the Pharo repository. We have closed 972 issues and received contributions from more than 70 different contributors. We have also a lot of work in the separate projects that are included in each Pharo release: http://github.com/pharo-spec/NewTools (https://github.com/pharo-spec/NewTools) http://github.com/pharo-spec/NewTools-DocumentBrowser (https://github.com/pharo-spec/NewTools-DocumentBrowser) http://github.com/pharo-spec/Spec (https://github.com/pharo-spec/Spec) http://github.com/pharo-vcs/Iceberg (https://github.com/pharo-vcs/Iceberg) http://github.com/ObjectProfile/Roassal3 (https://github.com/ObjectProfile/Roassal3) http://github.com/pillar-markup/Microdown (https://github.com/pillar-markup/Microdown) http://github.com/pillar-markup/BeautifulComments (https://github.com/pillar-markup/BeautifulComments) http://github.com/pharo-project/pharo-vm (https://github.com/pharo-project/pharo-vm) Contributors We always say Pharo is yours. It is yours because we made it for you, but most importantly because it is made by the invaluable contributions of our great community (yourself). A large community of people from all around the world contributed to Pharo 11.0 by making pull requests, reporting bugs, participating in discussion threads, providing feedback, and a lot of helpful tasks in all our community channels. Thank you all for your contributions. The Pharo Team Discover Pharo: https://pharo.org/features Try Pharo: http://pharo.org/download Learn Pharo: http://pharo.org/documentation

May 11, 2023

Pharo contribution Jenkins end of service

by Christophe Demarey

Hi all, Some years ago, we provided a Jenkins instance to check the health / quality of projects that are not in Pharo core but important for the community: https://ci.inria.fr/pharo-contribution/ <https://ci.inria.fr/pharo-contribution/> Since, we moved to GitHub and GitHub actions are mainly used to achieve the same goal. Therefore there is no more reason to keep this service. Thatâs why we decided to stop the Pharo contribution Jenkins on 12th June 2023. If you need to save some data (job artefacts, job setup), let us know. The server is now up but it has not been updated since a while and can stop working from time to time. On 12th June 2023, we will shutdown the server and all data will be removed. The Pharo team.

May 11, 2023

Re: Pharo VM Release - v10.0.5

by Noury Bouraqadi

Many thanks to the Pharo team! Noury On May 5 2023, at 7:22 pm, tesonep(a)gmail.com wrote: > 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 (http://pharo.org/download)) Also, OBS packages are ready to be updated using your distribution package manager. > > This is the new VM that will be stable for Pharo 11 release and Pharo 12 alpha, it is also compatible with Pharo 10 images but it is not the default for Pharo 10. > Changelog > > * Testing scavenger tenuring by @PalumboN in https://github.com/pharo-project/pharo-vm/pull/588 > * Deleting Pharo image from the VM repo by @jordanmontt in https://github.com/pharo-project/pharo-vm/pull/591 > * Cleaning Up Third Party Libraries by @tesonep in https://github.com/pharo-project/pharo-vm/pull/581 > > **Full Changelog**: https://github.com/pharo-project/pharo-vm/compare/v10.0.4...v10.0.5 > > 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 (mailto:tesonep@gmail.com) > >

May 6, 2023

Pharo VM Release - v10.0.5

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) Also, OBS packages are ready to be updated using your distribution package manager. This is the new VM that will be stable for Pharo 11 release and Pharo 12 alpha, it is also compatible with Pharo 10 images but it is not the default for Pharo 10. Changelog * Testing scavenger tenuring by @PalumboN in https://github.com/pharo-project/pharo-vm/pull/588 * Deleting Pharo image from the VM repo by @jordanmontt in https://github.com/pharo-project/pharo-vm/pull/591 * Cleaning Up Third Party Libraries by @tesonep in https://github.com/pharo-project/pharo-vm/pull/581 **Full Changelog**: https://github.com/pharo-project/pharo-vm/compare/v10.0.4...v10.0.5 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

May 5, 2023

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

by Marcus Denker

With some last fixes, Pharo11 now is ready for release, Pharo12 improvements continue, with a focus on Protocols/ClassOrganizer, Compiler, Code Completion and CompiledMethodTrailer/sourcePointer simplifications. For the later, these posts to the pharo-dev list have more details: [Pharo12] Simplify CompiledMethod trailer: just support fixed sourcePointers https://lists.pharo.org/empathy/thread/XBAX4TN2F2CBD6VCU4PCAB7KXKTOS5GU [Pharo12] Simpler sourcePointer encoding https://lists.pharo.org/empathy/thread/AZQ3JHTV22XNO5STSII62UJEVE3ANDFN [Pharo12] commentSourcePointer and Metaclass https://lists.pharo.org/empathy/thread/QBVM3DV4NDXETJUH7QVOZCZYGENFGLJB # Pharo11 - 13526-Attempt-to-release-a-shared-cairo-font-face #13574 https://github.com/pharo-project/pharo/pull/13574 - Fix wrong double click #13577 https://github.com/pharo-project/pharo/pull/13577 - Fix/filter #13589 https://github.com/pharo-project/pharo/pull/13589 - Debugger fixes #13592 https://github.com/pharo-project/pharo/pull/13592 - Add new welcomebrowser #13623 https://github.com/pharo-project/pharo/pull/13623 - Make protocol classification a setting #13615 https://github.com/pharo-project/pharo/pull/13615 # Pharo112 ## Clean Blocks - Clean blocks for announcement #13590 https://github.com/pharo-project/pharo/pull/13590 ## SystemOrganizer - Make Smalltalk environnement return a RPackageOrganizer #13403 https://github.com/pharo-project/pharo/pull/13403 - Remove references to SystemOrganization #13632 https://github.com/pharo-project/pharo/pull/13632 - Deprecate SystemOrganization #13497 https://github.com/pharo-project/pharo/pull/13497 ## Protocols / ClassOrganization - Cleanup protocol announcements in ClassOrganization #13646 https://github.com/pharo-project/pharo/pull/13646 - Test ClassOrganization>>#hasProtocol: #13644 https://github.com/pharo-project/pharo/pull/13644 - ClassOrganization classification cleanings #13373 https://github.com/pharo-project/pharo/pull/13373 - Ensure #addSelector:withMethod: classifies methods #13635 https://github.com/pharo-project/pharo/pull/13635 - Reduce cyclomatic complexity of #classify:under: #13630 https://github.com/pharo-project/pharo/pull/13630 - Do not reclassify already classified method #13621 https://github.com/pharo-project/pharo/pull/13621 - Simplify classify:under: #13604 https://github.com/pharo-project/pharo/pull/13604 - Remove ClassOrganization>>#protocolNameOfElement:ifAbsent: #13605 https://github.com/pharo-project/pharo/pull/13605 - Improve #renameProtocolNamed:toBe: #13466 https://github.com/pharo-project/pharo/pull/13466 - Do not rely on #protocolNameOfElement: in Traits #13582 https://github.com/pharo-project/pharo/pull/13582 - Remove usage of #protocolNameOfElement:ifAbsent: in traits #13593 https://github.com/pharo-project/pharo/pull/13593 - Remove hack from ClassOrganization>>protocolNameOfElement: #13653 https://github.com/pharo-project/pharo/pull/13653 ## Improvements - rubric: doit actions on empty selection selects the current expression #13096 https://github.com/pharo-project/pharo/pull/13096 - Simplify code export #13624 https://github.com/pharo-project/pharo/pull/13624 ## Code Completion - Completion complete empty tokens #13638 https://github.com/pharo-project/pharo/pull/13638 - Autocompletion must replace from start of the word if case-insensitivâ¦ #13548 https://github.com/pharo-project/pharo/pull/13548 - Code Completion: multiple fixes on replacements annoying bugs #13625 https://github.com/pharo-project/pharo/pull/13625 - Completion: prepare for empty token #13636 https://github.com/pharo-project/pharo/pull/13636 - Complete super message send #13637 https://github.com/pharo-project/pharo/pull/13637 ## CompiledMethod trailer cleanup / sourcePointer - HEInstaller should take the trailerSize into account #13627 https://github.com/pharo-project/pharo/pull/13627 - this PR introduces CompiledMethod>>#clearSourcePointer and #sourcePointer: #13578 https://github.com/pharo-project/pharo/pull/13578 - Deprecated CompiledMethodTrailer #13579 https://github.com/pharo-project/pharo/pull/13579 - skip some SourceFileArrayTest #13585 https://github.com/pharo-project/pharo/pull/13585 - Fix-SourceFileArrayTest for new encoding #13596 https://github.com/pharo-project/pharo/pull/13596 - #sourceCodeAt: should return nil in failure case #13586 https://github.com/pharo-project/pharo/pull/13586 - Simpler sourcePointer encoding #13583 https://github.com/pharo-project/pharo/pull/13583 - Set #trailerSize to 5 #13580 https://github.com/pharo-project/pharo/pull/13580 - CommentSourcePointer-move-methods-down #13640 https://github.com/pharo-project/pharo/pull/13640 - move commentSourcePointer from ClassDescription to Class #13643 https://github.com/pharo-project/pharo/pull/13643 - fix BehaviorTest>>#testInstSize #13648 https://github.com/pharo-project/pharo/pull/13648 - Faster #setSourcePointer: #13645 https://github.com/pharo-project/pharo/pull/13645 ## Compiler - Add compiler option to not optimise special sends #13569 https://github.com/pharo-project/pharo/pull/13569 - Compiler: do generation #13541 https://github.com/pharo-project/pharo/pull/13541 - Cleanup-optionInlineRepeat-is-default #13614 https://github.com/pharo-project/pharo/pull/13614 - MethodMapTest-use-Compiler #13620 https://github.com/pharo-project/pharo/pull/13620 - Compiler: get requestor #13606 https://github.com/pharo-project/pharo/pull/13606 - AST: add a scanner state #13557 https://github.com/pharo-project/pharo/pull/13557 ## Cleanups / Tests - Remove some dead code in ChangeSet #13622 https://github.com/pharo-project/pharo/pull/13622 - Add test on CompiledCode>>#equivalentTo: #13595 https://github.com/pharo-project/pharo/pull/13595 - extract return from ifTrue:ifFalse: expression #13603 https://github.com/pharo-project/pharo/pull/13603 - extract return from ifTrue:ifFalse: expression #13601 https://github.com/pharo-project/pharo/pull/13601 - use nested and: expression instead of ifTrueifFalse #13611 https://github.com/pharo-project/pharo/pull/13611 - extract return from ifTrue:ifFalse: expression #13609 https://github.com/pharo-project/pharo/pull/13609

May 5, 2023

[Pharo12] commentSourcePointer and Metaclass

by Marcus Denker

Hi, up to Pharo11, the commentSourcePointer that is used to read and write the class comments was in ClassOrganization. In Pharo 12, we moved the commentSourcePointer to Class, Metaclass therefore has no empty commentSourcePointer anymore via itâs organizer. PR is mergedâ¦ these are of course more steps then you would think Started in Pharo11: - ix-tests-commentSourcePointer #11441 https://github.com/pharo-project/pharo/pull/11441 - Add commentSourcePointer to ClassDescription #11326 https://github.com/pharo-project/pharo/pull/11326 Pharo 12: - Set-CommentSourcepointer-ClassDescription #13171 https://github.com/pharo-project/pharo/pull/13171 - remove commentSourcePointer from ClassOrganization #13176 https://github.com/pharo-project/pharo/pull/13176 - CommentSourcePointer-move-methods-down #13640 https://github.com/pharo-project/pharo/pull/13640 - move commentSourcePointer from ClassDescription to Class #13643 https://github.com/pharo-project/pharo/pull/13643 - fix BehaviorTest>>#testInstSize #13648 https://github.com/pharo-project/pharo/pull/13648 and DONE. Moving ivars around in these classes is of course not easy, it can only be done with creating a PR by editing the code directly and then can be bootstapped, but you could not do that from a running image. (this explains why the commentSourcePointer was in ClassOrganization to start with, when it was introduced, this was the only place to put without major hassle) - the code is now much simpler to understand (Metaclass forwards all methods related to comments to #instanceSide) - it saves (a little bit) of memory (Smalltalk globals allClasses size * 8) bytes - is just one step to move merge ClassOrganization with ClassDescription, which will be a bit more relevant in terms of memory Marcus

May 4, 2023

Re: [Pharo12] Simplify CompiledMethod trailer: just support fixed sourcePointers

by Marcus Denker

The last PR now changes the trailer size to 5. https://github.com/pharo-project/pharo/pull/13580 <https://github.com/pharo-project/pharo/pull/13580> This way .changes/sources size can be 512GB. The most important things is, though, that this validates that we can change the space easily, e.g use 64bit and store some ObjectID... The fixed trailer does have an impact on speed for bytecode interpretation (via the Context). e.g. when looking for senders of special selectors, it has to fall back to use InstructionStream scanFor:, as the selectors are not in the literals. [#+ senders] bench Pharo11 : "'3.891 per second'" Pharo12 : "'4.913 per second'" This is some 25% faster, due to not having to instantiate a CompiledMethodTrailer for #endPC. Marcus > On 28 Apr 2023, at 11:07, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > We did (im Pharo12) a simplification of how method trailers are handled. Below is the class comment of the now Deprecated and empty > class CompiledMethodTrailer. > > The issue https://github.com/pharo-project/pharo/issues/13512 has a list of all the intermediate steps done. > > ========== > > CompiledMethodTrailer was removed in Pharo12 > > It was responsible for encoding and decoding various kinds of compiled method trailer data, but that had many downsides: > > â¢ variable length trailers forced often called methods like CompiledMethod>>#endPC to instantiate an instance > â¢ setting a sourcePointer that required a different length trailer (e.g embedding sources) needed to create a new compiled method and do a become > â¢ to avoid that, the compiler supported to use an existing trailer and delegated instance creation of CompiledMethod to it. > â¢ using 1 byte for the trailer kind lead to the need use Variable length encoding already for our ~40MB source file for some methods. > > > All in all, the CompiledMethodTrailer added a lot of complexity for nothing. > > What do we do now? > > â¢ use use a fixed-length trailer (see #trailerSize) > â¢ writing and reading that is not that complex (see #setSourcePointer, #sourcePointer:) > > Q: I used to hand a trailer to the compiler, what should I do now? > > The compiler now creates always CompiledMethods with a fixed, but empty trailer. Just use #sourcePointer to set it after. > > Q: I used to clear the trailer using #copyWithTrailerBytes:, what should I do now? > > There is now #cearSourcePointer. Just use #copy before if you want a copy. > > Q: I want to have a non-installed method, but with source code. > The compiler now sets a #source property (and setting a source pointer via #sourcePointer: removes it). > If you use the compiler, you need to do nothing special anymore! All methods come with source via the property by default. > > >

May 3, 2023