- Pharo-dev - lists.pharo.org

Abut writeOn: versus storeOn:
by StÃ©phane Ducasse Dec. 23, 2020

Dec. 23, 2020

Hi I saw that a couple of collections implement writeOn: in addition to storeOn: and I was wondering if someone knows the reason. My gut feeling is that this is somehow dead code. Because readOn: logic is the inverse of storeOn: and I was wondering what is the equivalent for writeOn: S -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Aurore Dalle FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

2 2

[Pharo 8.0] Build #1145: backportIfErrorDo
by ci-pharo-ci-jenkins2＠inria.fr Dec. 22, 2020

Dec. 22, 2020

There is a new Pharo build available! The status of the build #1145 was: FAILURE. The Pull Request #6154 was integrated: "backportIfErrorDo" Pull request url: https://github.com/pharo-project/pharo/pull/6154 Issue Url: https://github.com/pharo-project/pharo/issues/backportIfErrorDo Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #1144: Fixes #6993 against P8: Incorrect error message on failed parsing of a number with high radix
by ci-pharo-ci-jenkins2＠inria.fr Dec. 22, 2020

Dec. 22, 2020

There is a new Pharo build available! The status of the build #1144 was: FAILURE. The Pull Request #6994 was integrated: "Fixes #6993 against P8: Incorrect error message on failed parsing of a number with high radix" Pull request url: https://github.com/pharo-project/pharo/pull/6994 Issue Url: https://github.com/pharo-project/pharo/issues/6993 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Progress Report -> Refactoring Project - ( December 14 - 18 )
by EVELYN CUSI LOPEZ Dec. 21, 2020

Dec. 21, 2020

