April 2023 - Pharo-users - lists.pharo.org

EXIF / JPEG metadata
by Alistair Grant Nov. 30, 2025

Nov. 30, 2025

Hi Everyone, As far as I can tell, JPEGReadWriter in Pharo 7 doesn't read (or write) the image metadata, e.g. title, keywords, exposure time, etc. Is anyone aware of a package that does? Thanks! Alistair

2 1

The System Browser has recently started showing 2 comments tabs - one is text and one is formatted pretty. That seems odd and is not wanted - has anyone else seen this? Pharo 10 stable image - windows 64 - all reloaded recently...
by mark.odonoghue.2010＠gmail.com May 12, 2024

May 12, 2024

![Image](https://media.discordapp.net/attachments/223421264751099906/1060833258427920385/image.png)

4 4

Re: [Pharo-users] Personal wiki / information manager
by Evan Donahue Sept. 25, 2023

Sept. 25, 2023

Seems that Pharo is a magnet for this kind of project. I've been writing one as well and using it to organize my research notes. Does anyone working on personal info mgmt tools want to talk offline? I expect we're running into some of the same issues, both conceptual and technical. Evan

18 33

Pharo being featured in Exercism's Mind Shifting May
by bajger＠gmail.com May 11, 2023

May 11, 2023

Hi there! Hi there! Pharo track will be promoted on Mind shifting May of Exercism initiative. Here are some details from one Exercism founder (Erik): \ \ https://forum.exercism.org/t/pharo-being-featured-in-mind-shifting-may/5420 There are couple of things we could improve here: \ where it is used: weâd definitely find better and newer examples that ATMs usecaseâ¦ where it is great: I would add productivity, once people get through initial learning curve. It is tightly connected to bullets below (image based approach and liveness and immersive env.) Features: embeddability and interoperability with othe PLs - working on minimal Pharo image that can be part of e.g. C program and vice versa. So if you have ideas, thoughts how this script can be improved, please reply!

4 4

Porting from VW to Pharo
by Steffen MÃ¤rcker May 8, 2023

May 8, 2023

Hi! this topic pops up from time to time on the mailing list. I want to port a number of packages to Pharo. I remember "Shaping" asking this for porting PDFtalk. 1. Is the workflow still up to date or is there a new way of doing things? 2. From what I understand so far, I just need the following package from Store: - Smalltalk Transform Project 3. Is there a page that documents the process process in general? https://wiki.pdftalk.de/doku.php?id=setupvisualworks seems to be specific for PDFtalk like the thread on this list. Kind regards, Steffen

5 14

Collection>>reduce naming
by Steffen MÃ¤rcker April 30, 2023

April 30, 2023

Hi! I wonder whether there was a specific reason to name this method #reduce:? I would have expected #fold: as this is the more common term for what it does. And in fact, even the comment reads "Fold the result of the receiver into aBlock." Whereas #reduce: is the common term for what we call with #inject:into: . I am asking not to annoy anyone but out of curiosity. It figured this out only by some weird behaviour after porting some code that (re)defines #reduce . Ciao! Steffen

4 22

This week (17/2023) on the Pharo Issue Tracker
by Marcus Denker April 28, 2023

April 28, 2023

# Pharo 11 - Refactor block ensure during termination to allow override #13534 https://github.com/pharo-project/pharo/pull/13534 # Pharo 12 ## Small Improvements - Small cleanup #bitShift:, #<< and #<< #13523 https://github.com/pharo-project/pharo/pull/13523 - Clean info of MethodChangeRecord #13519 https://github.com/pharo-project/pharo/pull/13519 - remove some methods that are just copied from a superclass #13504 https://github.com/pharo-project/pharo/pull/13504 - Some RPackage cleanups #13505 https://github.com/pharo-project/pharo/pull/13505 - Adding inspector transmission node #510 https://github.com/pharo-spec/NewTools/pull/510 ## Protocol - Use #protocolOfSelector: in CompiledMethod>>#category #13457 https://github.com/pharo-project/pharo/pull/13457 - Improve ClassDescription>>#addAndClassifySelector:withMethod:inProtocol: #13533 https://github.com/pharo-project/pharo/pull/13533 - Fix case were method is in a class but not in a protocol #13572 https://github.com/pharo-project/pharo/pull/13572 - Simplify ClassOrganization>>removeElement: and remove protocol if empty #13530 https://github.com/pharo-project/pharo/pull/13530 - Classify method before installing them #13539 https://github.com/pharo-project/pharo/pull/13539 - Make Protocol announcements use real protocols #13506 https://github.com/pharo-project/pharo/pull/13506 ## AST - Style literal arrays #13502 https://github.com/pharo-project/pharo/pull/13502 - Do not hardcode stylers #13537 https://github.com/pharo-project/pharo/pull/13537 - AST: cleanup scanner #13562 https://github.com/pharo-project/pharo/pull/13562 - AST: kill multiple keyword token #13554 https://github.com/pharo-project/pharo/pull/13554 - AST: cleanup compiler API (and clients) #13520 https://github.com/pharo-project/pharo/pull/13520 - AST: cleanup extension methods from OpalCompiler #13514 https://github.com/pharo-project/pharo/pull/13514 ## Compiler - Compiler: doSemanticAnalysis yourself #13517 https://github.com/pharo-project/pharo/pull/13517 - add new test RBCodeSnippet class>>#badScanner with special scanner hacks #13553 https://github.com/pharo-project/pharo/pull/13553 - Add compiler option to not optimise special sends #13569 https://github.com/pharo-project/pharo/pull/13569 - Factorize some code in recompilation management #13551 https://github.com/pharo-project/pharo/pull/13551 - Scope: generalize target class #13540 https://github.com/pharo-project/pharo/pull/13540 - RBMethodMode: compiledMethod sould be a simple accessor #13525 https://github.com/pharo-project/pharo/pull/13525 - Detach compilationContext a little #13511 https://github.com/pharo-project/pharo/pull/13511 - Reduce usage of compilationContext from IR* Classes #13513 https://github.com/pharo-project/pharo/pull/13513 ## CompiledMethod trailer cleanup - Compiler: Cleanup trailer for the frontend #13575 https://github.com/pharo-project/pharo/pull/13575 - Compiler: Cleanup for trailer removal in IRByteCodeGenerator #13565 https://github.com/pharo-project/pharo/pull/13565 - Cleanup: do not reference CompiledMethodTrailer in ReflectiveMethod #13564 https://github.com/pharo-project/pharo/pull/13564 - Cleanup: Fuel does not need to use #copyWithTrailerBytes: #13560 https://github.com/pharo-project/pharo/pull/13560 - Cleanup-instanceCreationCompiledMethod #13559 https://github.com/pharo-project/pharo/pull/13559 - Do not use #trailer to read the sourcePointer #13558 https://github.com/pharo-project/pharo/pull/13558 - getSourceFromFile-return-nil #13556 https://github.com/pharo-project/pharo/pull/13556 - Cleanup: CompiledMethodTrailer should not create methods #13555 https://github.com/pharo-project/pharo/pull/13555 - CompiledMethodTrailer-Cleanup-even-more #13550 https://github.com/pharo-project/pharo/pull/13550 - CompiledMethodTrailer: more cleanup, do not use it for #endPC #13546 https://github.com/pharo-project/pharo/pull/13546 - CompiledMethodTrailer: remove #VarLengthSourcePointer support #13545 https://github.com/pharo-project/pharo/pull/13545 - CompiledMethodTrailer: use 4 bytes as sourcePointer #13527 https://github.com/pharo-project/pharo/pull/13527 - Cleanup-Tests-CompiledMethodTrailer #13528 https://github.com/pharo-project/pharo/pull/13528 - Cleanup-CompiledMethod-Source-Embedding #13522 https://github.com/pharo-project/pharo/pull/13522 - remove all unsused encodings from CompiledMethodTrailer. #13510 https://github.com/pharo-project/pharo/pull/13510 - CompiledMethod simplification: remove the last user of #copyWithSource: #13507 https://github.com/pharo-project/pharo/pull/13507 ## Improve Tests - Commit-Deprecation-Rewrites #13567 https://github.com/pharo-project/pharo/pull/13567 - Make shift tests more robust #13570 https://github.com/pharo-project/pharo/pull/13570 - Small cleanings in tests #13576 https://github.com/pharo-project/pharo/pull/13576 - Ensure ThreadedFFI tests terminate all launched processes #13538 https://github.com/pharo-project/pharo/pull/13538 - Make sure class parser tests clean the system #13536 https://github.com/pharo-project/pharo/pull/13536 - Reflectivity: make tests more reliable (and fix a bug) #13544 https://github.com/pharo-project/pharo/pull/13544

1 0

This week (16/2023) on the Pharo Issue Tracker
by Marcus Denker April 21, 2023

April 21, 2023

We merged ~60 PRs this week. # Pharo 11 - Backport #13426: Make protocol of super method a priority in MethodClassifier #13432 https://github.com/pharo-project/pharo/pull/13432 - Use fixed spec version for Pharo 11 #13445 https://github.com/pharo-project/pharo/pull/13445 ## GIT/Iceberg (for Pharo 12, too) - 1279 merge menu should indicate the sense of the action #1680 https://github.com/pharo-vcs/iceberg/pull/1680 - Remove unused variable #1695 https://github.com/pharo-vcs/iceberg/pull/1695 - Fix for adding a SSH credential from UI raises an Error #1638 https://github.com/pharo-vcs/iceberg/pull/1638 - Use ED25519 keys as default instead of RSA to improve security and follow new GitHub standards #1649 https://github.com/pharo-vcs/iceberg/pull/1649 - [fix] prevent Iceberg window to crash when the registry is empty #1670 https://github.com/pharo-vcs/iceberg/pull/1670 - Fix for issue #11969 in pharo repository: Better description "packages unloaded packages #1672 https://github.com/pharo-vcs/iceberg/pull/1672 #Pharo 12 ## Enhancements - Completion menu: some love on the detail window #13473 https://github.com/pharo-project/pharo/pull/13473 - Use Pharo12 branch of Spec and NewTools #13460 https://github.com/pharo-project/pharo/pull/13460 - Fix random failure of Ombu in windows. #13448 https://github.com/pharo-project/pharo/pull/13448 - Make protocol of super method a priority in MethodClassifier #13426 https://github.com/pharo-project/pharo/pull/13426 - Cut dependency from CommandLine to UIManager #13431 https://github.com/pharo-project/pharo/pull/13431 - Fix typo introduced in merge #13446 https://github.com/pharo-project/pharo/pull/13446 - Added inspector extensions for RPackage #509 https://github.com/pharo-spec/NewTools/pull/509 ## RPackage and SystemOrganizer - Synch bug in RPackage removal #13496 https://github.com/pharo-project/pharo/pull/13496 ## Protocol and Categories - Keep pushing protocols usage #13443 https://github.com/pharo-project/pharo/pull/13443 - Add some tests on classifications of methods #13485 https://github.com/pharo-project/pharo/pull/13485 - Rename #removeMethodTag: into #removeProtocolIfEmpty: #13492 https://github.com/pharo-project/pharo/pull/13492 - Make #renameProtocolNamed:toBe: manage nils #13480 https://github.com/pharo-project/pharo/pull/13480 - Cleaning of #classify:inProtocolNamed: #13454 https://github.com/pharo-project/pharo/pull/13454 - Deprecate comment management of ClassOrganization #13464 https://github.com/pharo-project/pharo/pull/13464 - Remove ClassOrganization>>#silentlyRenameProtocolNamed:toBe: in favor of always announcing the rename #13458 https://github.com/pharo-project/pharo/pull/13458 - Improve ClassOrganization copy #13453 https://github.com/pharo-project/pharo/pull/13453 - Do not use #classComment #1376 https://github.com/pharo-spec/Spec/pull/1376 ## Compiler: Syntax Hightlight - SHRBTextStyler class>>#blueStyleTable distinguish some variables #13501 https://github.com/pharo-project/pharo/pull/13501 - Improve style for parenthesis, comments and syntax error #13491 https://github.com/pharo-project/pharo/pull/13491 - CodeSnippet: industrialize the testing of the styler #13490 https://github.com/pharo-project/pharo/pull/13490 - add SHRBStyleAttributionTest>>#testErrorStyle #13489 https://github.com/pharo-project/pharo/pull/13489 - Faulty code: improve highlight and icons #13486 https://github.com/pharo-project/pharo/pull/13486 - Fix bug in parenthesis highlight #13467 https://github.com/pharo-project/pharo/pull/13467 ## Compiler: AST - AST: starting visiting comments #13421 https://github.com/pharo-project/pharo/pull/13421 - Snippet: test more comments and fix some #13500 https://github.com/pharo-project/pharo/pull/13500 - Add support to deprecate globals #13348 https://github.com/pharo-project/pharo/pull/13348 - Compiler: expose the AST #13487 https://github.com/pharo-project/pharo/pull/13487 ## Compiler - Snippets: rename (and negate) isMethod to isScripting #13499 https://github.com/pharo-project/pharo/pull/13499 - Vocabulary: propose "script" in compiler #13301 https://github.com/pharo-project/pharo/pull/13301 - OpalCompiler: permit clients to use receiver: after context: as (a noop) #13498 https://github.com/pharo-project/pharo/pull/13498 - Introduce annotations #13449 https://github.com/pharo-project/pharo/pull/13449 - Use Compiler not #copyWithTrailerBytes #13488 https://github.com/pharo-project/pharo/pull/13488 - Directly update source pointer without creating an additional compiled method #13484 https://github.com/pharo-project/pharo/pull/13484 - remove-embeddSourceInTrailer #13481 https://github.com/pharo-project/pharo/pull/13481 - Compiler: remove #optionEmbeddSources #13479 https://github.com/pharo-project/pharo/pull/13479 - Compiler: explicit the need of requestor scope #13472 https://github.com/pharo-project/pharo/pull/13472 - Kill VariableNotDeclared #13471 https://github.com/pharo-project/pharo/pull/13471 - Factorize UndeclaredVariableErrors #13470 https://github.com/pharo-project/pharo/pull/13470 - Debug can recompile doit and uninstalled method #13469 https://github.com/pharo-project/pharo/pull/13469 - Cleanup OpalCompiler & CompilationContext #13423 https://github.com/pharo-project/pharo/pull/13423 - Compiler: simplify DoIt #13398 https://github.com/pharo-project/pharo/pull/13398 - faulty code: test runtimeSyntaxError #13422 https://github.com/pharo-project/pharo/pull/13422 - Rubric editors (thus calypso) execute doit actions in faulty mode #13450 https://github.com/pharo-project/pharo/pull/13450 - Debugger: can handle new exceptions UndeclaredVariableRead&UndeclaredVariableWrite #508 https://github.com/pharo-spec/NewTools/pull/508 - StTestDebuggerProvider class>>#compileMissingClassContextBuilder use permitUndeclared: #506 https://github.com/pharo-spec/NewTools/pull/506 - add missing SpCodeScriptingInteractionModel>>#needRequestorScope #1378 https://github.com/pharo-spec/Spec/pull/1378 - Spec2-Code: declare 'playground'-related capabilities as a compiler requestor #1377 https://github.com/pharo-spec/Spec/pull/1377 ## Cleanups - Refactoring BlockClosureTest >> testCannotReturn #13459 https://github.com/pharo-project/pharo/pull/13459 ## Trivial - use {} instead of Array with:with: #13483 https://github.com/pharo-project/pharo/pull/13483 - use nested and expression #13475 https://github.com/pharo-project/pharo/pull/13475 - use and expression instead of ifTrueifFalse #13477 https://github.com/pharo-project/pharo/pull/13477 - use and expression instead of ifTrueifFalse #13463 https://github.com/pharo-project/pharo/pull/13463 - Use {} instead of "Array with:" for some usages #13461 https://github.com/pharo-project/pharo/pull/13461

1 0

Yoshiki Ohshima - Croquet Microverse - 26 April 2023
by Giovanni Corriga April 20, 2023

April 20, 2023

For this month's online presentation, Yoshiki Ohshima will demonstrate the Croquet Microverse ( https://croquet.io/ ), which is a 3D collaborative construction environment. It is an incarnation of Smalltalk-based Croquet but instead implemented in JavaScript. Microverse allows a group of users to collaboratively create new objects in a virtual space, and describe their behaviors in the live programming manner that can be used by professional programmers. The object extension mechanism used in the Microverse is heavily influenced by past class and object extension mechanisms, many of which originated from experimentation and implementation in Smalltalk. Likewise, the architecture of the Microverse application framework draws upon other frameworks such as Morphic and AppKit. Yoshiki will explain the connections between those systems and the Microverse. Yoshiki ( https://tinlizzie.org/ohshima/ ) joined Walt Disney Imagineering R&D in 2000 as an intern while attending the graduate school of Tokyo Institute of Technology, and helped develop prototypes of Disney's theme park attractions. He also has been involved in Alan Kay's research group, and participated in the research and development effort of education programming environment Squeak Etoys and later took the leading role. Yoshiki has worked at the Viewpoints Research Institute, SAP Labs CDG, and Y Combinator Research, all of which Dr. Kay founded or helped found. He was awarded his PhD. for designing and implementing a massively parallel particle programming system from Tokyo Institute of Technology. This will be an online meeting from home. If you'd like to join us, please sign up in advance on the meeting's Meetup page ( https://www.meetup.com/ukstug/events/292570084/ ) to receive the meeting details.

1 0

Project and package structure recommendations
by Steffen MÃ¤rcker April 20, 2023

April 20, 2023

Hi, I'd like to ask for your advice or best practices regarding the package structure of a project. So far I have understood: - Iceberg can store multiple packages (project?) in a git repository - A package (or multiple?) and its dependencies is loaded via a baseline - A package can have flags (= categories?) Suppose, a project has - A core part - One or multipel optional parts, that a user may or may not want to load, too - Tests for the core - Tests for each optional part What's the recommended way to structure this in Pharo? For example, I've seen that some code in Pharo has its tests in the same package but flagged/categorized, other code has a separate package for tests. Also, can a (git) repository have multiple baselines? Sorry, if I am asking the obvious but I did not manage to find guidlines in the documentation yet. It might very well an oversight be myself. Kind regards, Steffen

3 3

This week (15/2023) on the Pharo Issue Tracker.
by Marcus Denker April 17, 2023

April 17, 2023

We merged ~ 80 PRs, closing 33 issues. # Pharo 11 Release is getting closer... - Use Microdown 2.4.0 and BeautifulComments 1.0.0 (preparing for release) #13388 https://github.com/pharo-project/pharo/pull/13388 - use fixed NewTools version #13412 https://github.com/pharo-project/pharo/pull/13412 - provide compatibility with old finalisation mechanism #13410 https://github.com/pharo-project/pharo/pull/13410 - Remove usage of old primitive 91 #13427 https://github.com/pharo-project/pharo/pull/13427 - 12885-Objectassert-fails-with-non-booleans-contradicting-its-own-comment #13251 https://github.com/pharo-project/pharo/pull/13251 - Calypso: check if node is nil before calling isCommentNode and cie #13418 https://github.com/pharo-project/pharo/pull/13418 - fix: ensure right method side (class vs instance) is chosen when looking through history https://github.com/pharo-vcs/iceberg/pulse - NewTools-Debugger-Breakpoints-Tools leaves the image in a dirty state. #504 https://github.com/pharo-spec/NewTools/pull/504 # Pharo12 Cleanups continue. The image is now ~5MB smaller due to the protocol cleanup and code removal. ## Fixes - Weekly Pharo11 sync #13429 https://github.com/pharo-project/pharo/pull/13429 - ClyJumpToTestMethodCommand>>#generateTestMethodNamed:in: use good protocol #13396 https://github.com/pharo-project/pharo/pull/13396 - Completion can extends keyword messages #13402 https://github.com/pharo-project/pharo/pull/13402 - Fix bug in syntaxt highlighting of comments #13319 https://github.com/pharo-project/pharo/pull/13319 - Refactoring rotten green test on Context #13411 https://github.com/pharo-project/pharo/pull/13411 - EpiceaBrowsers: stop catching all errors #13425 https://github.com/pharo-project/pharo/pull/13425 - Make protocol of super method a priority in MethodClassifier #13426 https://github.com/pharo-project/pharo/pull/13426 - 9778-InstructionStream-selectorToSendOrSelf-returns-GlobalVariable-bindings-too #13417 https://github.com/pharo-project/pharo/pull/13417 - Striked through symbols who are names of a deprecated global #13341 https://github.com/pharo-project/pharo/pull/13341 ## Bootrap - Remove dead code in Bootstrap #13435 https://github.com/pharo-project/pharo/pull/13435 - Use date and time as Stdio windows file name distinguisher #13299 https://github.com/pharo-project/pharo/pull/13299 - Cut dependency from Collection-Streams to UIManager #13406 https://github.com/pharo-project/pharo/pull/13406 - Fix dependies of RPackage-Core #13407 https://github.com/pharo-project/pharo/pull/13407 ## CI / Tests - Clean MCMethodDefinitionTest #13376 https://github.com/pharo-project/pharo/pull/13376 - Clean ClassRenameFixTest #13360 https://github.com/pharo-project/pharo/pull/13360 - Finish to cut 'Tests' package #13338 https://github.com/pharo-project/pharo/pull/13338 - Cleanup: Better ratio of commented classes #13329 https://github.com/pharo-project/pharo/pull/13329 - Add logs on Debugger-Oups-Tests to find error #13390 https://github.com/pharo-project/pharo/pull/13390 - FluidClassBuilder tests should clean the system #13404 https://github.com/pharo-project/pharo/pull/13404 - Remove ClassFactoryForTestCaseTest>>#testDuplicateClassWithNewName #13405 https://github.com/pharo-project/pharo/pull/13405 - CompiledCodeTest>>#testMessages should not assume order of elements #13438 https://github.com/pharo-project/pharo/pull/13438 ## Compiler: ASTCache - ASTCache: use a double weak dictionary #13379 https://github.com/pharo-project/pharo/pull/13379 - ASTCache>>#at:put: prevent TOCTOU when cleaning the cache #13408 https://github.com/pharo-project/pharo/pull/13408 - refactor ASTCache #13378 https://github.com/pharo-project/pharo/pull/13378 ## Compiler: CompiledMethods - Compiled methods: keep the source #13359 https://github.com/pharo-project/pharo/pull/13359 - Compiled method drop last property #13386 https://github.com/pharo-project/pharo/pull/13386 ## Compiler - Try to move workspace variables further (lite) #13393 https://github.com/pharo-project/pharo/pull/13393 - Compiler: remove OCASTTranslator subclasses #13352 https://github.com/pharo-project/pharo/pull/13352 - AST: fix node positions, and test them systematically #13350 https://github.com/pharo-project/pharo/pull/13350 - Faulty code importers: use new compiler API #13397 https://github.com/pharo-project/pharo/pull/13397 - OCASTSemanticAnalyzer chose the value of superOf of super-sends #13394 https://github.com/pharo-project/pharo/pull/13394 - OpalCompiler restore undeclared menu on the playground #13392 https://github.com/pharo-project/pharo/pull/13392 - implements RBBlockErrorNode>>#argumentNames #13384 https://github.com/pharo-project/pharo/pull/13384 ## ClassOrganizer/Protocol Cleanup - Introduce CompiledMethod>>#isClassified #13444 https://github.com/pharo-project/pharo/pull/13444 - Move class comment export to ClassDescription #13382 https://github.com/pharo-project/pharo/pull/13382 - Remove ClassDescription>>basicOrganization #13385 https://github.com/pharo-project/pharo/pull/13385 - Remove ClassOrganization>>hasOrganizedClass #13346 https://github.com/pharo-project/pharo/pull/13346 - Some cleanings protocol announcements and announcements #13381 https://github.com/pharo-project/pharo/pull/13381 - Rename Protocol class>>#ambiguous into #traitConflictName #13369 https://github.com/pharo-project/pharo/pull/13369 - Make protocols an array in ClassOrganization #13356 https://github.com/pharo-project/pharo/pull/13356 - Always announce creation of new protocols #13358 https://github.com/pharo-project/pharo/pull/13358 - Simplify protocol removals #13334 https://github.com/pharo-project/pharo/pull/13334 - Remove #protocolsOfSelector: and implement #protocolOfSelector: #13383 https://github.com/pharo-project/pharo/pull/13383 - Change Protocol to use an array for methodSelectors directly #13415 https://github.com/pharo-project/pharo/pull/13415 - Remove the need to give a SystemOrganizer to SystemDictionary #13314 https://github.com/pharo-project/pharo/pull/13314 ## Simple Cleanups - extract return from Float>>#asApproximateFractionAtOrder: #13400 https://github.com/pharo-project/pharo/pull/13400 - extract return from Rectangle>>#quickMerge: and use self class #13372 https://github.com/pharo-project/pharo/pull/13372 - rename truncation and roundoff to truncation and round off protocol in Rectangle #13375 https://github.com/pharo-project/pharo/pull/13375 - use and: expression instead of ifTrue:ifFalse: expression #13362 https://github.com/pharo-project/pharo/pull/13362 - extract return from Number>>#raisedTo: and add some tests #13355 https://github.com/pharo-project/pharo/pull/13355 - Cleanup-Define-subclassresponsability Boolean and Number #13416 https://github.com/pharo-project/pharo/pull/13416 - use and: expresion instead of ifTrue:ifFalse: expression #13439 https://github.com/pharo-project/pharo/pull/13439 - use and: expresion instead of ifTrue:ifFalse: expression in AST-Core #13441 https://github.com/pharo-project/pharo/pull/13441

1 0

headless mode
by Christophe TouzÃ© April 16, 2023

April 16, 2023

Bonjour, Quelqu'un pourrait-il me dire svp comment lancer une image Pharo 10 en mode headless (sous Ubuntu) ? J'ai essayÃ© "pharo --headless monImage.image" sans succÃ¨s. PrÃ©cision, j'ai Seaside dans mon image. Merci d'avance ! Hello, Could somebody tell me how to launch a Pharo 10 image in headless mode, under Ubuntu ? I have tried "pharo --headless myImage.image", without success. I have the Seaside package in my image, I don't know if it matters. Thanks !

2 1

Comparison of blocks
by Steffen MÃ¤rcker April 13, 2023

April 13, 2023

Hi! In VisualWorks, blocks can be compared with each other. In Pharo the comparison just checks for Identity. Is this on purpose? For reference, that's how BlockClosure>>= is implemented in VW: = aBlockClosure ^aBlockClosure class = self class and: [method = aBlockClosure method and: [outerContext = aBlockClosure outerContext and: [copiedValues = aBlockClosure copiedValues]]] Kind regards, Steffen

2 3

Re: [vwnc] Block evaluation with n+1 arguments
by Richard Sargent April 12, 2023

April 12, 2023

Excellent write up, Stephane! I will add that over the years, there have been many times (countless!) when developing/debugging involved a complex block and that turned out to be significant nuisance. I can elaborate on the details, but once a block gets passed around, revising it on the fly breaks debug and continue. Having a block comprise a single message send allows one to revise that method as and when needed. From: vwnc-request(a)lists.cs.illinois.edu <vwnc-request(a)lists.cs.illinois.edu> On Behalf Of stephane.ducasse(a)free.fr Sent: April 10, 2023 07:03 To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Cc: vwnc(a)lists.cs.illinois.edu Subject: Re: [vwnc] [Pharo-users] Block evaluation with n+1 arguments BTW to me when a block needs too many arguments it feels like that an object has to be born :) With an object I can just sent or not a given extra argument. Now I do not know enough your specific context but what I learned is that complex blocks are difficult to follow, manipulateâ¦ so I keep block as simple as possible and else I create little objects. This is a little lectures from a super cool forthcoming mooc https://rmod-files.lille.inria.fr/DesignCoffeeClub/ForLearningLab/7-Lang-04… <https://urldefense.com/v3/__https:/rmod-files.lille.inria.fr/DesignCoffeeCl…> On 6 Apr 2023, at 15:28, Steffen MÃ¤rcker <merkste(a)web.de <mailto:merkste@web.de> > wrote: Hi! I want to evaluate a block an argument 'arg1' and additional n arguments given in an array 'args'. The following code does the trick: block valueWithArguments: (Array with: arg1) , args. Is there a way to do this without the overhead of creating a new Array? (How) Can I add additional #value:value:[...] methods to BlockClosure that evaluate the block with n arguments directly without falling back to #valueWithArguments: ? If yes, what's the maximum? Cheers! Steffen

