- Pharo-dev - lists.pharo.org

Re: [Compiler] Variables in DoIts

by Denis Kudriashov

Hi. ÑÐ±, 25 Ð¸ÑÐ½. 2022 Ð³. Ð² 13:48, Guillermo Polito <guillermopolito(a)gmail.com>: > 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*. > In theory we can highlight the code from the full outer context as something inactive or we can try to draw the border over a selection. I did a little experiment but it does not look good. And I am not sure how useful it will be: [image: shadowDoIt.png]

July 24, 2022

Re: [Compiler] Variables in DoIts

by Marcus Denker

The next steo of this has been merged: we now evaluate DoIt methods in a way that we do not - need a method header - need to transfrom the AST for adding a return See the (now merged) PR of Denis here: https://github.com/pharo-project/pharo/pull/11463 This means that DoiT evaluation does not rely on the parse tree rewriter and does not need to be pretty-printed anymore. (which dies speed up #evaluate:, too). The screenshot shows code from a Playground, setting a playground binding a to 1, then a temp b to 2, then it enters the debugger due to the #halt. In the debugger we can read a and b, and we can eval âb haltâ to see that what used to be a âDoItIn:â accessing b via the context now looks just like the code that we executed from the first debugger: > On 24 Jun 2022, at 13:51, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > We finally merged a PR form Denis (Sorry for taking too longâ¦) that enables the use of DoitVariable in DoItIn: methods: > > > <Dionisiydk_2022-Jun-23.jpeg> > 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:) > > <DoItVariable.png>

July 21, 2022

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

by Marcus Denker

Works is slowing down with summer holidays starting in some parts of the world. But we managed to merge 8 PRs this week: Compiler ======== Main change of the weeks is that we now can compile DoIts without a method header and without the need of code reformatting (without having to add a return). - DoIts without method header and reformatting #11463 https://github.com/pharo-project/pharo/pull/11463 - Fix code highlighting for no-header doIts #1296 https://github.com/pharo-spec/Spec/pull/1296 - Fix code highlighting for no-header doIts #400 https://github.com/pharo-spec/NewTools/pull/400 Features ======== - Adding possibility to add bindings in debugger context interaction model #378 https://github.com/pharo-spec/NewTools/pull/378 Bug Fixes ========= - fixes: problem size of columns when updating inspector (Newtools #395) #1294 https://github.com/pharo-spec/Spec/pull/1294 Cleanup ======== - Integer: add missing #subclassResponsibility #11471 https://github.com/pharo-project/pharo/pull/11471 - tag AbstractBinaryFileStream as abstract #11472 https://github.com/pharo-project/pharo/pull/11472 - Deprecate-theMetaClass-theNonMetaClass #11467 https://github.com/pharo-project/pharo/pull/11467

July 21, 2022

Re: [Pharo-users] Looking for North American programming language/Smalltalk researchers (academic or industry)

by Sean DeNigris

Great idea! Definitely interested... > Given the success of Camp Smalltalk Supreme, Richard and I were wondering if there is interest in a 3rd research Smalltalk conference (alongside ESUG/IWST and FAST/Smalltalks) oriented to North American Smalltalkers.. > > It would probably take place in May/June, and probably in/around Toronto. > > So Iâm looking for people interested in being on a program committee.

July 18, 2022

Re: [Pharo-users] Looking for North American programming language/Smalltalk researchers (academic or industry)

by Yanni Chiu

Iâd be interested to be on the committee. Any date is okay, since Iâm local to Toronto. It would be good to have a real âCamp Smalltalkâ where we could have a time and place to code together. There hasnât been a big Smalltalk event in Toronto since the 1990âs, IIRC. Itâd be great if Richard has actually sparked a âSmalltalk Renaissanceâ (a least in Toronto). Cheers, Yanni Chiu On Thu, Jul 14, 2022 at 11:35 AM David Mason <dmason(a)ryerson.ca> wrote: > Given the success of Camp Smalltalk Supreme, Richard and I were wondering > if there is interest in a 3rd research Smalltalk conference (alongside > ESUG/IWST and FAST/Smalltalks) oriented to North American Smalltalkers.. > > It would probably take place in May/June, and probably in/around Toronto. > > So Iâm looking for people interested in being on a program committee. > > Thanks > > ../Dave >

July 17, 2022

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

by Marcus Denker