Hi all, Last week I did these tasks: - Pair programming with Pablo, to understand how use commander2 with calypso. By the moment this only works in source code context, some similary methods can be created to use commander2 in class, variable and method context. - Fix duplicated method issue ( https://github.com/pharo-project/pharo/pull/8147 ) - Fix all abstract instance variables issue ( https://github.com/pharo-project/pharo/pull/8138) - Continue fixing Extract method and ocurrences issues, I separated middle interactions with user (in Find and replace refactoring), to remove coupling between view and logic, but now I have some errors when I want use a composite refactoring. Tasks for this week: - Finish to fix Extract method issues, only logic part (removing views) - Migrate extract method to refactoring2. - Migrate command of extract method and occurrences to commander2 - Create extract setUp and tearDown refactoring only for TestCases - Fix undo refactoring issue (I already tried to correct, however I continue having some problems - https://github.com/pharo-project/pharo/compare/Pharo9.0...Lin777:FixUndoRef… ) - Add option to limit classes where we replace senders of method to other method (https://github.com/pharo-project/pharo/issues/8087) Cheers, Evelyn

1 0

This week (51/2020) on the Issue Tracker
by Marcus Denker Dec. 18, 2020

Dec. 18, 2020

FFI === - Integrating ThreadedFFI in the image. #8102 https://github.com/pharo-project/pharo/pull/8102 - fixing-initialization-of-ffibackend #8131 https://github.com/pharo-project/pharo/pull/8131 New Features ============= - Class>>#usesTrait: and Class>>#usesTraitTransitively: #8002 https://github.com/pharo-project/pharo/pull/8002 - ThemeIcons should have a #reset method #8050 https://github.com/pharo-project/pharo/pull/8050 Refactoring Engine =========== - 8079-RBRefactoringChangeTesttestAddMetaclassPattern-calls-definition #8107 https://github.com/pharo-project/pharo/pull/8107 - Fixing undo refactory #8051 https://github.com/pharo-project/pharo/pull/8051 Fixes ===== - 8129-Debugger-should-log-the-exception-always #8130 https://github.com/pharo-project/pharo/pull/8130 - Fixed #6391. Filed out methods are now saved into files that have colons in their names #7888 https://github.com/pharo-project/pharo/pull/7888 - Correctly decode file names from SDL2, at SDL2 #8116 https://github.com/pharo-project/pharo/pull/8116 - 8117-RBMethodNode>>methodClass-should-gard-for-nil #8118 https://github.com/pharo-project/pharo/pull/8118 - Bootstrapper in 64 and 32 bits #8064 https://github.com/pharo-project/pharo/pull/8064 - Make use of current working directory primitive on windows #8070 https://github.com/pharo-project/pharo/pull/8070 Graphics ======== - Moving the responsibility to the OSWindowDriver #8123 https://github.com/pharo-project/pharo/pull/8123 - 8086-RSLabelTest-Could-not-find-accessor-for-variable-named-anUTF8EncodedString #8104 https://github.com/pharo-project/pharo/pull/8104 - Enh/win32 athens #8069 https://github.com/pharo-project/pharo/pull/8069 Fluid Class Definitions ======================= Work continous: cleanups and fixes - 7923-Broken-traits-definitions #8046 https://github.com/pharo-project/pharo/pull/8046 - 8122-Expanding-a-class-does-not-respect-superclass #8137 https://github.com/pharo-project/pharo/pull/8137 - ClassParser-reduce-NewUndeclaredWarning #8121 https://github.com/pharo-project/pharo/pull/8121 - 8073-glitch-in-package-template #8106 https://github.com/pharo-project/pharo/pull/8106 - 8036-Spotter-uses-definition-for-class-instead-of-definitionString #8043 https://github.com/pharo-project/pharo/pull/8043 - 8098-definition---definitionString #8099 https://github.com/pharo-project/pharo/pull/8099 - 8080-TraitTesttestPrintingClassSide-is-calling-definition #8091 https://github.com/pharo-project/pharo/pull/8091 - 8078-EpHasImpactVisitorvisitBehaviorChange-calls-definition #8090 https://github.com/pharo-project/pharo/pull/8090 - 081-EpCodeChangeIntegrationTesttestRedundantClassDefinition-calls-definition-and-more #8096 https://github.com/pharo-project/pharo/pull/8096 - 8071-Replying-a-class-definition-with-Epicea-and-fluid-class-does-not-recreate-the-class #8072 https://github.com/pharo-project/pharo/pull/8072 Cleanups Dead Code ================== - Cleanup-ClassOrganization-listAtCategoryNumber #8126 https://github.com/pharo-project/pharo/pull/8126 - SlotScope-DeadCode-Clean #8105 https://github.com/pharo-project/pharo/pull/8105 Cleanups ======= - RBProgramNode>>#doSemanticAnalysis should be correctly packaged #8110 https://github.com/pharo-project/pharo/pull/8110 - Cleanup Variable class comment #8112 https://github.com/pharo-project/pharo/pull/8112 - Small typo in ReExceptionStrategy class comment #8093 https://github.com/pharo-project/pharo/pull/8093 - Typo in handle:about:forProppertiesDo: #8095 https://github.com/pharo-project/pharo/pull/8095 - Move ArrayTest to Collections-Sequenceable-Tests #7995 https://github.com/pharo-project/pharo/pull/7995 - 8075-RunArray-is-not-an-abstract-class #8076 https://github.com/pharo-project/pharo/pull/8076 - TestSkip should be TestSkipped #7997 https://github.com/pharo-project/pharo/pull/7997 - Remove unused ivars in DrTest packages #8085 https://github.com/pharo-project/pharo/pull/8085 - Typo in Path class method name delimeter #8048 https://github.com/pharo-project/pharo/pull/8048 - Cleanup Renraku-Help package #8059 https://github.com/pharo-project/pharo/pull/8059 - Mark abstract classes in Renraku #8061 https://github.com/pharo-project/pharo/pull/8061 - RBGenericNodeVisitor-tests #8067 https://github.com/pharo-project/pharo/pull/8067 Pharo 8 ======= - Backport to ease Moose loading #8124 https://github.com/pharo-project/pharo/pull/8124

1 0

[Pharo 8.0] Build #1143: Backport to ease Moose loading
by ci-pharo-ci-jenkins2＠inria.fr Dec. 16, 2020

Dec. 16, 2020

There is a new Pharo build available! The status of the build #1143 was: FAILURE. The Pull Request #8124 was integrated: "Backport to ease Moose loading" Pull request url: https://github.com/pharo-project/pharo/pull/8124 Issue Url: https://github.com/pharo-project/pharo/issues/backport Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

MoreVMs 2021 : Workshop on Modern Language Runtimes, Ecosystems, and VMs
by Fabio Niephaus Dec. 16, 2020

Dec. 16, 2020

============================================================================ Call for Extended Abstracts and Talks: MoreVMsâ21 5th International Workshop on Modern Language Runtimes, Ecosystems, and VMs Co-located with â¹Programmingâºâ21 March 22nd to 26th, 2021, Online, United Kingdom https://2021.programming-conference.org/home/MoreVMs-2021 ============================================================================ Following four previous successful editions, the MoreVMsâ21 workshop aims to bring together industrial and academic programmers to discuss the design, implementation, and usage of modern languages and runtimes. This includes aspects such as reuse of language runtimes, modular implementation, language design, and compilation strategies. By bringing together both researchers and practitioners, the workshop aims to enable a diverse discussion on how languages and runtimes are currently being utilized, and where they need to improve further. In addition to conventional workshop-style submissions, MoreVMs also accepts (and encourages) submissions that present early-stage work and emerging ideas. Relevant topics include, but are definitely not limited to, the following: - Extensible VM design (compiler- or interpreter-based VMs) - Reusable components (e.g. interpreters, garbage collectors, ...) - Static and dynamic compilation techniques - Techniques for targeting high-level languages such as JavaScript - Interoperability between languages - Tooling support (e.g. debugging, profiling, etc.) - Programming language development environments - Case studies of existing language implementation approaches - Language implementation challenges and trade-offs - Surveys and usage reports to understand usage in the wild - Ideas for more predictable performance - Ideas for how VMs could take advantage of new hardware features - Ideas for how we should build languages in the future Workshop Format and Submissions ------------------------------- We welcome presentation proposals in the form of extended abstracts (2 to 4 pages long) and talk proposals (title and 400 words abstract) discussing new techniques, insights, experiences, works-in-progress, as well as future visions, from either an academic or industrial perspective. The extended abstracts and talk proposals, and if the speakers wish, their slides, will be published on the workshop's website. Alternatively, extended abstracts can be published as part of the companion of â¹Programmingâºâ21 in the ACM DL. Publication in the ACM DL is conditional on the acceptance by the program committee. Please note that MoreVMsâ21 is organized as an academic workshop, and as such, speakers will be required to register for the workshop. Author Instructions ------------------- Submissions should use the ACM `acmart` format: https://www.acm.org/publications/proceedings-template If you are using LaTeX, submissions should use the 'acmart' document class with the 'sigconf' option, and with a font size of 9 point. Please use the Libertine/Biolinum font family. Please include page numbers in your submission using the LaTeX command `\settopmatter{printfolios=true}`. All submissions should be in PDF format. Please also ensure that your submission is legible when printed on a black and white printer. In particular, please check that colors remain distinct and font sizes are legible. Submission Site: https://easychair.org/conferences/?conf=morevms21 Important Dates --------------- Extended abstract and talk submissions: 2021-01-13 Author notification: 2021-02-15 Camera Ready: 2021-02-26 Workshop: TBA (between 2021-03-22 and 2021-03-26) All deadlines are Anywhere on Earth (AoE), i.e. GMT/UTC-12:00 hour. Program Committee ----------------- Maya Armyanova, Google, Germany Maxime Chevalier-Boisvert, UniversitÃ© de MontrÃ©al, Canada Lukas Diekmann, King's College London, United Kingdom Charlie Gracie, Microsoft, Canada Daco Harkes, Google, Denmark Christian Humer, Oracle Labs, Switzerland Sophie Kaleba, University of Kent, United Kingdom Mikel LujÃ¡n, University of Manchester, United Kingdom Ana Milanova, Rensselaer Polytechnic Institute, United States Tobias Pape, Hasso Plattner Institute, University of Potsdam, Germany Tomoharu Ugawa, University of Tokyo, Japan Organizers ---------- Fabio Niephaus, Hasso Plattner Institute, University of Potsdam, Germany David Leopoldseder, Oracle Labs, Austria

1 0

[ANN] Next Pharo Sprint: Dec 18
by Marcus Denker Dec. 14, 2020

Dec. 14, 2020

We will organize a Pharo sprint / Moose dojo Dec 18 (this Friday). This is a bit earlier due to Christmas times. Goals of this sprint: - Fix issues from tracker https://github.com/pharo-project/pharo/issues This is a Remote Sprint, it happens on Discord. http://pharo.org/contribute-events We have added a Board to coordinate the work: https://github.com/orgs/pharo-project/projects/9 A list of all Pharo Event of the year an be found here: https://association.pharo.org/events

1 0

Progress Report -> Refactoring Project - ( December 7 - 11 )
by EVELYN CUSI LOPEZ Dec. 14, 2020

Dec. 14, 2020

Hi everyone, Last week I did these tasks: - Review Commander2, to migrate refactorings to use Commander2 we must create a decorator class using Calypso, now only exists a decorator with Spec2 (SpCommand). - Fix UI rename method issue ( https://github.com/pharo-project/pharo/pull/7978) - Fix undo refactoring issue ( https://github.com/pharo-project/pharo/pull/8051) - Review Refactoring2 - Start to fix Extract method issues. Tasks for this week: - Finish to fix Extract method issues. - Re-visit all the tests to use a classBuilder instead of string as much as possible. - Improve the refactoring model to support traits and slots. - Fix Push up refactoring issue #2656 ( https://github.com/pharo-project/pharo/issues/2656) - Fix Abstract instance variables issue ( https://github.com/pharo-project/pharo/issues/8100) Cheers, Evelyn

1 0

Dec. 13, 2020

Dear happy Pharoers and others, Over the last months we have been working on the implementation of a MIT-licensed ARMv8 Just-In-Time compiler for Pharo VM. We are very happy with the advance on this subject, as we have not only implemented a new backend but we have added more than 2500 tests to the JIT, the primitives, code generation, plugins and the VM in general. In the process we fixed many problems. It shows that following the roadmap that was decided during General assembly of PharoDays, we have been investing in the Pharo VM and that our efforts are greatly paying off. Also, we are generating a lot of documentation and improving the process to really democratize the development of the VM. So Pharo is a better shape than ever on such matter and this opens a lot of possibility for the future. ## Call for Beta-Testers We would like to announce that a first version of our JIT backend is available for beta-testing for ARM Linux machines using Ubuntu. We are now entering into a beta testing stage of the VM and the image in Ubuntu ARM 64. We would like to invite you to our beta testing phase for the VM. If you're interested in participating, please contact pablo.tesone(a)inria.fr. The following sections give more details of the current status, and the following steps including Apple Silicon, Windows ARM64 and Linux Open Build System support. ## Current Status Our objective is to have a running JIT for the new aarch64 architecture (ARM 64bits). This task includes not only a new backend for the JIT compiler but also adding support for external libraries, dependencies and the build process. This means having a working VM with comparable features as the one existing in Intel X64. We are targeting all the major operating systems running in this platform (Linux, OSX, Windows). Each of them present different restrictions and conditions. This is the current status: - We implemented a full backend for the JIT compiler targeting aarch64. - All the image side was adapted to run on it, tested on Ubuntu ARM 64 bits. - We added support for: Iceberg (Libgit) / Athens (Cairo) / SDL / GTK - We implemented a LibFFI-based FFI backend as the default one for Pharo 9 in aarch64 (next to come in all platforms). This opens the door to ease port the features to other platforms and OSes. ## Following Steps and Open Betas: Linux Open Build System (OBS), Windows ARM64 and Apple Silicon Linux Systems: In the following days, we will also support Raspbian (Debian) and Manjaro on ARM64. For doing so, we are pushing the last details in having a single Linux build system through OBS. So, if you want to start doing beta-testing of these versions please contact us. A public beta will be open in around two weeks. Windows Systems: We have extended the build process to fully support Microsoft Visual Studio compilers and more flexibility to select the targets, also we are building it to run in Windows ARM. To correctly run the VM in Windows it is needed to build all dependencies for aarch64. In the following weeks, we expect to have a working Non-JIT version and a JIT version. The remaining points to have a JIT version are related with the build process as the API of the operating system has not changed from X64 to aarch64. OSX Systems: Our third target is to have a working version for the newest Apple silicon. We are acquiring the corresponding hardware to test and to address the differences in the API exposed to JIT applications. As it is the case of the Windows VM, there is not need to change the machine code generation backend; but to compile external libraries, and particularities of the new OS version. Thanks for your support, and again, if you like to start beta testing the VM please contact us. In the meantime, we will continue giving you news about the current state and where are we going. The consortium would like to particularly thank Schmidt Buro and Lifeware for their contracts. Regards, Pablo in behalf of the Pharo Consortium Engineers -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Aurore Dalle FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

2 1