- Pharo-dev - lists.pharo.org

Re: [Pharo-users] Pharo-vm mailing-list

by Norbert Hartl

Good move. There should be more interest in vm topics. thanks, Norbert > Am 01.07.2022 um 22:47 schrieb stephane ducasse <stephane.ducasse(a)inria.fr>: > > Hi > > Since a couple of years the Pharo crew has been working on the Pharo-vm and most of the communication was using internal channels. > > Now that the community is growing we believe that it is important to have a public way to communicate around the VM and our current and future developments. > > We are happy to announce that we set up a mailing-list for the Pharo-vm. > > https://lists.pharo.org/list/pharo-vm.lists.pharo.org <https://lists.pharo.org/list/pharo-vm.lists.pharo.org> > > Stef on the behalf of the Pharo lille crew. > > >

July 2, 2022

Pharo-vm mailing-list

by stephane ducasse

Hi Since a couple of years the Pharo crew has been working on the Pharo-vm and most of the communication was using internal channels. Now that the community is growing we believe that it is important to have a public way to communicate around the VM and our current and future developments. We are happy to announce that we set up a mailing-list for the Pharo-vm. https://lists.pharo.org/list/pharo-vm.lists.pharo.org <https://lists.pharo.org/list/pharo-vm.lists.pharo.org> Stef on the behalf of the Pharo lille crew.

July 1, 2022

This week (26/2022) on the Pharo Issue Tracker

by Marcus Denker

We merged ~15 Pull Requests this week, Compiler ======== More infos about the isForScripting cleanup: https://lists.pharo.org/empathy/thread/QR5NM2Z5CFYEI2EYN42O35UQBB3CGG6O - Compiler: Another small cleanup related to #interactive #11409 https://github.com/pharo-project/pharo/pull/11409 - Compiler small cleanups after DoItIn: cleanup #11403 https://github.com/pharo-project/pharo/pull/11403 - 9921-unify-isScripting-and-isForScripting #11416 https://github.com/pharo-project/pharo/pull/11416 - Cleanup-add-isScripting #11412 https://github.com/pharo-project/pharo/pull/11412 <https://github.com/pharo-project/pharo/pull/11412> - Added hooks to locally redefine the formatter #11318 https://github.com/pharo-project/pharo/pull/11318 Refactoring Engine =========== - Replacing method command refactorings with transformations from Ref2 #11417 https://github.com/pharo-project/pharo/pull/11417 - Replacing refactorings #11401 https://github.com/pharo-project/pharo/pull/11401 Features ======== - Autocomplete Spotter with current selection #11418 https://github.com/pharo-project/pharo/pull/11418 https://github.com/pharo-spec/NewTools/pull/386 Fixes ===== - DrTests fix - do not assume the selectIndex will trigger an event #11423 https://github.com/pharo-project/pharo/pull/11423 - Integrate Roassal3 v0.9.9h #11415 https://github.com/pharo-project/pharo/pull/11415 - fixing createSubclassResponsibility not to allow creating a subclass responsibility in a super class of the abstract class #383 https://github.com/pharo-spec/NewTools/pull/383 Cleanup ======= - Rules-add-missing-group #11424 https://github.com/pharo-project/pharo/pull/11424 - [cleanup] random cleanup of a missing word and two protocols that werâ¦ #381 https://github.com/pharo-spec/NewTools/pull/381 - DesktopMenuPragmaKeyword-Symbol #11422 https://github.com/pharo-project/pharo/pull/11422

July 1, 2022

Re: [Compiler API] unifying isScriping / isForScripting / isWorkspace

by Marcus Denker