Fixes ===== - Fix-Menu-Inspector-Meta #387 https://github.com/pharo-spec/NewTools/pull/387 - Updating Sindarin to Pharo-11 branch #393 https://github.com/pharo-spec/NewTools/pull/393 - Inspector columns cannot be resized #9828 https://github.com/pharo-spec/Spec/pull/1293 Virtual Machine ================ - Cleanup-M1-Variadic-FFI-Tests #11421 https://github.com/pharo-project/pharo/pull/11421 - Pharo Image support for Pharo VM's arithmetic SIMD bytecodes #11446 https://github.com/pharo-project/pharo/pull/11446 Cleanup ====== - code critique cleanup of some methods related to #category #11452 https://github.com/pharo-project/pharo/pull/11452 - Remove extra statement separator (dot) #11456 https://github.com/pharo-project/pharo/pull/11456 - remove-filteredResult #11460 https://github.com/pharo-project/pharo/pull/11460 - Replace deprecated calls to #'theMetaClass' with #'classSide' #11464 https://github.com/pharo-project/pharo/pull/11464 - Replace calls to #'theNonMetaClass' with #'instanceSide' #11465 https://github.com/pharo-project/pharo/pull/11465 - Optimized-timesRepeat #394 https://github.com/pharo-spec/NewTools/pull/394

July 15, 2022

Re: [Pharo-users] Looking for North American programming language/Smalltalk researchers (academic or industry)

by James Foster

Yes, Iâm interested but would prefer the second half of June (our school is on the quarter system) and would prefer weekdays rather than weekends. James Foster > On Jul 14, 2022, at 8:35 AM, David Mason <dmason(a)ryerson.ca> wrote: > > Given the success of Camp Smalltalk Supreme, Richard and I were wondering if there is interest in a 3rd research Smalltalk conference (alongside ESUG/IWST and FAST/Smalltalks) oriented to North American Smalltalkers.. > > It would probably take place in May/June, and probably in/around Toronto. > > So Iâm looking for people interested in being on a program committee. > > Thanks > > ../Dave

July 15, 2022

This week (27/2022) on the Pharo Issue Tracker MD

by Marcus Denker

We merged 12 PRs this week: Features ======= - Allow creating Pharo methods using the Bytecode IR #11437 https://github.com/pharo-project/pharo/pull/11437 - Show keyboard shortcuts on Debugger commands' tooltips https://github.com/pharo-spec/NewTools/pulse - Allow to add an image directly from layout #1285 https://github.com/pharo-spec/Spec/pull/1285 - Add drop list column support in tables #1290 https://github.com/pharo-spec/Spec/pull/1290 Bugs ==== - fix ShiftClassInstaller that fails to migrate some objects #11442 https://github.com/pharo-project/pharo/pull/11442 - Revert "Replacing method command refactorings with transformations from Ref2" #11438 https://github.com/pharo-project/pharo/pull/11438 Memory ====== do not store the commentSourcePointer in the class Organizer. Work in progress, see https://github.com/pharo-project/pharo/issues/10958 Add commentSourcePointer to ClassDescription #11326 https://github.com/pharo-project/pharo/pull/11326 fix-tests-commentSourcePointer #11441 https://github.com/pharo-project/pharo/pull/11441 Cleanup ====== - remove the Deprecated10 package #11426 https://github.com/pharo-project/pharo/https://github.com/pharo-project/pha… - reduce-asSymbol-in-tools #11436 https://github.com/pharo-project/pharo/pull/11436 - Cleanup: Deprecate FFIExternalReference>>#handle: and FFIExternalReference>>#handle #11431 https://github.com/pharo-project/pharo/pull/11431 - Cleanup-asRingMinimalDefinitionIn-Parent #11440 https://github.com/pharo-project/pharo/pull/11440

July 8, 2022

Fwd: [Esug-list] [ESUG 2022] Innovation Technology Awards

by stephane ducasse

> Begin forwarded message: > > From: Noury Bouraqadi <bouraqadi(a)gmail.com> > Subject: [Esug-list] [ESUG 2022] Innovation Technology Awards > Date: 20 June 2022 at 11:55:43 CEST > To: Members ESUG <esug-list(a)lists.esug.org> > > Dear fellow Smalltalkers, > > ESUG conference is a great event with multiple opportunities to discover and exchange. > One of them is the Innovation Technology Awards. > > This is a great opportunity to demo and discuss smart and cool Smalltalk software you've been developing the last 2 years. > All Smalltalk flavors are welcome! > > Submit your project now > https://esug.github.io/2022-Conference/awardsCall2022.html <https://esug.github.io/2022-Conference/awardsCall2022.html> > On Behalf of the ESUG Board, > Noury > _______________________________________________ > Esug-list mailing list -- esug-list(a)lists.esug.org > To unsubscribe send an email to esug-list-leave(a)lists.esug.org

July 3, 2022

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