- Pharo-dev - lists.pharo.org

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

by Marcus Denker

We merged 32 PRs this week: Bugs ==== - InitializedSlot-check-default #12895 https://github.com/pharo-project/pharo/pull/12895 - correcting computation of sets of protocols to remove and add #12962 https://github.com/pharo-project/pharo/pull/12962 - 12955-TFStringType-is-leaking-when-allocates-the-string-for-calling-a-function #12956 https://github.com/pharo-project/pharo/pull/12956 - Fixing bugged undo-redo commands after using completion #12570 https://github.com/pharo-project/pharo/pull/12570 Improvements =========== - Speed up ClassVar>>#isReferenced #12930 https://github.com/pharo-project/pharo/pull/12930 - Add new attributes to SDL_MouseWheelEvent #12897 https://github.com/pharo-project/pharo/pull/12897 - Synch zinc zodiac #12932 https://github.com/pharo-project/pharo/pull/12932 - Add BaselineOf:>>#pharoVersionsFrom: #12908 https://github.com/pharo-project/pharo/pull/12908 - Ensure #setUp is classified in running #12907 https://github.com/pharo-project/pharo/pull/12907 Compiler ======== - RBCodeSnippets test decompilation #12901 https://github.com/pharo-project/pharo/pull/12901 - no more RBScanner errorBlock #12900 https://github.com/pharo-project/pharo/pull/12900 - Improve faulty AST fromatting by RBSimpleFormatter #12902 https://github.com/pharo-project/pharo/pull/12902 - better fix for #12858: check isTempVariable #12971 https://github.com/pharo-project/pharo/pull/12971 - add RBCodeSnippetTest>>testCompileWithRequestor #12958 https://github.com/pharo-project/pharo/pull/12958 - Improve faulty compiling - small snippets cleanup #12947 https://github.com/pharo-project/pharo/pull/12947 - Improve faulty compiling: test shadowed reserved variables #12960 https://github.com/pharo-project/pharo/pull/12960 - Improve faulty reporting: IconStyler #12934 https://github.com/pharo-project/pharo/pull/12934 - Improve faulty compilation - semantic error #12919 https://github.com/pharo-project/pharo/pull/12919 - Improve faulty parsing. Add semantic snippets #12909 https://github.com/pharo-project/pharo/pull/12909 Syntax Highlighter ================== - Simplify styler #12952 https://github.com/pharo-project/pharo/pull/12952 - Improve styler #12915 https://github.com/pharo-project/pharo/pull/12915 - Add regression test to Shout #12974 https://github.com/pharo-project/pharo/pull/12974 - Loop imbricated styles + remove dead code #12964 https://github.com/pharo-project/pharo/pull/12964 - Remove dead code in SHTextStyler #12949 https://github.com/pharo-project/pharo/pull/12949 - Shout: Manage syntax highlight of dynamic array #12953 https://github.com/pharo-project/pharo/pull/12953 - Shout:â¯Rename some styles #12945 https://github.com/pharo-project/pharo/pull/12945 Tools ===== - new class SycInspectNodeCommand to simply inspect an AST node #12904 https://github.com/pharo-project/pharo/pull/12904 - 12807-Executable-comment-syntax-error-leads-to-CI-crash #12894 https://github.com/pharo-project/pharo/pull/12894 - Fix Calypso browsing unloaded package artifacts from Iceberg #12425 https://github.com/pharo-project/pharo/pull/12425 Cleanups ======== remove method Object asOrderedCollection #12852 https://github.com/pharo-project/pharo/pull/12852 Trivial ======= - Fix categories in PaSimpleMatrixExampleTest #12937 https://github.com/pharo-project/pharo/pull/12937 Pharo10 ======= - backport-issue-12955: TFStringType is leaking when allocates the string for calling a function #12966 https://github.com/pharo-project/pharo/pull/12966

March 13, 2023

Re: [ANN] preparing for release, freezing enhancements :)

by Christophe Demarey

