- Pharo-dev - lists.pharo.org

Confusing Refactoring Pull Up dialog

by Aik-Siong Koh

There are two questions, but only response accepted. I just want a pull up with nothing extra done. If I click yes, I get the extra methods. If I click no, nothing at all happens. Please advise, Thanks, Aik-Siong Koh

June 28, 2025

Re: Variable references, readers, writers

by Marcus Denker

This is the code that uses assignmentNodes: ((Point slotNamed: #x) assignmentNodes collect: [ :each | each methodNode compiledMethod ] ) asSet But as a downside, it has to create the AST. So maybe better is to use the API of the Variable: Point methods select: [ :each | (Point slotNamed: #x) isWrittenIn: each ] This is implemented to scan on the bytecode level for InstanceVariableSlot and thus is much faster: InstanceVariableSlot>>#isWrittenIn: ^aCompiledCode writesField: index > On 28 Jun 2025, at 00:38, steven.costiou(a)kloum.io wrote: > > Yes, to a variable (so including slots and all) you can ask readNodes and assignmentNodes (accessingNodes gives both). > It gives nodes from the AST, but from there you can obtain the methods and everything. > > Le 27.06.2025 22:27, Aik-Siong Koh a Ã©crit : >> A variable can have references. >> Those references can be split into readers and writers of the variable. >> Can Pharo list readers and writers separately? >> Thanks, >> Aik-Siong Koh

June 28, 2025

Re: Variable references, readers, writers

by steven.costiou＠kloum.io

Yes, to a variable (so including slots and all) you can ask readNodes and assignmentNodes (accessingNodes gives both). It gives nodes from the AST, but from there you can obtain the methods and everything. Le 27.06.2025 22:27, Aik-Siong Koh a Ã©critÂ : > A variable can have references. > Those references can be split into readers and writers of the variable. > Can Pharo list readers and writers separately? > Thanks, > Aik-Siong Koh

June 27, 2025

Re: Does not understand message inconsistency

by Aik-Siong Koh

"nil did not understand #selector" is great. Similarly, "Instance of " can be replace by "a" as in "aObject did not understand #selector" "aReadWriteStream did not understand #selector" For classes "PragmaMenuBuilder class did not understand #selector" Daniel Slomovits wrote: > I think it's because nil *is* pretty special--this is the equivalent > of a NullPointerException or similar in other languages (even though > in fact nil is an object like any other, it *is* usually a different > type of *semantic* error on the part of the programmer than with any > other class). UndefinedObject is also a pretty long class name, so > it's nice to leave that out. But I would be all in favor of making it > "nil did not understand #selector", to be more consistent but still > concise. > > On Fri, Jun 27, 2025, 3:00â¯PM Aik-Siong Koh <askoh(a)askoh.com > <mailto:askoh@askoh.com>> wrote: > > Why is UndefinedObject version of "did not understand" so > different from > others? > It also inverts the object message paradigm. > Thanks > Aik-Siong Koh > > description > > Â Â Â Â "Returns a textual description of the exception (based on the > message instance variable). If message is nil, it returns the > defaultDescription instead." > > Â Â Â Â message ifNil: [ ^ self defaultDescription ]. > Â Â Â Â message lookupClass == UndefinedObject ifTrue: [ > Â Â Â Â Â Â Â ^ message selector printString , ' was sent to nil' ]. > > Â Â Â Â ^ 'Instance of ' , message lookupClass printString > Â Â Â Â Â , ' did not understand ' , message selector printString >

June 27, 2025

Variable references, readers, writers

by Aik-Siong Koh

A variable can have references. Those references can be split into readers and writers of the variable. Can Pharo list readers and writers separately? Thanks, Aik-Siong Koh

June 27, 2025

Re: Does not understand message inconsistency

by Daniel Slomovits

I think it's because nil *is* pretty special--this is the equivalent of a NullPointerException or similar in other languages (even though in fact nil is an object like any other, it *is* usually a different type of *semantic* error on the part of the programmer than with any other class). UndefinedObject is also a pretty long class name, so it's nice to leave that out. But I would be all in favor of making it "nil did not understand #selector", to be more consistent but still concise. On Fri, Jun 27, 2025, 3:00â¯PM Aik-Siong Koh <askoh(a)askoh.com> wrote: > Why is UndefinedObject version of "did not understand" so different from > others? > It also inverts the object message paradigm. > Thanks > Aik-Siong Koh > > description > > "Returns a textual description of the exception (based on the > message instance variable). If message is nil, it returns the > defaultDescription instead." > > message ifNil: [ ^ self defaultDescription ]. > message lookupClass == UndefinedObject ifTrue: [ > ^ message selector printString , ' was sent to nil' ]. > > ^ 'Instance of ' , message lookupClass printString > , ' did not understand ' , message selector printString >

June 27, 2025

Does not understand message inconsistency

by Aik-Siong Koh

Why is UndefinedObject version of "did not understand" so different from others? It also inverts the object message paradigm. Thanks Aik-Siong Koh description Â Â Â "Returns a textual description of the exception (based on the message instance variable). If message is nil, it returns the defaultDescription instead." Â Â Â message ifNil: [ ^ self defaultDescription ]. Â Â Â message lookupClass == UndefinedObject ifTrue: [ Â Â Â Â Â Â ^ message selector printString , ' was sent to nil' ]. Â Â Â ^ 'Instance of ' , message lookupClass printString Â Â Â Â , ' did not understand ' , message selector printString

June 27, 2025

[ANN] Pharo 13.1 released

by Esteban Lorenzano

Hi, We just released Pharo 13.1 with some quality of life improvements we merged since version 13.0: Whatâs Changed * update new tools to v0.10.4 and spec to v2.0.3 by @estebanlm in https://github.com/pharo-project/pharo/pull/18313 * bump iceberg to v2.4.1 by @estebanlm in https://github.com/pharo-project/pharo/pull/18210 * Fix for #18225: Be robust against unintentionally sending #initialize to a Trait (Pharo 13) by @MarcusDenker in https://github.com/pharo-project/pharo/pull/18238 * [P13 Backport] Fix: Rubric error when jumping to previous word and string begins with separators by @Gabriel-Darbord in https://github.com/pharo-project/pharo/pull/18232 * [Pharo13] Adding validation of the hierarchy for all the slots by @tesonep in https://github.com/pharo-project/pharo/pull/18243 * Fix closing window shortcuts in combination with window groups by @guillep in https://github.com/pharo-project/pharo/pull/18116 * Fixing the Toplo Version by @tesonep in https://github.com/pharo-project/pharo/pull/18263 * [Pharo13] Update Roassal to new Released version by @tesonep in https://github.com/pharo-project/pharo/pull/18262 * Fix cursor on multiple OSWindows by @tinchodias in https://github.com/pharo-project/pharo/pull/18280 * Backport #18289 to P13: Fix Duplicate class refactoring by @jecisc in https://github.com/pharo-project/pharo/pull/18290 * rename examples and ClapHelp command by @demarey in https://github.com/pharo-project/pharo/pull/18312 *Full Changelog*: https://github.com/pharo-project/pharo/compare/v13.0.0...v13.1.0 Cheers, Esteban 

June 26, 2025

Pharo News of the Week 25/2025

by Marcus Denker

- GitProjectHealth: A Mining Software Repository and Ticket management Platform tool, in Pharo https://github.com/moosetechnology/gitprojecthealth - [ANN] Pharo client libraries for Google Cloud Platform services https://github.com/newapplesho/google-cloud-smalltalk - ESUG Tech Awards 2025: Deadline June 30 https://esug.org/2025-Conference/awardsCall2025.html - [ANN] Containers-Buffer: Circular buffer implementation with LIFO and FIFO variants https://github.com/pharo-containers/Containers-Buffer - [ANN] Hera, a BDD framework for Pharo https://all-objects-all-the-time.st/#/blog/posts/14 If you want to add your news to this list, use this form: https://tinyurl.com/4c89buy4 # The week on the Pharo Issue Tracker # Pharo 13 - Backport #18289 to P13: Fix Duplicate class refactoring #18290 https://github.com/pharo-project/pharo/pull/18290 - Fix cursor on multiple OSWindows #18280 https://github.com/pharo-project/pharo/pull/18280 - backport modal testing #1783 https://github.com/pharo-spec/Spec/pull/1783 # Fixes - New Cavrois Integration block in Morphic to cut direct code #18288 https://github.com/pharo-project/pharo/pull/18288 - Fix multiple Rubric examples and add smoke tests #18281 https://github.com/pharo-project/pharo/pull/18281 - Fix MessagTally>>exampleSpyForSeconds #18278 https://github.com/pharo-project/pharo/pull/18278 - Cut cyclic dependency in Zinc #18109 https://github.com/pharo-project/pharo/pull/18109 # Completion - Adding fetcher to NecEntry and subclasses #18269 https://github.com/pharo-project/pharo/pull/18269 # Refactoring Engine - Fix Duplicate class refactoring if there are spaces in package or package tag #18289 https://github.com/pharo-project/pharo/pull/18289 - Fix pullUpMethod in presence of used instance variables #18285 https://github.com/pharo-project/pharo/pull/18285 # Tools - Fix example of StOpenFilePresenter #1169 https://github.com/pharo-spec/NewTools/pull/1169 - Fix ProtocolChooserPresenter #1168 https://github.com/pharo-spec/NewTools/pull/1168 - renamed menu items / usage of strategies to position back windows #1167 https://github.com/pharo-spec/NewTools/pull/1167 - Improve new transcript #1166 https://github.com/pharo-spec/NewTools/pull/1166 - Fix for okbutton rename protocol #1165 https://github.com/pharo-spec/NewTools/pull/1165 # Git Support - Fix some failing tests #1944 https://github.com/pharo-vcs/iceberg/pull/1944 - Fix git direct access to repository #1940 https://github.com/pharo-vcs/iceberg/pull/1940 - Added SyncToFiles command #1936 https://github.com/pharo-vcs/iceberg/pull/1936 # Cleanup - Remove dead code in PasteUpMorph #18279 https://github.com/pharo-project/pharo/pull/18279

June 20, 2025

Pharo Paper Collection: Papers wanted!

by Marcus Denker

Hello, As you might know, we have started to collect all papers / books that are related to Pharo. This is on HAL (https://hal.science) an international repository for open science that is used by the french science community (e.g. Inria and CNRS). The platform is open to anyone and after some years of iteration, it starts to be really quite nice. "HAL is a multidisciplinary open archive for the sharing of published and unpublished research. It is at the service of researchers in academic institutions, both public and private. In France, HAL is the national archive chosen by the scientific and academic community for the open dissemination of its research results. The repository is also at the service of researchers affiliated to foreign academic institutions, whether public or private.â More infos here: https://about.hal.science/en/ The Pharo collection on HAL now contains over 200 entries. The collection includes papers/books that are either about Pharo or use it in some way. https://hal.science/PHARO The HAL Monitor provides some more stats: https://monitor.hal.science/?collection=PHARO Of course, there are only those papers in the archive that the orginal authors added (and tagged for the Pharo Collection). To check if your paper is there, the easiest is to check the authors: https://inria.hal.science/PHARO/browse/author How do I add my papers? ===================== The HAL platform is open to everyone. https://hal.science - create an account - start submission by clicking submit. You are asked for all information / the PDF of your paper. - In the META Data: add âPHAROâ in the field âCollaboration/Projectâ. After the paper is validated, it will show up in the PHARO collection around one day later. If your paper is already in HAL: just modify the meta data and add âPHAROâ in the field âCollaboration/Projectâ

June 20, 2025