3 5

Fwd: [Esug-list] [IWST 2023]Call for Papers
by stephane ducasse April 12, 2023

April 12, 2023

> Begin forwarded message: > > From: Gocrdana Rakic via Esug-list <esug-list(a)lists.esug.org> > Subject: [Esug-list] [IWST 2023]Call for Papers > Date: 11 April 2023 at 19:40:35 CEST > To: esug-list(a)lists.esug.org > Reply-To: Gocrdana Rakic <goca(a)dmi.uns.ac.rs> > > Call For Papers > IWST 2023: International Workshop on Smalltalk Technologies > Lyon, France; August 29th-31st, 2023 > Goals and scope > The goals of the workshop is to create a forum around contributions and experiences in building or using technologies related to Smalltalk. While maturity of presented ideas and results is not crucial, it is expected that their presentation trigger discussion and exchange of ideas. The topics of your paper can be on all aspect of Smalltalk, theoretical as well as practical. Authors are invited to submit research articles or industrial papers. > > Important Dates > Submission deadline: May 14th, 2023 > > Notification deadline: June 11th, 2023 > > Re-submission deadline: July 1st, 2023 > > Workshop: August 29th-31st, 2023 > > Topics > We welcome contributions on all aspects, theoretical as well as practical, of Smalltalk related topics such as: > > Aspect-oriented programming, > > Design patterns, > > Experience reports, > > Frameworks, > > Implementation, new dialects or languages implemented in Smalltalk, > > Interaction with other languages, > > Meta-programming and Meta-modeling, > > Tools > > Submissions, reviews, and selection > We are looking for papers of two kinds: > > Short position papers (5 to 10 pages) describing fresh ideas and early results. > > Long research papers (more than 10 pages) with deeper description of experiments and of research results. > > Both submissions and final papers must be prepared using the CEUR ARTÂ 1-columnÂ style <https://ceur-ws.org/Vol-XXX/CEURART.zip>. > > All submissions must be sent via EasyChair submission page <https://easychair.org/conferences/?conf=iwst23>. > > Reviewing > > Submissions will be reviewed by at least 3 reviewers. Selected papers will be invited to be presented at the workshop in Lyon and published in the CEUR-WS Proceedings <https://ceur-ws.org/>. > > As the workshop form encourage bringing fresh ideas and early results to be presented and discussed, and aims for giving a chance to young community members to learn and grow, it may happen that submissions with discussion potential be conditionally accepted. In this case authors are expected to strictly follow the recommendation of the reviewers and resubmit a new version for the second fast review by the chairs in collaboration with assigned reviewers, and for making the final decision. > > Best Paper Award > > To encourage the submission of high-quality papers, the IWST organizing committee is very proud to announce a Best Paper Award for this edition of IWST. > > We thank our financial contributors who make it possible for prizes for the three best papers (estimated): 1000 USD for first place, 600 USD for second place and 400 USD for third place. > > The ranking will be decided by the program committee during the review process. The awards will be given during the ESUG conference social event. > > The Best Paper Award will take place only with a minimum of six submissions. Notice also that to be eligible, a paper must be presented at the workshop by one of the author and that the presenting author must be registered at the ESUG conference. > > Program chairs > Stephane Ducasse, Inria Lille, France (chair), > Gordana Rakic, University of Novi Sad, Serbia (chair) > Program committee > > Nour Agouf, Inria Lille, France, > Vincent Blondeau, Lifeware, Switzerland, > Cedrick Beler, Ecole Nationale d Ingenieurs de Tarbes, Hautes-Pyrenees, France, > Nicolas Cardozo, Universidad de los Andes, Bogota, Colombia, > Celine Deknop, Universite catholique de Louvain (UCL), Belgium, > Michele Lanza, Software Institute, Universita della Svizzera italiana, Lugano, Switzerland, > Eric Lepors, Thales DMS, France, > Dave Mason, Ryerson University, Toronto, Canada, > Kim Mens, Universite catholique de Louvain (UCL), Belgium, > Ana-Maria Oprescu, University of Amsterdam, Neatherlands, > Jean Privat, University of Quebec in Montreal, Canada, > Pooja Rani, University of Bern, Switzerland, > Larisa Safina, Inria Lille, France, > Joao Saraiva, University of Minho, Portugal, > BenoÃ®t Verhaeghe, Berger-Levrault, Lyon, France, > Oleksandr Zaytsev, Cirad, UMR SENS, France > _______________________________________________ > Esug-list mailing list -- esug-list(a)lists.esug.org <mailto:esug-list@lists.esug.org> > To unsubscribe send an email to esug-list-leave(a)lists.esug.org <mailto:esug-list-leave@lists.esug.org>