Hi Jean, > Le 13 mars 2023 Ã 12:33, Privat, Jean <privat.jean(a)uqam.ca> a Ã©crit : > >> what would be the rational behind having a main branch as default instead a branch with the version we are working on? > > As with most naming issues in CS, this does not change a lot in the grand order of things. > However, I believe that using a standard nomenclature could help newcomers and casual developers. > >> I could consider start having branchs named, e.g. pharo12-dev, to differentiate it from the stable branch, but since that would mean to change a lot of tools that depend on the naming, it has to be considered careful > > pharo12-dev is great. > but since there is only main dev branch, maybe the `pharo12-` part is not that useful. > but since it's a git repository, maybe use a conventional name for "the main development branch" that is master or main. In git, master / main branch does not mean it is the main or current development branch. It is just the default branch name of a new repository. It could be used as a development branch as well as an integration branch (e.g. gitflow). I would not use main for the current dev branch but rather pharoxx or pharoxx-dev. Christophe

March 13, 2023

Re: [ANN] preparing for release, freezing enhancements :)

by Privat, Jean

> As every year, we try to release in april. Now if this will be there or not, it always depends on several things, but for now we are pretty confident on it :P Nice. Spring is related to renewal or something :) > what would be the rational behind having a main branch as default instead a branch with the version we are working on? As with most naming issues in CS, this does not change a lot in the grand order of things. However, I believe that using a standard nomenclature could help newcomers and casual developers. > I could consider start having branchs named, e.g. pharo12-dev, to differentiate it from the stable branch, but since that would mean to change a lot of tools that depend on the naming, it has to be considered careful pharo12-dev is great. but since there is only main dev branch, maybe the `pharo12-` part is not that useful. but since it's a git repository, maybe use a conventional name for "the main development branch" that is master or main. -J ________________________________________ De : Esteban Lorenzano <estebanlm(a)netc.eu> EnvoyÃ© : 10 mars 2023 07:53 Ã : Pharo Development List Cc : Pharo Development List Objet : [Pharo-dev] Re: [ANN] preparing for release, freezing enhancements :) Hi Jean, As every year, we try to release in april. Now if this will be there or not, it always depends on several things, but for now we are pretty confident on it :P About renaming branches... we will not do that for the moment, sorry. We have discussed a lot in the past and this naming pattern is working so far. But as every release also, we will re-discuss our process after the release happens, to iterate on it and improve... what would be the rational behind having a main branch as default instead a branch with the version we are working on? (I could consider start having branchs named, e.g. pharo12-dev, to differentiate it from the stable branch, but since that would mean to change a lot of tools that depend on the naming, it has to be considered careful). cheers! Esteban On Mar 10 2023, at 1:42 pm, Privat, Jean <privat.jean(a)uqam.ca> wrote: Nice, do you have a timeframe in mind for the release, or this will be "when it's ready"? Also, a suggestion: do not create a `Pharo12` branch yet but use a master/main one (and make it the default branch). It helps newcomers to understand more easily the structure of the project. -J ________________________________________ De : Esteban Lorenzano <estebanlm(a)netc.eu> EnvoyÃ© : 10 mars 2023 05:03 Ã : Pharo Development List Objet : [Pharo-dev] [ANN] preparing for release, freezing enhancements :) Hello, We are slowly preparing to release Pharo 11. For those making changes that are not bugfixes, we will open Pharo 12 branch beginning of next week. Please, stop submitting enhancement/modification changes to Pharo 11, but instead all bugfixes you can contribute are welcome :) cheers! Esteban

March 13, 2023

Re: [ANN] preparing for release, freezing enhancements :)

by Esteban Lorenzano

Hi Jean, As every year, we try to release in april. Now if this will be there or not, it always depends on several things, but for now we are pretty confident on it :P About renaming branches... we will not do that for the moment, sorry. We have discussed a lot in the past and this naming pattern is working so far. But as every release also, we will re-discuss our process after the release happens, to iterate on it and improve... what would be the rational behind having a main branch as default instead a branch with the version we are working on? (I could consider start having branchs named, e.g. pharo12-dev, to differentiate it from the stable branch, but since that would mean to change a lot of tools that depend on the naming, it has to be considered careful). cheers! Esteban On Mar 10 2023, at 1:42 pm, Privat, Jean <privat.jean(a)uqam.ca> wrote: > Nice, > > do you have a timeframe in mind for the release, or this will be "when it's ready"? > Also, a suggestion: do not create a `Pharo12` branch yet but use a master/main one (and make it the default branch). > It helps newcomers to understand more easily the structure of the project. > > -J > ________________________________________ > De : Esteban Lorenzano <estebanlm(a)netc.eu> > EnvoyÃ© : 10 mars 2023 05:03 > Ã : Pharo Development List > Objet : [Pharo-dev] [ANN] preparing for release, freezing enhancements :) > > Hello, > We are slowly preparing to release Pharo 11. > For those making changes that are not bugfixes, we will open Pharo 12 branch beginning of next week. > > Please, stop submitting enhancement/modification changes to Pharo 11, but instead all bugfixes you can contribute are welcome :) > cheers! > Esteban >

