- Pharo-dev - lists.pharo.org

ARM64 VM for Manjaro/Arch
by Patrick Henning Feb. 16, 2021

Feb. 16, 2021

Hello, I am writing to ask how I can access the beta ARM64 VM for Arch-type Linux (I am using Manjaro in particular). Thank you! Patrick

2 3

Progress Report -> Refactoring Project - ( February 1 - 5 )
by Evelyn Cusi Lopez Feb. 15, 2021

Feb. 15, 2021

Hi all Last week I did these tasks: - Expose variable refactoring commands in source context ( https://github.com/pharo-project/pharo/pull/8472) - Improve messages of push up method refactoring, also add the option to push up referenced instance variables ( https://github.com/pharo-project/pharo/pull/8531) - Introduce a new way to move the method to class side refactoring ( https://github.com/pharo-project/pharo/pull/8532) - Add rename package refactoring ( https://github.com/pharo-project/pharo/pull/8533) Tasks for this week: - Improve extract setUp refactoring. - Fix previews of extract method with arguments ( https://github.com/pharo-project/pharo/issues/5855) - Improve renaming method refactoring, to only rename senders in specific packages (https://github.com/pharo-project/pharo/issues/8513) - Fix move to component issue ( https://github.com/pharo-project/pharo/issues/8499) Cheers, Evelyn

4 3

This week (06/2021) on the Issue Tracker
by Marcus Denker Feb. 12, 2021

Feb. 12, 2021

merge spec2 0.8.2 (GUI) ================= - all presenters can now be styled (not just widgets as before). - lists/trees/tables: activation happens also on enter (not just double click). - applications now have icon providers to answer icons by application - start documenting layouts (box layout) - bugfixes - https://github.com/pharo-spec/Spec/releases/tag/v0.8.2 Move to Iceberg v2 (git) =================== In short, this version is a UI update that was required for Pharo 9.0. The functionality should be the same as in previous version. - Migration from Spec1 to Spec2 - Migration from Commander1 to Commander2 - General pass over source code, especially in TipUI package. - Pass on README and Wiki documentation - GitHub Actions workflows instead of Travis and AppVeyor - Tests don't depend on OSSubProcess or ProcessWrapper - https://github.com/pharo-vcs/iceberg/releases/tag/v2.0.0 Features ======== - New icon styler for disabled breakpoints #8530 https://github.com/pharo-project/pharo/pull/8530 Fixes ====== - 8503-Slot-remove-in-Stateful-Traits #8539 https://github.com/pharo-project/pharo/pull/8539 - 8540-TFFI-should-support-passing-a-ByteArray-in-a-char-parameter-a-TFStringType #8541 https://github.com/pharo-project/pharo/pull/8541 - Fixes #4011 Character nextObject crashes Pharo too #8545 https://github.com/pharo-project/pharo/pull/8545 - Fixes issue #7616 implementors and senders browsing broken in the debugger #8462 https://github.com/pharo-project/pharo/pull/8462 - 8551-Error-when-doing-implementors-of-of-non-string-literals #8552 https://github.com/pharo-project/pharo/pull/8552 - 8520-TwoWay-Become-should-not-loop-infinite-when-out-of-space https://github.com/pharo-project/pharo/pull/8523 - 7662-Must-be-boolean-deoptimization-targeting-wrong-or-block #8519 https://github.com/pharo-project/pharo/pull/8519 - ReflectivityTest>>#setUp copies the ASTCache #8527 https://github.com/pharo-project/pharo/pull/8527 - Testing and adding debugger inspector maximize assertion failure diff pane #8501 https://github.com/pharo-project/pharo/pull/8501 Cleanups ======== - AST-unify-children #8555 https://github.com/pharo-project/pharo/pull/8555 - 8042 deprecate and remove pointdist because there is pointdistance to with exactly the same implementation #8543 https://github.com/pharo-project/pharo/pull/8543 - 8353-startStepping-is-calling-an-undefined-method #8535 https://github.com/pharo-project/pharo/pull/8535 - fixes #4856 - print on methods should avoid calling blindly print string on their elements #8497 https://github.com/pharo-project/pharo/pull/8497 - Adding deprecations that were recommended by DepMiner (accepted by 2 reviewers) #8496 https://github.com/pharo-project/pharo/pull/8496 - Adding deprecations for Opal Compiler that were recommended by DepMiner and accepted by Pablo #8507 https://github.com/pharo-project/pharo/pull/8507 - Cleanup-Compiler-Backend-DeadCode #8517 https://github.com/pharo-project/pharo/pull/8517 - 6757-Remove-references-to-the-class-Interpreter #8518 https://github.com/pharo-project/pharo/pull/8518 - 8473-whenGotForcus-method-in-RubScrolledTextMorph-class #8516 https://github.com/pharo-project/pharo/pull/8516

1 0

This week (05/2021) on the Issue Tracker
by Marcus Denker Feb. 5, 2021

Feb. 5, 2021

We merged 34 Pull Requests and closed 64 issues this week. Often one focuses on the pull requests. But even closed issue tracker entries that do not result in one PR did require work... even if it might be just spending 30 minutes trying to recreate the problem only to find that it has indeed been fixed already a long time ago. A complete list of the closed issues is available at https://github.com/pharo-project/pharo/pulse Here are the PRs: Debugger ======== - 2681 debugger step into does not go into accessors or methods with primitives #8456 https://github.com/pharo-project/pharo/pull/8456 - 8379-Debugger-Contextat-infinite-loop-when-pressing-Through-in-a-test-case-condition #8426 https://github.com/pharo-project/pharo/pull/8426 - Removing suspicious update code in the debugger inspector, and fixing variable update problem with recursive call #8430 https://github.com/pharo-project/pharo/pull/8430 - 8370 metalinks cannot be reinstalled if the image was saved while they were uninstalled #8448 https://github.com/pharo-project/pharo/pull/8448 Refactoring =========== - RB - Expose variable refactoring commands in source context #8472 https://github.com/pharo-project/pharo/pull/8472 - RB - Create new refactoring, to create accessors with lazy initialization #8464 https://github.com/pharo-project/pharo/pull/8464 - RB - Fix ExtractMethodTransformation #8465 https://github.com/pharo-project/pharo/pull/8465 - RB - Introduce Extract setUp refactoring #8466 https://github.com/pharo-project/pharo/pull/8466 Features ======== - Reorganize world menu #8414 https://github.com/pharo-project/pharo/pull/8414 Fixes ===== - Fix smart characters and add missing tests #8504 https://github.com/pharo-project/pharo/pull/8504 - TaRenameSlot-TestAndFix #8484 https://github.com/pharo-project/pharo/pull/8484 - Changeset-fileout-DNU #8486 https://github.com/pharo-project/pharo/pull/8486 - 692-Deprecation-exception-when-use-Open-Directory-Chooser-button-dialog-of-Iceberg-Settings-UI #8492 https://github.com/pharo-project/pharo/pull/8492 - 8458-Filelist-does-not-understand-readStream #8480 https://github.com/pharo-project/pharo/pull/8480 - Introduce asOpenInterval in Interval #8477 https://github.com/pharo-project/pharo/pull/8477 - 8450-ChangeSorter-should-open-and-work-with-new-Spec2 #8453 https://github.com/pharo-project/pharo/pull/8453 - 7987-Class-definition-should-not-be-evaluated-if-it-contains-a-syntax-error #8452 https://github.com/pharo-project/pharo/pull/8452 - Fix copy-paste to take into account real AST node #8449 https://github.com/pharo-project/pharo/pull/8449 Cleanups - Deprecations =================== Work related to deprecations.. as you might know, we can tag methods not only as deprecated, but add code to them which on-the-fly, at runtime, fixes the caller. This makes it much easier to evolve APIs. - Adding deprecations that were recommended by DepMiner (accepted by 3 reviewers) #8495 https://github.com/pharo-project/pharo/pull/8495 - Adding deprecations that were recommended by DepMiner (accepted by all 4 reviewers) #8494 https://github.com/pharo-project/pharo/pull/8494 - Adding transformation rules for two deprecated methods of Context. One of them was recommended by DepMiner but had to be modified #8510 https://github.com/pharo-project/pharo/pull/8510 - 7638-withSqueakLineEnding-should-be-moved-to-deprecated-package #8470 https://github.com/pharo-project/pharo/pull/8470 - 8471-Deprecate-OSSDL2WindowHandle #847 https://github.com/pharo-project/pharo/pull/8475 - 8467-Fuel-is-using-an-old-API-from-MultiByteFileStream #8468 https://github.com/pharo-project/pharo/pull/8468 Cleanups ======== And more cleanupsâ¦ Among other cleanups, we are still slowly fixing all the cases where a variable is defined but not used. Nearly there! when it is done, we add a release test and thus will never be able to merge code like that ever again. - DiskDirectoryEntry-remove-unused-classVar #8488 https://github.com/pharo-project/pharo/pull/8488 - Cleanup-unused-vars-JobProgressBarMorph #8498 https://github.com/pharo-project/pharo/pull/8498 - remove some unused class variables 1 #8433 https://github.com/pharo-project/pharo/pull/8433 - Classify one unclassified method in Trait #8487 https://github.com/pharo-project/pharo/pull/8487 - Clean the log file created on the disk by the test #8457 https://github.com/pharo-project/pharo/pull/8457 - 7889-GZipReadStream--fileIntoNewChangeSet-fullFileName #8447 https://github.com/pharo-project/pharo/pull/8447 - 7879-Clunky-interactive-but-bad-flow-for-fileIntoNewChangeSet #8493 https://github.com/pharo-project/pharo/pull/8493 - Move-ArgumentNamesTest-to-Debugger-Model-Tests-Core #8438 https://github.com/pharo-project/pharo/pull/8438 - 8454-Removing-more-users-of-oldDefinition #8455 https://github.com/pharo-project/pharo/pull/8455 Documentation ============== - 4372-Improve-ifNotNil-and-friends-comment-methods-to-indicate-that-they-are-optimized #8483 https://github.com/pharo-project/pharo/pull/8483 - Comment Interval>>#rangeIncludes: and more complete test #8446 https://github.com/pharo-project/pharo/pull/8446

1 0

Progress Report -> Refactoring Project - ( January 24 - 28 )
by Evelyn Cusi Lopez Feb. 1, 2021

Feb. 1, 2021

Hi all Last week I did these tasks: - Review PRs of clean unused variables ( https://github.com/pharo-project/pharo/pull/8425 , https://github.com/pharo-project/pharo/pull/8422) - Fix issue to reuse existing method in RBExtractMethodTransformation ( https://github.com/pharo-project/pharo/pull/8465 ). - Add new refactoring to generate accessors with lazy initialization ( https://github.com/pharo-project/pharo/pull/8464) - Review some issues and I help to close some were already fixed ( https://github.com/pharo-project/pharo/issues/6002 , https://github.com/pharo-project/pharo/issues/7108) - Fix issue to rename manifest class when rename a package, but I have problems with dependencies ( https://github.com/pharo-project/pharo/compare/Pharo9.0...Lin777:RenameMani… ). - Add the first version of extract setUp refactoring ( https://github.com/pharo-project/pharo/pull/8466) Tasks for this week: - Fix dependencies problems of rename manifest issue. - Improve extract setUp refactoring. - Fix previews of extract method with arguments ( https://github.com/pharo-project/pharo/issues/5855) - Fix rename refactoring, this should rename only local methods ( https://github.com/pharo-project/pharo/issues/6366) - Fix protect instance variable issue Cheers, Evelyn

1 0

This week (04/2021) on the Issue Tracker
by Marcus Denker Jan. 29, 2021

Jan. 29, 2021

If you want to help, a nice first step to get familiar with improving the system is to review Pull Requests. For example, there are always very simple ones (like the ones listed here in "Cleanup Unused Variablesâ) that are fairly easy to understand and review. Open Pull requests are here: https://github.com/pharo-project/pharo/pulls Debugger improvements and Fixes =========================== - Added empty selection interval to force SpCodePresenter to auto-scroll. #8428 https://github.com/pharo-project/pharo/pull/8428 - OCDoitTest-testDoItContextReadIvar #8437 https://github.com/pharo-project/pharo/pull/8437 - 7763-Does-BlockClosurecull-need-the-pragma-debuggerCompleteToSender #8427 https://github.com/pharo-project/pharo/pull/8427 - Inspecting a Text no longer shows the formatted text #8352 https://github.com/pharo-project/pharo/issues/8352 Refactoring Improvements ======================== - Fix broken tests - extract method and ocurrences #8420 https://github.com/pharo-project/pharo/pull/8420 - RB - Add message to kwon how many occurrences were replaced #8380 https://github.com/pharo-project/pharo/pull/8380 Fixes ===== - 8168-CompiledMethodreferencedClasses-should-not-take-class-variables-into-account #8240 https://github.com/pharo-project/pharo/pull/8240 - Mouse events were sent twice when using an event handler #8404 https://github.com/pharo-project/pharo/pull/8404 - Mouse over event is sent multiple times #8401 https://github.com/pharo-project/pharo/pull/8401 - Improve the Help for Spec2 #8410 https://github.com/pharo-project/pharo/pull/8410 - Fix a regression from earlier pharo that used to perserve order in sequences #8402 https://github.com/pharo-project/pharo/pull/8402 Cleanup Unused Variables ========================= - spec1-clean-ivars #8431 https://github.com/pharo-project/pharo/pull/8431 - remove two unused ivars in GT-Tests #8432 https://github.com/pharo-project/pharo/pull/8432 - Remove-unused-vars-RB #8422 https://github.com/pharo-project/pharo/pull/8422 -RBExtractMethodAndOccurrences-unused-ivar #8425 https://github.com/pharo-project/pharo/pull/8425 - 8354-SycRemoveMessageArgumentCommand-with-unused-ivar #8419 https://github.com/pharo-project/pharo/pull/8419

1 0

Look for software for virtual outing
by askoh Jan. 27, 2021

Jan. 27, 2021

Hi: My team at work has been asked to organize a "Virtual Outing" for socializing or camaraderie. I am think of using a Smalltalk virtual reality software for such an outing. Would any of Qwaq, Tref, Croquet be viable VR platforms for a group of less that 50 people? Thanks, Aik-Siong Koh -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

2 2

Jan. 25, 2021

> Begin forwarded message: > > From: Simon Holland via Esug-list <esug-list(a)lists.esug.org> > Subject: [Esug-list] URGENT - Fully funded Research Internship for Smalltalk programmer > Date: 24 January 2021 at 16:06:42 CET > To: esug-list(a)lists.esug.org > Reply-To: Simon Holland <simonxholland(a)icloud.com> > > URGENT â Fully funded five-month research internship available immediately in the School of Computing and Communications at The Open University for programmer. > > A fully funded place for a five-month Research Intern is immediately available at the School of Computing at the Open University. Prospective research interns could be excellent final year undergraduates, Masters students, or PhD students, or could have recently completed any of these awards. The post is available immediately, but in any case, you must be available to start in February 2021. Due to covid restrictions, the intern will be based remotely, with co-ordination online. > > The project involves the iterative design, construction and exploration of a highly expressive Direct Combination system (although no previous knowledge of Direct Combination is required). Direct Combination is a family of user interaction techniques, and a user interaction framework. Recent developments in Stateful Traits (Tesone et al., 2020) have provided tools for creating new highly expressive Direct Combination systems. > > The Project will involve designing, implementing and evaluating a new direct combination engine, and creating support tools as needed. You will be strongly encouraged to contribute as co-author to one or more refereed research publications. This research internship is available to start immediately and will run for five months. You will be able to work remotely for this whole period. > > Skills > Good Smalltalk programming skills are essential, ideally in Pharo. Good written and oral English communication skills are essential. Willingness to consider the end-userâs point of view is important. Various background skills are not essential, but could be helpful, such as: knowledge of, or interest in, software composition research and metaprogramming; good TDD habits; acquaintance with stateful traits; acquaintance with the Data-Context-Interaction paradigm; experience and skills with the Pharo toolset, such as Roassal, the Glamorous Toolkit, and Iceberg. > > Applications should include a CV with contact details and covering note that summarizes: > â¢ evidence of appropriate knowledge, skills and experience, > â¢ why you want to undertake this particular internship and why you would be a good candidate, > â¢ telephone, email and postal contact details for two referees, at least one of whom must be able to comment on subject discipline specifics. > > For more information, or for informal enquiries, which are encouraged, contact s.holland or o.howson (insert <at> here) open.ac.uk <http://open.ac.uk/>. Applications should also be sent to this address, and also copied to STEM-CC-Secretaries(a)open.ac.uk <mailto:STEM-CC-Secretaries@open.ac.uk>. > > âââââââââââââââââââââââââââââââââââââââ > > Further particulars > Design, Implementation, and Evaluation of a highly expressive Direct Combination Prototype > > Candidates are not required to know anything about Direct Combination (DC). However, some optional background is provided for candidates who might wish to know about the projectâs aim and scope. > > Direct Combination is variously a principle, a family of user interaction techniques, and a user interaction framework (Holland and Oppenheim, 1999; Holland et al., 2002a). Together, these can give users greatly enhanced flexibility interacting with digital systems and can reduce search when dealing with complex or unfamiliar interfaces (Holland et al., 2005). > > Direct Combination also has potential to simplify multi-device interaction (Holland et al., 2002), enhance bimanual interaction (Webb, 2017), facilitate interactions spanning virtual and physical boundaries; encourage serendipitous interaction (Holland et al., 2002b), and to enable the incremental development of novel interactions by end-user programming (Holland, 2003). While the potential of Direct Combination has been widely noted (e.g. Beaudouin-Lafon and Mackay, 2000, Rekimoto, 2004, Bartoleo et al, 2006 , Webb, 2017, Agarwal et al, 2019) existing implementations have been constrained by the limitations of available mechanisms for the modelling of separation of concerns in multi-dimensional domain models. > > However, new mechanisms that facilitate separation of concerns, in particular the revised version of Stateful Traits (Tesone et al., 2020) have created new opportunities for building highly expressive Direct Combination engines. Reenaskaugâs Data-Context-Interaction Paradigm (Reenskaug, 2006; James Coplien and Trygve Reenskaug, 2012) has also contributed relevant insights. > > As well as prototyping the new DC engine, the project will prototype support tools. To this end, the project will also involve analysing and creating informal domain models for one or two end-user domains, anticipated to be an AR/VR game in Unity (linked via a simple OSC bridge) and possibly an interface to allow end users and music scholars to query, analyse and visualise large quantities of linked music data on the web (via SPARQL). > > The choice of Smalltalk as preferred development environment reflects the fact that three previous implementations of Direct Combination at the Open University, and the reference implementations of both Stateful Traits and DCI, were all developed in Smalltalk (variously in Squeak, VisualWorks and Pharo). At the same time, the pervasively live-object nature of Smalltalk and its sophisticated IDE, along with the powerful metaprogramming facilities, offer substantial advantages in facilitating rapid prototyping and exploration. > > References > > Agarwal, Mallika, Arjun Srinivasan, and John Stasko. (2019) "VisWall: Visual Data Exploration Using Direct Combination on Large Touch Displays." 2019 IEEE Visualization Conference (VIS). IEEE, 2019 > > Bartolomeo, G., BlefariMelazzi, N., Cortese, G., Friday, A., Prezerakos, G., Walker, R. and Salsano, S., 2006, February. Sms: Simplifying mobile services-for users and service providers. In Advanced Int'l Conference on Telecommunications and Int'l Conference on Internet and Web Applications and Services (AICT-ICIW'06) (pp. 209-209). IEEE. > > Beaudouin-Lafon, M. and Mackay, W.E., 2000, May. Reification, polymorphism and reuse: three principles for designing visual interfaces. In Proceedings of the working conference on Advanced visual interfaces (pp. 102-109). > > James Coplien and Trygve Reenskaug (2012) The data, context and interaction paradigm. In SPLASH '12: Proceedings of the 3rd annual conference on Systems, programming, and applications: software for humanity. > > Gedenryd, H. (2002). Beyond Inheritance, Aspects and Roles: a Unified Scheme for Object and Program Composition. TR2002/09, Department of Computing, The Open University, Milton Keynes, MK76AA, UK. > > Holland, S. and Oppenheim, D. (1999) Direct Combination. Proceedings of CHI 1999 pp. 262-269. > > Holland, S., Morse, D.R., Gedenryd, H. (2002a) Direct Combination: a New User Interaction Principle for Mobile and Ubiquitous HCI. In Paterno, F., (Ed.) (2002) Human Computer Interaction with Mobile Devices. Mobile HCI 2002. > > Holland, Simon; Gedenryd, Henrik and Morse, David (2002b). Applying Direct Combination to afford spontaneity in Pervasive Computing. In: Workshop on Supporting Spontaneous Interaction in Ubiquitous Computing Settings, 29 Sep - 1 Oct 2002, Gothenburg, Sweden. > > Reenskaug, T. (2006) DCI Documentation http://heim.ifi.uio.no/~trygver/themes/babyide/baby-documents.html <http://heim.ifi.uio.no/~trygver/themes/babyide/baby-documents.html> (Accessed 19 Dec 2020) > > Holland, Simon (2005). A first empirical study of direct combination in a ubiquitous environment. In: Fincher, Sally; Markpoulos, Panos; Moore, David and Ruddle, Roy eds. People and computers XVIII - Design for life: proceedings of HCI 2004. London, UK: Springer, pp. 229â247. > > Holland, Simon (2003). Ambient Combination: Applying Direct Combination to Afford Spontaneity in Pervasive Computing . http://mcl.open.ac.uk/DC/uploads/Ambient%20Combination%20Long.pdf <http://mcl.open.ac.uk/DC/uploads/Ambient%20Combination%20Long.pdf> (accessed 10 Jan 2021) > > Rekimoto, J. (2004). SyncTap: synchronous user operation for spontaneous network connection. Personal and Ubiquitous Computing, 8(2), 126-134. > > Pablo Tesone, StÃ©phane Ducasse, Guillermo Polito, Luc Fabresse, Noury Bouraqadi (2020) A new modular implementation for stateful traits, Science of Computer Programming, Volume 195, 102470, ISSN 0167-6423, https://doi.org/10.1016/j.scico.2020.102470 <https://doi.org/10.1016/j.scico.2020.102470>. > > Webb, A.M., 2017. Phrasing Bimanual Interaction for Visual Design (Doctoral dissertation). > > > > > > > > > > _______________________________________________ > Esug-list mailing list > Esug-list(a)lists.esug.org > http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org -------------------------------------------- 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

1 0

Jan. 25, 2021

Dear happy Pharoers, First we wish you a good 2021 year. We really hope that we will get out of this situation. On the Pharo side we have excellent news. Pharo 90 is continuing to follow its roadmap and it will be another version a massive amount of improvements. We will mention them in the Pharo 90 announce but we can cite a few: Spec2, new tools, new debugger framework, better parser, general speedup, new optimisations, full block and clean block closures, support for large images, new fluid class syntax, ... The key and important advance is that the VM roadmap is delivering. 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 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. We are currently fixing ephemerons since they never really worked in Pharo. We are stressing the infrastructure with more than 50000 ephemerons. Also, we are improving and cleaning up the primitive invocation scheme to fix heap corruption issues, and fixing many open issues in the VM. Finally, we are working a lot to have a reproducible build in all the platforms and easing the path to VM development, we are still far from our objective but the improvements are starting to show. We are happy that following the roadmap that was decided during General assembly of PharoDays is successful. We have been investing in the Pharo VM and that our efforts are greatly paying off. This is the current status around the VM - We implemented a full backend for the JIT compiler targeting ARMv8 (AARCH64) - We launched the beta version for Windows, Linux and raspberry of the new 64 JIT ARM. - We are waiting to receive a new mac machine to be able to test our new JIT on it. - All the image side was adapted to run on it, tested on Ubuntu ARM 64 bits and Windows ARM. - We have support for all third party libraries in these platforms: Iceberg (Libgit) / Athens (Cairo) / SDL / GTK. - We implemented a LibFFI-based FFI backend as the default one for Pharo 9 in aarch64 (It is also present in other platforms, keeping the existing one as fallback, e.g. used when the VM is not the latest). - We revisited the complete compilation chain on Windows to use CMake and avoid Cigwin dependency. - We are starting to use OBS to build for multiple Unix and Linux distributions (Debian-like is Done, More distributios to come). - Many bugs on the VM have been fixed, for all these bugs tests have been written to detect regressions and to to document the solution. - We are always performing clean-ups of the VM base code: removing dead-code and experiments from the main branch. All removed code is kept in the history and it is accessible to revisit or to improve to the level that is required to be integrated (e.g., Newspeak Support, Lowcode) - We improved the implementation of Windows Network primitives, and we have done a clean-up of the event handling code allowing an IDLE VM. - We are starting to improve the JIT compiler. We are applying some approaches developed in modern compiler such as bloc representation. - We are working in statistics collection to characterize the behavior of different components of the VM. - We are planning to generate a set of benchmarks that correctly represents the workload of applications using the VM (e.g, Web Server, Interactive Applications, FFI intensive applications). It means that in the near future we expect to be able to improve even more our VM applying a scientific approach: measure, assess, improve. - We expect that for Pharo 10, we will continue to clean the VM code and be more agile. - We will able to look again at Sista. All these steps show that we are in much better situation. We drastically reduce the truck factor around the VM. It particularly means that the consortium now does not depend of the good will and knowledge of other people. We want to thank every member of the consortium. Now we have a particular thank to Lifeware that renewed their contract and Schmidt Buro for their original contract. A last word â do not hesitate to contact us, we are here to help you growing your business. S. Ducasse on the behalf of the Pharo consortium -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr <http://stephane.ducasse.free.fr/> / http://www.pharo.org <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 -------------------------------------------- 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

1 0

[ANN] Next Pharo Sprint: Jan 29
by Marcus Denker Jan. 25, 2021

Jan. 25, 2021

We will organize a Pharo sprint / Moose dojo Jan 29 (this Friday) 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