1 0

Re: [vwnc] Block evaluation with n+1 arguments
by Steffen MÃ¤rcker April 11, 2023

April 11, 2023

Hi Stephane, thanks for linking the upcoming lesson. I'll have a look. :-D Best, Steffen stephane.ducasse(a)free.fr schrieb am Montag, 10. April 2023 16:03:16 (+02:00): BTW to me when a block needs too many arguments it feels like that an object has to be born :) With an object I can just sent or not a given extra argument. Now I do not know enough your specific context but what I learned is that complex blocks are difficult to follow, manipulateâ¦ so I keep block as simple as possible and else I create little objects. This is a little lectures from a super cool forthcoming mooc https://rmod-files.lille.inria.fr/DesignCoffeeClub/ForLearningLab/7-Lang-04… On 6 Apr 2023, at 15:28, Steffen MÃ¤rcker <merkste(a)web.de> wrote: Hi! I want to evaluate a block an argument 'arg1' and additional n arguments given in an array 'args'. The following code does the trick: block valueWithArguments: (Array with: arg1) , args. Is there a way to do this without the overhead of creating a new Array? (How) Can I add additional #value:value:[...] methods to BlockClosure that evaluate the block with n arguments directly without falling back to #valueWithArguments: ? If yes, what's the maximum? Cheers! Steffen -- Gesendet mit Vivaldi Mail. Laden Sie Vivaldi kostenlos von vivaldi.com herunter.