March 10, 2023

Re: [ANN] preparing for release, freezing enhancements :)

by Privat, Jean

Nice, do you have a timeframe in mind for the release, or this will be "when it's ready"? Also, a suggestion: do not create a `Pharo12` branch yet but use a master/main one (and make it the default branch). It helps newcomers to understand more easily the structure of the project. -J ________________________________________ De : Esteban Lorenzano <estebanlm(a)netc.eu> EnvoyÃ© : 10 mars 2023 05:03 Ã : Pharo Development List Objet : [Pharo-dev] [ANN] preparing for release, freezing enhancements :) Hello, We are slowly preparing to release Pharo 11. For those making changes that are not bugfixes, we will open Pharo 12 branch beginning of next week. Please, stop submitting enhancement/modification changes to Pharo 11, but instead all bugfixes you can contribute are welcome :) cheers! Esteban

March 10, 2023

[ANN] preparing for release, freezing enhancements :)

by Esteban Lorenzano

Hello, We are slowly preparing to release Pharo 11. For those making changes that are not bugfixes, we will open Pharo 12 branch beginning of next week. Please, stop submitting enhancement/modification changes to Pharo 11, but instead all bugfixes you can contribute are welcome :) cheers! Esteban

March 10, 2023

Re: This week (9/2023) on the Pharo Issue Tracker

by Tim Mackinnon