> On 28 Jun 2022, at 09:29, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > This is not directly the compiler API, but the API used by tools (e.g. requestors): > > There where three methods to test if the requestor operates on whole methods or not. > > - isWorkspace > - isScripting > - isForScripting > > This had lead to odd bugs in the past that something that was tested for one requestor failed if used in another context. > (For that, we added both #isScripting and #isForScripting for some cases already). > > This Issue points to a series of PRs that unifies the situation: > > unify #isScripting and #isForScripting #9921 > https://github.com/pharo-project/pharo/issues/9921 > > > Note: it is not really possible to do this backward compatible in a nice way, but the good news is that this is an API used for tools that should not be used normally outside of the development tools themselves. > There are two PRs to be reviewed: 1) spec https://github.com/pharo-spec/Spec/pull/1289 <https://github.com/pharo-spec/Spec/pull/1289> 2) rest of the system: https://github.com/pharo-project/pharo/pull/11416 <https://github.com/pharo-project/pharo/pull/11416> Marcus

June 28, 2022

[Compiler API] unifying isScriping / isForScripting / isWorkspace

by Marcus Denker

This is not directly the compiler API, but the API used by tools (e.g. requestors): There where three methods to test if the requestor operates on whole methods or not. - isWorkspace - isScripting - isForScripting This had lead to odd bugs in the past that something that was tested for one requestor failed if used in another context. (For that, we added both #isScripting and #isForScripting for some cases already). This Issue points to a series of PRs that unifies the situation: unify #isScripting and #isForScripting #9921 https://github.com/pharo-project/pharo/issues/9921 Note: it is not really possible to do this backward compatible in a nice way, but the good news is that this is an API used for tools that should not be used normally outside of the development tools themselves. Marcus

June 28, 2022

Traits-Based Collections, Streams, Etc

by sean＠clipperadams.com

What ever happened to this work? It was exciting and seemed valuable but never made it into Pharo. The traited collections \[1\] seemed particularly interesting and useful 1 https://www.researchgate.net/profile/Damien-Pollet/publication/45942931_BLO…

June 25, 2022

Re: [Compiler] Variables in DoIts

by Guillermo Polito

> El 25 jun 2022, a las 14:38, Denis Kudriashov <dionisiydk(a)gmail.com> escribiÃ³: > > Now we can play with other interesting options. > We can completely remove reformatting of code for DoIts and make the debugging more "transparent" for users: > > <simpleDoIt.png> > > Notice there is no DoIt header anymore . What is selected for the DebugIt command is what the user really sees in the debugger. > I remember when for the first time I tried the smalltalk environment DoIt methods were a real magic for me. With this view I would have much less questions. > > What do you think? > I like this much much better than what was that before!! Iâd suggest, for further improvement (but not blocking), that Iâd like to see the entire code and context of the do-it context. Just showing the selected text makes one lose context. Instead, it would be super cool to show the entire context + code of where the selection was done, and that the program counter is set where the selection was set. Of course, now that Iâm thinking about it, I would wonder how to resolve when to *stop*. Only showing the selected code solves visually the *stopping*. It is clear that evaluation stops when we arrive at the end. G

June 25, 2022

Re: [Compiler] Variables in DoIts

by Denis Kudriashov

Now we can play with other interesting options. We can completely remove reformatting of code for DoIts and make the debugging more "transparent" for users: [image: simpleDoIt.png] Notice there is no DoIt header anymore . What is selected for the DebugIt command is what the user really sees in the debugger. I remember when for the first time I tried the smalltalk environment DoIt methods were a real magic for me. With this view I would have much less questions. What do you think?

June 25, 2022

[Compiler] Variables in DoIts

by Marcus Denker

Hi, We finally merged a PR form Denis (Sorry for taking too longâ¦) that enables the use of DoitVariable in DoItIn: methods: Denis: #pharo has finally transparent variables in the debugger doIts. No ThisContext readVariable trick And we could even get rid of #DoItIn:, after merging another small cleanup, both methods now is just #DoIt as a selector. How does it work? Denis: It is the power of first class variables. There is DoItVariable fully integrated now which represents variables from different context Marcus: DoitVariable has the original Variable instance and the context (what used to the ThisContext parameter of DoItIn:). It can be read reflectively by sending #read, compiler delegates code generation to the Variables (#emitValue:)

June 24, 2022

This week (25/2022) on the Pharo Issue Tracker

by Marcus Denker

We merged 17 PRs this week. The main news is that DoIts that evaluate against a context (e.g. printing a value of a temp variable in the debugger) now use normal variables names (PR 9588). #DoItIn: is gone, as the parameter is not needed anymore (PR 11402) And PR#11379 enables IM support in SDL2: Some natural languages needs a support agent so-called IM to input letters/symbols including emojis. Compiler ======== - [Compiler] Reify OCSemanticScope's representing the meaning of the code: a method or a doIt expressions #9588 https://github.com/pharo-project/pharo/pull/9588 - Compiler-Cleanup-OldDoItTransformations #11402 https://github.com/pharo-project/pharo/pull/11402 - OpalCompiler-Simplify-interactive #11392 https://github.com/pharo-project/pharo/pull/11392 - Simplify-BytecodeGenerator-AdditionalLiterals #11383 https://github.com/pharo-project/pharo/pull/11383 - Cleanup-IRClosureStackCount #11387 https://github.com/pharo-project/pharo/pull/11387 Reduce Symbol creation ======================= Some more simple changes to avoid creating new symbols during interactive use - 11394-Cursor-classresizeForEdge-should-hard-code-common-cases #11395 https://github.com/pharo-project/pharo/pull/11395 - IconNames-06-21 #11393 https://github.com/pharo-project/pharo/pull/11393 - Symbol-intern-blankIconOfWidth #11385 https://github.com/pharo-project/pharo/pull/11385 - Icon renames #380 https://github.com/pharo-spec/NewTools/pull/380 - IconNames-06-21 #1282 https://github.com/pharo-spec/Spec/pull/1282 Fixes ===== - fix 8661: enables IM support in SDL2 #11379 https://github.com/pharo-project/pharo/pull/11379 - 11388 - show context menu even when no item is selected #11398 https://github.com/pharo-project/pharo/pull/11398 - revert #9765 #11397 https://github.com/pharo-project/pharo/pull/11397 - chore(Fuel): update to 5.1.0 #11384 https://github.com/pharo-project/pharo/pull/11384 Features ======== - TestRunner #11372 Experimental new testrunner model https://github.com/pharo-project/pharo/pull/11372 - Add SpModelChangedPort #1279 https://github.com/pharo-spec/Spec/pull/1279 Documentation ============== - fix download link 32 bit #3 https://github.com/pharo-project/pharo-site/pull/3

June 24, 2022