1 0

Block evaluation with n+1 arguments
by Steffen MÃ¤rcker April 11, 2023

April 11, 2023

Hi! I want to evaluate a block an argument 'arg1' and additional n arguments given in an array 'args'. The following code does the trick: block valueWithArguments: (Array with: arg1) , args. Is there a way to do this without the overhead of creating a new Array? (How) Can I add additional #value:value:[...] methods to BlockClosure that evaluate the block with n arguments directly without falling back to #valueWithArguments: ? If yes, what's the maximum? Cheers! Steffen

4 4

English subtitles for Adele Goldberg
by Richard Kenneth Eng April 7, 2023

April 7, 2023

https://youtu.be/8uGV9hcIN_Y I've added an English subtitle track (NOT auto-generated) to correct for the two minutes of audio difficulty in Adele Goldberg's keynote talk. The auto-generated subtitle track is incomplete during these two minutes (5:26).

1 0

This week (13/2023) on the Pharo Issue Tracker
by Marcus Denker April 7, 2023

April 7, 2023

#This week (13/2023) on the Pharo Issue Tracker. We merged around 100 Pull Reuests this week (Pharo11 and Pharo12) To see the state of not yet merged PRs easier, we added a GitHub Board https://github.com/orgs/pharo-project/projects/34 To see what is happing in Pharo11 and Pharo12, we are staring to check if Kanban style boards can help Pharo11: https://github.com/orgs/pharo-project/projects/35 Pharo12: https://github.com/orgs/pharo-project/projects/38 #Pharo 11 ## Epemerons - Move weak dictionaries to new finalization #13212 https://github.com/pharo-project/pharo/pull/13212 ## Fixes - Update find sdl2 #13031 https://github.com/pharo-project/pharo/pull/13031 - Playground not able to evaluate simple #timesRepeat: #13321 https://github.com/pharo-project/pharo/pull/13321 - Handle Cmd/Ctrl + right arrow during completion. #13217 https://github.com/pharo-project/pharo/pull/13217 - Added new text selection for pharo #13231 https://github.com/pharo-project/pharo/pull/13231 - Fast table should not manage keydown as keystroke #13214 https://github.com/pharo-project/pharo/pull/13214 - Socket error handling can get in a loop #13228 https://github.com/pharo-project/pharo/pull/13228 - SDL2 on MacOS required to postpone focus #12946 https://github.com/pharo-project/pharo/pull/12946 - KeyboardKey class>>#initializeKeyFromCharacterCompatibilityTable maps 3 characters incorrectly #13211 https://github.com/pharo-project/pharo/pull/13211 - Fix selection of multiword #13218 https://github.com/pharo-project/pharo/pull/13218 - Fix the UI of the spotter by outlining the input field. Fix pharo/#10993 #421 https://github.com/pharo-spec/NewTools/pull/421 - Fix DNU trimBoth on non-strings #1372 https://github.com/pharo-spec/Spec/pull/1372 ## Cleanups - StFilterFuzzy>>#applyFilterWithQuery send missing #takeFirst: #13242 https://github.com/pharo-project/pharo/pull/13242 - 12165-ReAbstractRule-mentions-missing-help-in-class-comment #13252 https://github.com/pharo-project/pharo/pull/13252 - Replace allProtocols by protocols #1373 https://github.com/pharo-spec/Spec/pull/1373 - SpCodePresenter>>#evaluate source code is string #1371 https://github.com/pharo-spec/Spec/pull/1371 ## Speed - do not compute message sends dependencies in browser dependencies tool #13268 https://github.com/pharo-project/pharo/pull/13268 #Pharo12 - Weekly P11 sync in P12 #13253 https://github.com/pharo-project/pharo/pull/13253 ## Fixes - 4969-Epicea-Reverting-a-class-remove-looses-class-comment #13332 https://github.com/pharo-project/pharo/pull/13332 - hotfix ClassTest>>#testCommentSourcePointer #13281 https://github.com/pharo-project/pharo/pull/13281 - Fix #13246 class comments can get lost when commiting code #13276 https://github.com/pharo-project/pharo/pull/13276 - Finder: Ignoring combinations selector for collections #13226 https://github.com/pharo-project/pharo/pull/13226 ## Compiler - Faulty Code: compiler honor failBlock #13261 https://github.com/pharo-project/pharo/pull/13261 - Faulty code: improve error block node #13264 https://github.com/pharo-project/pharo/pull/13264 - RBNotice: add isSyntaxError and make it easier to sort them #13344 https://github.com/pharo-project/pharo/pull/13344 - Faulty code: forbid read of undeclared variables #13238 https://github.com/pharo-project/pharo/pull/13238 - Faulty code: don't permit undeclared by default #13286 https://github.com/pharo-project/pharo/pull/13286 - Compiler simplify OCSemanticScope #13303 https://github.com/pharo-project/pharo/pull/13303 - Faulty parser: better faulty literal (byte) arrays #13300 https://github.com/pharo-project/pharo/pull/13300 - Some compiler cleanup #13302 https://github.com/pharo-project/pharo/pull/13302 - Faulty code: make undeclared write resumable with the right value #13297 https://github.com/pharo-project/pharo/pull/13297 - Faulty code: add permitUndeclared #13280 https://github.com/pharo-project/pharo/pull/13280 - Faulty code: move code reparator to RBNotice #13277 https://github.com/pharo-project/pharo/pull/13277 - Snippets: split badExpressions into 3 methods #13263 https://github.com/pharo-project/pharo/pull/13263 - Faulty code: various undeclared cleanups #13248 https://github.com/pharo-project/pharo/pull/13248 - Faulty code: inspect notice #13243 https://github.com/pharo-project/pharo/pull/13243 - Cleanup some compiler clients #13235 https://github.com/pharo-project/pharo/pull/13235 - Faulty code: forbid write to undeclared variables #13201 https://github.com/pharo-project/pharo/pull/13201 - Faulty code snippet: test evaluation #13223 https://github.com/pharo-project/pharo/pull/13223 - Compiler: replace parseForRequestor by checkNotice #13222 https://github.com/pharo-project/pharo/pull/13222 ## SystemOrganizer Cleanup - Remove the need to give a SystemOrganizer to SystemDictionary #13314 https://github.com/pharo-project/pharo/pull/13314 - Remove SystemOrganisation global #13306 https://github.com/pharo-project/pharo/pull/13306 - Remove references to SystemOrganization #13271 https://github.com/pharo-project/pharo/pull/13271 - Remove references to SystemOrganizer #13259 https://github.com/pharo-project/pharo/pull/13259 - Make RPackageOrganizer polymorphic with SystemOrganizer #13258 https://github.com/pharo-project/pharo/pull/13258 - RPackageOrganizer should not call system organizer global but keep a reference #13245 https://github.com/pharo-project/pharo/pull/13245 - Rename SystemOrganizer "elements" into "Behavior" #13206 https://github.com/pharo-project/pharo/pull/13206 ##Protocol vs Category - Protocol: Rename "category" into protocol in rules #13203 https://github.com/pharo-project/pharo/pull/13203 - Rename some "category" into protocol in code export #13190 https://github.com/pharo-project/pharo/pull/13190 - Remove usage of Protocol>>#canBeRemoved #13311 https://github.com/pharo-project/pharo/pull/13311 - Remove nullProtocolName #13333 https://github.com/pharo-project/pharo/pull/13333 - Use Protocol>>#unclassified instead of #defaultName #13331 https://github.com/pharo-project/pharo/pull/13331 - Remove class AllProtocol #13289 https://github.com/pharo-project/pharo/pull/13289 - Remove ClassOrganization>>allProtocol #13275 https://github.com/pharo-project/pharo/pull/13275 - hotfix: add missing return in ClassOrganization>>#ensureProtocol: #13278 https://github.com/pharo-project/pharo/pull/13278 - Protocols: Allow to compile a method with a real protocol #13247 https://github.com/pharo-project/pharo/pull/13247 - Rename #methodsInProtocolNamed: into #methodSelectorsInProtocol: #13257 https://github.com/pharo-project/pharo/pull/13257 - Remove ClassOrganization>>allProtocolNames #13256 https://github.com/pharo-project/pharo/pull/13256 - Inline protocol organizer #13187 https://github.com/pharo-project/pharo/pull/13187 - ProtocolOrganizer: Inline more behavior into ClassOrganization #13234 https://github.com/pharo-project/pharo/pull/13234 ## Refactoring Engine - [Refactoring] push down method in some classes driver #13175 https://github.com/pharo-project/pharo/pull/13175 - Refactor: insert new class refactoring #13216 https://github.com/pharo-project/pharo/pull/13216 - 13215-RB-RBRefactoringChangeTesttestPerformChangeMetaclass #13221 https://github.com/pharo-project/pharo/pull/13221 ## CI / Bootstrap - Skip windows broken tests #13308 https://github.com/pharo-project/pharo/pull/13308 - Remove PBOldExtendedBootstrap #13290 https://github.com/pharo-project/pharo/pull/13290 - Bootstrap: allow to authetificate github requests during the bootstrap #13279 https://github.com/pharo-project/pharo/pull/13279 - Declare global variables Display, World and ActiveWorld #13236 https://github.com/pharo-project/pharo/pull/13236 ## Small Cleanups - unskip #testPerformChangeClass #13213 https://github.com/pharo-project/pharo/pull/13213 - Remove some unecessary not from the kernel #13197 https://github.com/pharo-project/pharo/pull/13197 - Faulty code: fix syntax error on empty closers #13262 https://github.com/pharo-project/pharo/pull/13262 - SettingBrowser class>>viewAllSettings has no senders and is broken #13288 https://github.com/pharo-project/pharo/pull/13288 - Restore comment of MockForCompilation #13293 https://github.com/pharo-project/pharo/pull/13293 - remove Deprecated11 #13291 https://github.com/pharo-project/pharo/pull/13291 - Fix some deprecated sends #13287 https://github.com/pharo-project/pharo/pull/13287 - Remove dependency of Collections-Abstract/Sequenceable over Random-Core #13294 https://github.com/pharo-project/pharo/pull/13294 - Extract SourceFileArrayTest to System-Sources-Tests #13307 https://github.com/pharo-project/pharo/pull/13307 - Do not disable system announcements during rpackage tests #13298 https://github.com/pharo-project/pharo/pull/13298 - Clean ChangeSetClassChangesTest #13317 https://github.com/pharo-project/pharo/pull/13317 - Remove deprecated modelwants steps in in p12 #13325 https://github.com/pharo-project/pharo/pull/13325 - Finish to cut 'Tests' package #13338 https://github.com/pharo-project/pharo/pull/13338 - Cleanup small cleanups in baseline of base libraries package #13327 https://github.com/pharo-project/pharo/pull/13327 - Deprecate OneShotArmed / doOnlyOnce: mechanism in ProtoObject (P12) #13320 https://github.com/pharo-project/pharo/pull/13320 - Cleanup: Move as "Arrayed" tagged test classes from generic "Collections-Tests" package to specific "Collections-Native-Tests" package #13336 https://github.com/pharo-project/pharo/pull/13336 - Fix and load SystemCommands tests #13340 https://github.com/pharo-project/pharo/pull/13340 - Remove general help package from the repo #13339 https://github.com/pharo-project/pharo/pull/13339 - extract return and use and: expression. add some tests #13343 https://github.com/pharo-project/pharo/pull/13343 - deprecate classesThatImplementAllOf: method. fix: #12832 #13266 https://github.com/pharo-project/pharo/pull/13266 - PositionableStream>>nextChunkText is dead code #13232 https://github.com/pharo-project/pharo/pull/13232 - This commit simplifies some conditionals using isEmpty followed by an #ifTrue:[ifFalse:] #13200 https://github.com/pharo-project/pharo/pull/13200 - Move runarray to collections support #13140 https://github.com/pharo-project/pharo/pull/13140

