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

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