While I'm not able to commit time to help due to personal commitments taking all my spare time at the moment - it does make me smile reading the list of improvements and the fact the people care about this stuff. Big thanks to all of you! Tim On Fri, 3 Mar 2023, at 10:51 AM, Marcus Denker wrote: > We merged 58 PRs this week: > > > Compiler > ======== > > - Improve faulty parsing of byte array literal (alternative version) #12818 > https://github.com/pharo-project/pharo/pull/12818 > > - NumberParser: kill requestor #12835 > https://github.com/pharo-project/pharo/pull/12835 > > - Add RBToken>>isSpecial: to simplify parsing code #12836 > https://github.com/pharo-project/pharo/pull/12836 > > - Clean some parsing code #12861 > https://github.com/pharo-project/pharo/pull/12861 > > - Improve scanning: escape comments #12857 > https://github.com/pharo-project/pharo/pull/12857 > > - Hook for custom syntaxhighlight #12594 > https://github.com/pharo-project/pharo/pull/12594 > > - Improve faulty parsing: generalize code snippets #12847 > https://github.com/pharo-project/pharo/pull/12847 > > - Improve faulty parsing: rename content as contents (a s was missing) #12854 > https://github.com/pharo-project/pharo/pull/12854 > > - > 12858-CopiedLocalVariable-answers-false-to-isTemporaryVariable-even-when-it-is > #12869 > https://github.com/pharo-project/pharo/pull/12869 > > - HotFix. Restore RBScanner>>#parseErrorNode: #12875 > https://github.com/pharo-project/pharo/pull/12875 > > - Do not stack RBUnfinishedStatementErrorNode #12873 > https://github.com/pharo-project/pharo/pull/12873 > > - EFFormatter use parenthesis on error nodes if some were present #12872 > https://github.com/pharo-project/pharo/pull/12872 > > - RBCodeSnippet nice overview of error messages #12871 > https://github.com/pharo-project/pharo/pull/12871 > > - Rewrite some error messages to follow the style Foo expected #12874 > https://github.com/pharo-project/pharo/pull/12874 > > - Improve faulty parsing on variables #12868 > https://github.com/pharo-project/pharo/pull/12868 > > - Improve faulty parsing of methods #12879 > https://github.com/pharo-project/pharo/pull/12879 > > - Improve faulty parsing by testing unreachable code #12893 > https://github.com/pharo-project/pharo/pull/12893 > > - Improve faulty parsing on chars (and primitive arrays) #12891 > https://github.com/pharo-project/pharo/pull/12891 > > Fixes > ===== > > - Update matchesTypes to fix DNU in matchesTypes #12611 > https://github.com/pharo-project/pharo/pull/12611 > > - Fix float comparision with precision and start to test Math-Operationâ¦ #12615 > https://github.com/pharo-project/pharo/pull/12615 > > - Refactoring TDebugger class>>#handlesContext: to > TDebugger>>#handlesDebugSession: #12833 > https://github.com/pharo-project/pharo/pull/12833 > > - New try at not hardcoding Metacello Attributes #12511 > https://github.com/pharo-project/pharo/pull/12511 > > - Fix TPrintTests rotten green tests #12846 > https://github.com/pharo-project/pharo/pull/12846 > > - Use MethodClassifier protocol for new methods instead of the selected > protocol #12882 > https://github.com/pharo-project/pharo/pull/12882 > > - Do not ask the user a method protocol first but instead try to auto > classify the method and only ask the user if auto classification failed > #470 > https://github.com/pharo-spec/NewTools/pull/470 > > - Fix #10929 Graphic UI selection glitch with selected text on large > screens #12863 > https://github.com/pharo-project/pharo/pull/12863 > > - Fix #12459 : text selection drag and drop problem. #12460 > https://github.com/pharo-project/pharo/pull/12460 > > - Fixing debugger inspector that wasn't updating when the debugger > entered a new optimized scope #472 > https://github.com/pharo-spec/NewTools/pull/472 > > - Prevent recursive retries on createIcebergRepositoryWithFallbackFor:url: #1673 > https://github.com/pharo-vcs/iceberg/pull/1673 > > - Fixes: Committing with empty description can lead to problems #1681 #1682 > https://github.com/pharo-vcs/iceberg/pull/1682 > > External Package > =============== > > - Update the version of graph algos to use the latest one #12851 > https://github.com/pharo-project/pharo/pull/12851 > > - Updating Tonel version #12865 > https://github.com/pharo-project/pharo/pull/12865 > > - Sync ston #12829 > https://github.com/pharo-project/pharo/pull/12829 > > - Microdown-RichTextComposer is now managed outside #12890 > https://github.com/pharo-project/pharo/pull/12890 > > > CI > === > > - Make all PRs to run in the latest VM #12605 > https://github.com/pharo-project/pharo/pull/12605 > > - Remove zinc file system from bootstrap #12839 > https://github.com/pharo-project/pharo/pull/12839 > > - Skipping test in windows as it is hanging #12887 > https://github.com/pharo-project/pharo/pull/12887 > > > Features > ======== > > - new general rule ReNotEqualityOperatorsRule to inform users of != or > !== #12864 > https://github.com/pharo-project/pharo/pull/12864 > > - Adding new rewrite tools #464 > https://github.com/pharo-spec/NewTools/pull/464 > > - Loading Chest in BaselineOfNewTools: Integration of Chest as a > debugger extension #451 > https://github.com/pharo-spec/NewTools/pull/451 > > Cleanups > ======== > > - Remove SerialPort that relies on a vm plugin that is not in the vm > anymore #12773 > https://github.com/pharo-project/pharo/pull/12773 > > - Refactoring UI cleanup #12528 > https://github.com/pharo-project/pharo/pull/12528 > > - Remove old slang pragmas #12849 > https://github.com/pharo-project/pharo/pull/12849 > > - Remove not loaded Pillar packages #12848 > https://github.com/pharo-project/pharo/pull/12848 > > - Deprecate all nativeboost methods #12838 > https://github.com/pharo-project/pharo/pull/12838 > > - Remove dependency of ChangeSet on Author #12584 > https://github.com/pharo-project/pharo/pull/12584 > > - Remove old RewriteTools #12607 > https://github.com/pharo-project/pharo/pull/12607 > > - Remove help packages that are not loaded in the image #12613 > https://github.com/pharo-project/pharo/pull/12613 > > - Cleanup: Condense Rubric packages #12626 > https://github.com/pharo-project/pharo/pull/12626 > > - Cleanup: Condense System-Caching packages #12660 > https://github.com/pharo-project/pharo/pull/12660 > > - Cleanup: Condense System-Changes packages #12662 > https://github.com/pharo-project/pharo/pull/12662 > > - Clean up spaces in Polymorph-Widgets package #12855 > https://github.com/pharo-project/pharo/pull/12855 > > - Cleanup: Condense System-BasicCommandLineHandler packages #12658 > https://github.com/pharo-project/pharo/pull/12658 > > - use ifEmpty ifNotEmpty #12877 > https://github.com/pharo-project/pharo/pull/12877 > > - Remove reference to deprecated class #1679 > https://github.com/pharo-vcs/iceberg/pull/1679