1 0

A blog on graph algorithms library of Pharo
by DK Goutham April 6, 2023

April 6, 2023

Dear Pharo Users, Here's a blog on *pharo-ai/graph-algorithms* library. This acts as a primer for people new to this library and discusses the flow and architecture of the library. The motive of this blog is to introduce people to the amazing graph library of Pharo and give them enough confidence to contribute to this library. Link: https://medium.com/@dkgoutham1806/graph-algorithms-in-pharo-7d12af0be060 Happy reading! Thank you, Goutham

4 3

Pharo 11 release soon: Please check Issue Tracker
by Marcus Denker April 5, 2023

April 5, 2023

Hi, Pharo11 us now frozen for a while, it seems we are on a good way to release soon. This is always a good time to clean up the issue tracker. Please check especially the issues you opend https://github.com/pharo-project/pharo/issues Github often fails to close the isssue even though it is correctly set as to be closed in the PR. And often bugs are fixed due to a duplicate issue tracker entry or as part of other work. As we do not timeout issues anymore, we rely on everyone to help to keep this in a somewhat sane stateâ¦ Marcus

1 0

This week (13/2023) on the Pharo Issue Tracker
by Marcus Denker April 3, 2023

April 3, 2023

We again merged ~60 PRs. Pharo11 got some bugfixes and last improvements. In Pharo12, we continue the compiler refactoring and the cleanup of ClassOrganizer. Pharo11 ======= Last Improvements ================= - Add a way to know the real processor architecture #13124 https://github.com/pharo-project/pharo/pull/13124 - remove end line characters in returned value of processorArchitecture #13155 https://github.com/pharo-project/pharo/pull/13155 - Removing unused instance variable topContext in DebugContext #13179 https://github.com/pharo-project/pharo/pull/13179 - Add inspector extensions for Chronology #499 https://github.com/pharo-spec/NewTools/pull/499 - More inspector extensions #497 https://github.com/pharo-spec/NewTools/pull/497 Fixes ===== - 13181-DeprecationPerformedNotification-Automatic-deprecation-code-rewrite #13182 https://github.com/pharo-project/pharo/pull/13182 - implement #selectedClassOrMetaClass in MCTool to return nil #13167 https://github.com/pharo-project/pharo/pull/13167 - 13141-timesRepeat-does-not-work-on-nested-loops #13154 https://github.com/pharo-project/pharo/pull/13154 - 13122 rbparser cutting tokens in stepBar [Pharo11] #13129 https://github.com/pharo-project/pharo/pull/13129 - fixing the code update bug after compiling a missing method with the unfiltered stack #491 https://github.com/pharo-spec/NewTools/pull/491 - Categorizing uncategorized classes in new tools debugger tests #500 https://github.com/pharo-spec/NewTools/pull/500 - SpCodeInteractionModel>>#notify: Avoid crashing #1363 https://github.com/pharo-spec/Spec/pull/1363 - SpDropListExampleTest does not opens Playgorunds anymore #1359 https://github.com/pharo-spec/Spec/pull/1359 Pharo12 ======= Speed ===== - speedup-testNoShadowedVariablesInMethods #13170 https://github.com/pharo-project/pharo/pull/13170 - Speed up #assertCollection:hasSameElements: in case they are equals. #13144 https://github.com/pharo-project/pharo/pull/13144 ClassOrganizer Cleanup ====================== - Inline extensions of protocol organizer #13194 https://github.com/pharo-project/pharo/pull/13194 - ChangeRecord: rename category into protocol #13188 https://github.com/pharo-project/pharo/pull/13188 - Inline some protocol organizer behavior #13191 https://github.com/pharo-project/pharo/pull/13191 - remove commentSourcePointer from ClassOrganization #13176 https://github.com/pharo-project/pharo/pull/13176 - Set-CommentSourcepointer-ClassDescription #13171 https://github.com/pharo-project/pharo/pull/13171 - Update behaviour of #protocolNamed: #13173 https://github.com/pharo-project/pharo/pull/13173 - Simplify and deprecate ClassDescription>>allProtocolsUpTo: #13160 https://github.com/pharo-project/pharo/pull/13160 - ProtocolOrganizer cleanings #13169 https://github.com/pharo-project/pharo/pull/13169 - ClassComments-Via-Class #13168 https://github.com/pharo-project/pharo/pull/13168 - Rename #nullCategory into #nullProtocolName #13157 https://github.com/pharo-project/pharo/pull/13157 Compiler Cleanup ================ - Remove RBInstanceVariableNode crufts #13199 https://github.com/pharo-project/pharo/pull/13199 - Faulty code: Make OCUndeclaredVariableWarning a little less special #13186 https://github.com/pharo-project/pharo/pull/13186 - Compiler source code is String #13184 https://github.com/pharo-project/pharo/pull/13184 - Factorize recompile:from: #13180 https://github.com/pharo-project/pharo/pull/13180 - OpalCompiler gain install #13152 https://github.com/pharo-project/pharo/pull/13152 - Faulty code: improve code error descriptions #13174 https://github.com/pharo-project/pharo/pull/13174 - Faulty code: make OCASTSemanticAnalyzer (almost) faulty only #13165 https://github.com/pharo-project/pharo/pull/13165 - CodeImport - stop requestor madness #13162 https://github.com/pharo-project/pharo/pull/13162 - Faulty code - signal mainly CodeError #13164 https://github.com/pharo-project/pharo/pull/13164 - Faulty code improve scanner on error tokens #13135 https://github.com/pharo-project/pharo/pull/13135 - Faulty code: introduce invalid variables #13148 https://github.com/pharo-project/pharo/pull/13148 - CodeSnippet: can update itself thaks to metaprogramming and code transformation #13127 https://github.com/pharo-project/pharo/pull/13127 - Faulty code: cleanup CodeError #13163 https://github.com/pharo-project/pharo/pull/13163 - Faulty code: improve shadowing policy and implementation #13132 https://github.com/pharo-project/pharo/pull/13132 - Faulty code: improve error on unexpected block parameter #13133 https://github.com/pharo-project/pharo/pull/13133 - 13122 rbparser cutting tokens in stepBar [Pharo12] #13130 https://github.com/pharo-project/pharo/pull/13130 Refactoring Engine ================== - Refactorings clean up #13131 https://github.com/pharo-project/pharo/pull/13131 - Refactoring push down method command to use driver #13099 https://github.com/pharo-project/pharo/pull/13099 - Remove duplicated mocking #13151 https://github.com/pharo-project/pharo/pull/13151 Improvements ============= - Improve announcements printing #13178 https://github.com/pharo-project/pharo/pull/13178 - Clean copying methods of ClassDescription #13159 https://github.com/pharo-project/pharo/pull/13159 - More explicit error message for slot usage in bootstrap #13145 https://github.com/pharo-project/pharo/pull/13145 - move bootstrap/src into main src #13016 https://github.com/pharo-project/pharo/pull/13016 Cleanups ======== - OSPlatformTest should be in System-Platforms-Tests #13192 https://github.com/pharo-project/pharo/pull/13192 - Factorize announcement subscribers #13185 https://github.com/pharo-project/pharo/pull/13185 - Synch with p11 #13147 https://github.com/pharo-project/pharo/pull/13147

2 1