- Pharo-users - lists.pharo.org

ESUG Presentation deadline is 1st of JUNE!
by stephane ducasse May 1, 2023

May 1, 2023

Hello people do not wait the last moment, it will help the organizers. ESUG 2023 Call for Presentations 28.8.2023 to 01.9.2023 Lyon France https://esug.github.io <https://esug.github.io/> https://esug.github.io/2023-Conference/conf2023.html Deadline for submission is 1 st of June! ESUG is the premium and fun conference around smalltalk technologies. You can support the ESUG conference in many different ways: - Sponsor the conference. New sponsoring packages are described at http://www.esug.org/supportesug/becomeasponsor/ - Submit a talk, a software or a paper to one of the events. See below. - Attend the conference. We'd like to beat the previous record of attendance (180 people at Koln 2019)! - Students can get free registration and hosting if they enroll into the the Student Volunteers program. See below. ## Developers Forum: International Smalltalk Developers Conference We are looking for YOUR experience on using Smalltalk. You will have 30 min for presentations and 45 min for hands-on tutorials. The list of topics for the normal talks and tutorials includes, but is not limited to the following: - XP practices, Development tools, Experience reports - Model driven development, Web development, Team management - Meta-Modeling, Security, New libraries & frameworks - Educational material, Embedded systems and robotics - SOA and Web services, Interaction with other programming languages - Teaching Pearls and Show us Your Business New this year!!! We added two types of sessions in addition to the regular talks and show us your projects sessions. Show your business 10 min session (Get prepared!!) Teaching pearls : we want some session on how to teach some design aspects. We want your tip and tricks to teach Smalltalk or OOP. We expect to have several 10 to 15 min sessions aggregated. ### How to submit? Make a Pull Request here https://github.com/ESUG/esug.github.io/tree/source/2023-Conference/talks [Or but only if you are not connected to the worldâ¦ send an email to stephane.ducasse(a)inria.fr <mailto:stephane.ducasse@inria.fr>] Title: [ESUG 2023] Please follow the template below the email will be automatically processed! Name: Email: Abstract: Bio: 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

ESUG 2023 student volunteer program!
by stephane ducasse May 1, 2023

May 1, 2023

Please distribute to the community and more Call for Student Volunteers Student volunteers help keep the conference running smoothly; in return, they have free accommodations, while still having most of the time to enjoy the conference. Pay attention: the places are limited so do not wait till the last minute to apply. Conference details: Send an email to stephane.ducasse at inria.fr <http://inria.fr/> and Oleksandr Zaitsev <olk.zaytsev(a)gmail.com <mailto:olk.zaytsev@gmail.com>> with: Title: [ESUG 2023 Student] name, gender, university/school, country, email address short description of you and why you are interested in participating For which period is accommodation covered? Accommodation is covered from Sunday 27.8.2023 to 01.9.2023 (including nights from Sunday to Monday and from Thursday to Friday). Students will be hosted in student rooms. ESUG additionally covers for the lunches during the week and one dinner. Duties include handling registration as people arrive at the conference, filling coffee machines, collecting presentation slides for ESUG right after the presentation is given, being present at an information desk to answer questions, and generally being helpful. Student volunteering makes the conference better, takes a fairly small amount of time and doesn't significantly interfere with enjoying and learning from the conference. Please Note, this role requires discipline and constant attention to all attendees. Information about hotel Student Volunteer rooms are booked at (to be announced). If you are student volunteer, do not book yourself, we have arranged the booking already! _______________________________________________

1 0

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

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