March 3, 2023

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

by Marcus Denker

We merged 58 PRs this week: Compiler ======== - Improve faulty parsing of byte array literal (alternative version) #12818 https://github.com/pharo-project/pharo/pull/12818 - NumberParser: kill requestor #12835 https://github.com/pharo-project/pharo/pull/12835 - Add RBToken>>isSpecial: to simplify parsing code #12836 https://github.com/pharo-project/pharo/pull/12836 - Clean some parsing code #12861 https://github.com/pharo-project/pharo/pull/12861 - Improve scanning: escape comments #12857 https://github.com/pharo-project/pharo/pull/12857 - Hook for custom syntaxhighlight #12594 https://github.com/pharo-project/pharo/pull/12594 - Improve faulty parsing: generalize code snippets #12847 https://github.com/pharo-project/pharo/pull/12847 - Improve faulty parsing: rename content as contents (a s was missing) #12854 https://github.com/pharo-project/pharo/pull/12854 - 12858-CopiedLocalVariable-answers-false-to-isTemporaryVariable-even-when-it-is #12869 https://github.com/pharo-project/pharo/pull/12869 - HotFix. Restore RBScanner>>#parseErrorNode: #12875 https://github.com/pharo-project/pharo/pull/12875 - Do not stack RBUnfinishedStatementErrorNode #12873 https://github.com/pharo-project/pharo/pull/12873 - EFFormatter use parenthesis on error nodes if some were present #12872 https://github.com/pharo-project/pharo/pull/12872 - RBCodeSnippet nice overview of error messages #12871 https://github.com/pharo-project/pharo/pull/12871 - Rewrite some error messages to follow the style Foo expected #12874 https://github.com/pharo-project/pharo/pull/12874 - Improve faulty parsing on variables #12868 https://github.com/pharo-project/pharo/pull/12868 - Improve faulty parsing of methods #12879 https://github.com/pharo-project/pharo/pull/12879 - Improve faulty parsing by testing unreachable code #12893 https://github.com/pharo-project/pharo/pull/12893 - Improve faulty parsing on chars (and primitive arrays) #12891 https://github.com/pharo-project/pharo/pull/12891 Fixes ===== - Update matchesTypes to fix DNU in matchesTypes #12611 https://github.com/pharo-project/pharo/pull/12611 - Fix float comparision with precision and start to test Math-Operationâ¦ #12615 https://github.com/pharo-project/pharo/pull/12615 - Refactoring TDebugger class>>#handlesContext: to TDebugger>>#handlesDebugSession: #12833 https://github.com/pharo-project/pharo/pull/12833 - New try at not hardcoding Metacello Attributes #12511 https://github.com/pharo-project/pharo/pull/12511 - Fix TPrintTests rotten green tests #12846 https://github.com/pharo-project/pharo/pull/12846 - Use MethodClassifier protocol for new methods instead of the selected protocol #12882 https://github.com/pharo-project/pharo/pull/12882 - Do not ask the user a method protocol first but instead try to auto classify the method and only ask the user if auto classification failed #470 https://github.com/pharo-spec/NewTools/pull/470 - Fix #10929 Graphic UI selection glitch with selected text on large screens #12863 https://github.com/pharo-project/pharo/pull/12863 - Fix #12459 : text selection drag and drop problem. #12460 https://github.com/pharo-project/pharo/pull/12460 - Fixing debugger inspector that wasn't updating when the debugger entered a new optimized scope #472 https://github.com/pharo-spec/NewTools/pull/472 - Prevent recursive retries on createIcebergRepositoryWithFallbackFor:url: #1673 https://github.com/pharo-vcs/iceberg/pull/1673 - Fixes: Committing with empty description can lead to problems #1681 #1682 https://github.com/pharo-vcs/iceberg/pull/1682 External Package =============== - Update the version of graph algos to use the latest one #12851 https://github.com/pharo-project/pharo/pull/12851 - Updating Tonel version #12865 https://github.com/pharo-project/pharo/pull/12865 - Sync ston #12829 https://github.com/pharo-project/pharo/pull/12829 - Microdown-RichTextComposer is now managed outside #12890 https://github.com/pharo-project/pharo/pull/12890 CI === - Make all PRs to run in the latest VM #12605 https://github.com/pharo-project/pharo/pull/12605 - Remove zinc file system from bootstrap #12839 https://github.com/pharo-project/pharo/pull/12839 - Skipping test in windows as it is hanging #12887 https://github.com/pharo-project/pharo/pull/12887 Features ======== - new general rule ReNotEqualityOperatorsRule to inform users of != or !== #12864 https://github.com/pharo-project/pharo/pull/12864 - Adding new rewrite tools #464 https://github.com/pharo-spec/NewTools/pull/464 - Loading Chest in BaselineOfNewTools: Integration of Chest as a debugger extension #451 https://github.com/pharo-spec/NewTools/pull/451 Cleanups ======== - Remove SerialPort that relies on a vm plugin that is not in the vm anymore #12773 https://github.com/pharo-project/pharo/pull/12773 - Refactoring UI cleanup #12528 https://github.com/pharo-project/pharo/pull/12528 - Remove old slang pragmas #12849 https://github.com/pharo-project/pharo/pull/12849 - Remove not loaded Pillar packages #12848 https://github.com/pharo-project/pharo/pull/12848 - Deprecate all nativeboost methods #12838 https://github.com/pharo-project/pharo/pull/12838 - Remove dependency of ChangeSet on Author #12584 https://github.com/pharo-project/pharo/pull/12584 - Remove old RewriteTools #12607 https://github.com/pharo-project/pharo/pull/12607 - Remove help packages that are not loaded in the image #12613 https://github.com/pharo-project/pharo/pull/12613 - Cleanup: Condense Rubric packages #12626 https://github.com/pharo-project/pharo/pull/12626 - Cleanup: Condense System-Caching packages #12660 https://github.com/pharo-project/pharo/pull/12660 - Cleanup: Condense System-Changes packages #12662 https://github.com/pharo-project/pharo/pull/12662 - Clean up spaces in Polymorph-Widgets package #12855 https://github.com/pharo-project/pharo/pull/12855 - Cleanup: Condense System-BasicCommandLineHandler packages #12658 https://github.com/pharo-project/pharo/pull/12658 - use ifEmpty ifNotEmpty #12877 https://github.com/pharo-project/pharo/pull/12877 - Remove reference to deprecated class #1679 https://github.com/pharo-vcs/iceberg/pull/1679

March 3, 2023

Re: Pharo VM Release - v10.0.0

by Gabriel Cotelli

Congratulations on the new VM release! Are there some reasons to skip this version as the default for Pharo 10 images? Or is it just not worth the effort, given the close release date of Pharo 11? I need to update our Pharo docker images and I want to understand if it's better to wait for the Pharo 11 release. On Wed, Mar 1, 2023 at 7:26 AM tesonep(a)gmail.com <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) 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

Re: Pharo VM Release - v10.0.0

by Norbert Hartl

This is yet again an impressive list of good things. Always appreciated are "Remov*" features :) I'm especially interested in ephemerons and how it improves the weak structures in the image. Hope the image support that makes use of the vm features follows soon. A wish would be to know a bit more about the permanent space news. Great work as always. Thanks! Norbert > Am 01.03.2023 um 11:26 schrieb tesonep(a)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 <http://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 <mailto:tesonep@gmail.com>

March 1, 2023