- Pharo-dev - lists.pharo.org

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

Feb. 17, 2023

We merged 42 PRs and closed 66 issues Fixes ===== - Unnecessary characters rule should be an information and not a warning #12764 https://github.com/pharo-project/pharo/pull/12764 - FIx #wantsSteps deprecated calls #12782 https://github.com/pharo-project/pharo/pull/12782 - Removing the TStDebuggerExtension trait from the dummy debugger presenter #463 https://github.com/pharo-spec/NewTools/pull/463 Tests ===== - add some Duration tests #12777 https://github.com/pharo-project/pharo/pull/12777 - 11368-Failing-on-CI-random-CoNarrowHistoryFetcherTesttestNarrowingReturnsSameElementsThatCallingDirectly #12768 https://github.com/pharo-project/pharo/pull/12768 - categorization tests should print culprints if any #12780 https://github.com/pharo-project/pharo/pull/12780 Documentation ============= - Missing class comment: BaselineOfBeacon #12640 https://github.com/pharo-project/pharo/pull/12640 - Missing class comment BaselineOfClap and lint issue #12642 https://github.com/pharo-project/pharo/pull/12642 Cleanup ======= - Adjust #initialize categorization cases #12638 https://github.com/pharo-project/pharo/pull/12638 - Remove BlueInk packages #12612 https://github.com/pharo-project/pharo/pull/12612 - use String>>streamContens: and assert:equals: #12786 https://github.com/pharo-project/pharo/pull/12786 - 29 of the kind Cleanup: Condense SUnit packages #12630 https://github.com/pharo-project/pharo/pull/12630

1 0

PhEP: Underscores in Numeric Literals
by Privat, Jean Feb. 14, 2023

Feb. 14, 2023

This PhEP describes the extension of Pharo numeric literals to accepts (and ignore) underscore characters (`_` ASCII 95). Many languages (including Python https://peps.python.org/pep-0515/ , Java https://docs.oracle.com/javase/7/docs/technotes/guides/language/underscores… or Ruby) accept some forms of numeric literal that ignore _. The idea is to permit long literals that are still readable, eg. `1_000_000_000` is easier for a human than `100000000` especially since in the previous literal a zero is missing (I'm a tricky deceitful fellow). The details of the proposal are in the PR: https://github.com/pharo-project/pheps/pull/16 -- Jean Privat

4 3

ESUG 2023 Call for participation
by stephane ducasse Feb. 11, 2023

Feb. 11, 2023

ESUG 2023 Call for Presentations 28.8.2023 to 01.9.2023 Lyon France https://esug.github.io https://esug.github.io/2023-Conference/conf2023.html 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] Title: [ESUG 2023] Please follow the template below the email will be automatically processed! Name: Email: Abstract: Bio: ## 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 and Oleksandr Zaitsev <olk.zaytsev(a)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

This week (6/2023) on the Pharo Issue Tracker
by Marcus Denker Feb. 10, 2023

Feb. 10, 2023

We merged 60 PRs, closed 76 issues Features ======== - Add #ensureOpen to Trascript to not open multiple transcripts while sâ¦ #12588 https://github.com/pharo-project/pharo/pull/12588 - Improve ReImplementedNotSentRule to ignore self calls + add tests #12585 https://github.com/pharo-project/pharo/pull/12585 - Adding an accessor for the root nodes of the settings browser #12521 https://github.com/pharo-project/pharo/pull/12521 Speed ===== - Disable setting formatIncompleteIdentifiers by default #12475 https://github.com/pharo-project/pharo/pull/12475 Fixes ===== - 12418-MCMethodDefinition-asSymbol-error-when-catString-isNil-loading-BaselineOf #12589 https://github.com/pharo-project/pharo/pull/12589 - Improve robustess of DependencyAnalyzer #12581 https://github.com/pharo-project/pharo/pull/12581 - 12518-ImageCleaner-shareLiterals-shouldnt-consider-Strings-and-Symbols-the-same #12529 https://github.com/pharo-project/pharo/pull/12529 - fix #12573: Error due to deprecated wantsStepsIn: on "senders of" #12574 https://github.com/pharo-project/pharo/pull/12574 - Fix DrTest UI when plugin selection change #12468 https://github.com/pharo-project/pharo/pull/12468 - Fix #12408, remove containerTabs from the notebook and not from the owner submorphs #12464 https://github.com/pharo-project/pharo/pull/12464 - Extract set up now classify setUp in #running #12512 https://github.com/pharo-project/pharo/pull/12512 Compiler ======== - Compiler: enable optionInlineTimesRepeat and optionInlineRepeat by default #12604 https://github.com/pharo-project/pharo/pull/12604 - add a "parse plugin" mechanism to OpalCompiler #12429 https://github.com/pharo-project/pharo/pull/12429 Refactoring Engine ================== - FindAndReplaceRefactoring is a transformation #12495 https://github.com/pharo-project/pharo/pull/12495 - Cleanup unused refactorings #12531 https://github.com/pharo-project/pharo/pull/12531 Tools ===== - Use the list of VM parameters from the pharo image. #448 https://github.com/pharo-spec/NewTools/pull/448 - Improved debugger symbol diff in failing tests #462 https://github.com/pharo-spec/NewTools/pull/462 - fix test of Sindarin when timesRepeat: is optimized #461 https://github.com/pharo-spec/NewTools/pull/461 - Integrating JumpToCaret command from Sindarin to the advanced step menu in the debugger toolbar #428 https://github.com/pharo-spec/NewTools/pull/428 - 377-Uncategorised-method-in-StDebuggerCommandtransform #433 https://github.com/pharo-spec/NewTools/pull/433 - Double click on the debugger stack browse the method #460 https://github.com/pharo-spec/NewTools/pull/460 - Spotter Insert selection setting #454 https://github.com/pharo-spec/NewTools/pull/454 - Fix spotter bug while clicking a header #455 https://github.com/pharo-spec/NewTools/pull/455 - Simplifying code in settings commands #459 https://github.com/pharo-spec/NewTools/pull/459 - Debugger-Actions are legacy code from the previous debugger. #458 https://github.com/pharo-spec/NewTools/pull/458 CI related ========== - fix transcript output testIgnoreDeprecationWarnings #12603 https://github.com/pharo-project/pharo/pull/12603 - skip the test testNewProcessTaskRunnerRunsInNewProcessEveryTime on the CI #12530 https://github.com/pharo-project/pharo/pull/12530 Documentation ============= - 12498-Documentation-fix-for-Dictionary--keysAndValuesDo #12580 https://github.com/pharo-project/pharo/pull/12580 - add block ast node stats code as class comment #12606 https://github.com/pharo-project/pharo/pull/12606 - comment to explicit class size initialize behavior #12463 https://github.com/pharo-project/pharo/pull/12463 Cleanup ======= - Remove debugger actions #12515 https://github.com/pharo-project/pharo/pull/12515 - 5500-Ban-rule-on-testReadComputedSlotCompiled #12523 https://github.com/pharo-project/pharo/pull/12523 - 11142-TestRunner--classNamesNotUnderTest-is-sent-but-not-implemented #12525 https://github.com/pharo-project/pharo/pull/12525 - Remove SourceCodeFont setting that has no effect #12522 https://github.com/pharo-project/pharo/pull/12522 - Stepping mecanisme should be used by model and morph. But it is curreâ¦ #12510 https://github.com/pharo-project/pharo/pull/12510 - 12080-Dead-code-viewContentsInWorkspace #12524 https://github.com/pharo-project/pharo/pull/12524 - remove dead code with wikiStyleHelp: pragma #12582 https://github.com/pharo-project/pharo/pull/12582 - Add <ignoreForCoverage> to methods generated by the manifest builder #12583 https://github.com/pharo-project/pharo/pull/12583 - Rename PlatformIndependentEnvironment into NullOSEnvironment #12520 https://github.com/pharo-project/pharo/pull/12520 - extract return from ifTrueifFalse expression #12561 https://github.com/pharo-project/pharo/pull/12561 - 22 x cleanups of the kind Cleanup: Condense Reflectivity packages #12601 https://github.com/pharo-project/pharo/pull/12601 - Remove use of deprecated classes #1351 https://github.com/pharo-spec/Spec/pull/1351 - Remove use of deprecated classes #1351 https://github.com/pharo-spec/Spec/pull/1351

1 0

[Help needed] Please check your old issue tracker entries!
by Marcus Denker Feb. 8, 2023

Feb. 8, 2023

Hi, We waste a lot of time with - turning prose descriptions of fixes into code - trying to fix bugs that are already fixed - trying to understand issues that have just not enough infos One thing that would help: If everyone would regularly check their old issue tracker entries. I think what happens is that when bugs get fixed, everyone assumes that of course the issue gets closed, too But that is not happening due to multiple reasons: - Duplicated entries. The *other one* was closed, but not yours - Fixes happening e.g. due to code rewrites The easiest is to use the created_by feature: https://github.com/pharo-project/pharo/issues/created_by/MarcusDenker - check if the issue is still relevant - has it been fixed? - is the description understandable? - if it has a suggestion of a fix, do a PR. (it is much harder to turn prose into code than you would think!) Marcus

1 0

This week (4/2023) on the Pharo Issue Tracker
by Marcus Denker Feb. 3, 2023

Feb. 3, 2023

We merged 39 PRs and closed 77 issues. If you want to help, there are 29 PRs: https://github.com/pharo-project/pharo/pulls Features ======== - Introduce new string comparison primitive #12504 https://github.com/pharo-project/pharo/pull/12504 - Profiler: simplify world menu #12501 https://github.com/pharo-project/pharo/pull/12501 - ReSentNotImplementedRule: take Pragma into account #12295 https://github.com/pharo-project/pharo/pull/12295 - 12431 Better user experience for final dot critique and cleaning #12455 https://github.com/pharo-project/pharo/pull/12455 - Fix #3067: Float>>#closeTo: does not use Float>>epsilon as default precision #12451 https://github.com/pharo-project/pharo/pull/12451 - Fix #3332: New package committed by Iceberg is always dirty #12453 https://github.com/pharo-project/pharo/pull/12453 - Fix #12287 adding group model to parent window #12446 https://github.com/pharo-project/pharo/pull/12446 - Improving the ChangesBrowser presenter #12438 https://github.com/pharo-project/pharo/pull/12438 - [improvement] better default hierarchy display #11053 https://github.com/pharo-project/pharo/pull/11053 - Complete symbols #11918 https://github.com/pharo-project/pharo/pull/11918 - convert numpad keys with NumLock turned off #12258 https://github.com/pharo-project/pharo/pull/12258 Speed ===== - 12128-Poor-performance-with-large-WriteStreams #12205 https://github.com/pharo-project/pharo/pull/12205 Fixes ===== - Honor theme changed events #12473 https://github.com/pharo-project/pharo/pull/12473 - fix: DeprecateClassCommand DNU #12494 https://github.com/pharo-project/pharo/pull/12494 - Fix conflict between formatter and rules: spaces before new lines #12448 https://github.com/pharo-project/pharo/pull/12448 - 11968-Clean-Blocks-Jobowner-assumes-valid-outerContext #12055 https://github.com/pharo-project/pharo/pull/12055 - Re-introduce list morph shortcuts using keydown #12386 https://github.com/pharo-project/pharo/pull/12386 CI related ========== - 12508-CI-failing-test-RBReplaceSubtreeTransformationTesttestTransformOneOfManyStatements #12509 https://github.com/pharo-project/pharo/pull/12509 - 12440-CI-failing-test-testClassSideInitializeMethodNeedsToBeInClassInitializationProtocol #12442 https://github.com/pharo-project/pharo/pull/12442 - Fix dependencies tests #12449 https://github.com/pharo-project/pharo/pull/12449 Cleanups ======== - Fix #3172: parseTreeFor: asymbol should be renamed parseTreeOfMethodNamed: aSymbol #3172 #12452 https://github.com/pharo-project/pharo/pull/12452 - Removed duplicated line form RubSmalltalkEditor>>tallySelection #12437 https://github.com/pharo-project/pharo/pull/12437 - Extracting the logic of screenshot and selection #11254 https://github.com/pharo-project/pharo/pull/11254 - Review if #scanToken: in RBScanner is still needed #11554 https://github.com/pharo-project/pharo/pull/11554 - Clean some duplication logic by extracting Smalltalk tools into a sepâ¦ #12085 https://github.com/pharo-project/pharo/pull/12085 - move emit from Announcement to Object #12266 https://github.com/pharo-project/pharo/pull/12266 Trivial Cleanups ================ - 9 x cleanups of the kind Cleanup: Condense NECompletion packages #12485 https://github.com/pharo-project/pharo/pull/12485 - 2x cleanups of the kind extract return from ifTrue: ifFalse: and remove white spaces #12476 https://github.com/pharo-project/pharo/pull/12476

1 0

Code quality: tagging unsent selectors (e.g. in tests)
by Marcus Denker Jan. 30, 2023

Jan. 30, 2023

Hi, If you have in your code a message send with a selector that is not implemented anywhere, it likely will result in a DNU - but not if you compile a method on the fly (used in tests often) - if the DNU is catched (e.g. for a proxy pattern) - if the code is compatibility code, never executed in this version of the system We can ban the rule, but that just stopps checking for the whole method for all selectors, what we want is to communicate that *this selector* is ok in this special use (per method granularity is ok). SystemNaviation>>#allUnimplementedCalls did have the feature that one can tag selectors that should be ignored. This uses the pragma #ignoreUnimplementedCalls: see Context class >> initializePrimitiveSimulators <ignoreUnimplementedCalls: #(#registerPrimitiveSimulators)> This was used in just one method, I think because a) the rule did not take it into account and b) the terminology is just wrong (âCallâ). I think - ReSentNotImplementedRule should takes this pragma into account - change the bad terminology âallUnimplementedCalls" - use pragma: <ignoreNotImplementedSelectors: > PR is here: https://github.com/pharo-project/pharo/pull/12295 (what the PR does not yet do is to change syntax highlight to not color the selector red, this could be done later, too)

3 5

This week (4/2023) on the Pharo Issue Tracker
by Marcus Denker Jan. 27, 2023

Jan. 27, 2023

This week, we merged 28 Pull requests, fixing 31 issues Fixes ===== - Update BaselineOfPharo with Roassal3 version v0.9.9L #12430 https://github.com/pharo-project/pharo/pull/12430 - checkIfMustRefresh in OmBlockFileStore>>blockForLocalNameAsInteger: #12197 https://github.com/pharo-project/pharo/pull/12197 - Fix for multiple Epicea issues #12375 https://github.com/pharo-project/pharo/pull/12375 - FIX CI issues - FFIExternalString>>#basicHandle:at: calls deprecated message #12405 https://github.com/pharo-project/pharo/pull/12405 - Fix for "Browse this version in Calypso" Error after clicking an unloaded package #12423 https://github.com/pharo-project/pharo/pull/12423 - 12410-Minimal-Image-does-not-open-ChangesFile-correctly #12411 https://github.com/pharo-project/pharo/pull/12411 - fix testTallyInstructions #12393 https://github.com/pharo-project/pharo/pull/12393 - Spotter is broken> DNU #tools #12397 https://github.com/pharo-project/pharo/pull/12397 Cleanups ======== - RubScrolledTextMorph>>#mouseWheel: sends unimplemented message #scrolâ¦ #12402 https://github.com/pharo-project/pharo/pull/12402 - 12416-Fixing-Classes-Reported-by-NoUnusedVariablesLeftTest #12417 https://github.com/pharo-project/pharo/pull/12417 - 12413-Improving-the-dependency-of-Formatter-Settings-with-EFFormatter #12414 https://github.com/pharo-project/pharo/pull/12414 - Move #asNumber from AST-Core to Kernel (where it is also already tested) #12388 https://github.com/pharo-project/pharo/pull/12388 - extract return from ifTrue:ifFalse: in Integer>>#printStringRadix: #12433 https://github.com/pharo-project/pharo/pull/12433 - 11x Cleanups of the kind Cleanup: Condense Calypso packages #12284 https://github.com/pharo-project/pharo/pull/12284 this Changelog is archived at https://github.com/pharo-project/pharo-changelogs/blob/master/weekly/2023/4…

1 0

[Issue Tracker] reviews needed
by Marcus Denker Jan. 26, 2023

Jan. 26, 2023

Hi, I wanted again to make some noise about the issue tracker. Yes, we merge 20-40 PRs per week, but even with that, there are many PRs in the queueâ¦ e.g. - Complete symbols #11918 https://github.com/pharo-project/pharo/pull/11918 - 12128-Poor-performance-with-large-WriteStreams #12205 https://github.com/pharo-project/pharo/pull/12205 - Fix Calypso browsing unloaded package artifacts from Iceberg #12425 https://github.com/pharo-project/pharo/pull/12425 - Introducing a Color Palette to cache the allocation of Color objects by tht UITheme #12419 https://github.com/pharo-project/pharo/pull/12419 We have open 35 PRs, the complete list is here: https://github.com/pharo-project/pharo/pulls some random notes: - reviews are always helpful, and even if there is already a positive review, a second one helps. - one part of a review is to check that the code is not doing obvious bad things (like un-doing older changes, dumb mistakesâ¦.) if you feel unsure what you can do as you do not really understand the change, that one you can check (and just say that in the review). - if you do PRs e.g with a pair, ask the person that did not commit to add a real review so it is clear that there where already two eyes on the code - if you work in a team, ask your team mates to review your code especially if you use that fix already internally - if you use the fix in your project already, add a review to just state that - if you see a fix where you think âI hope this will be merged soonâ, if you review, you will make it much easierâ¦ - if you see a fix that is reviewed, green and not merged and you do not understand why: do a review - consider just reviewing / doing *something* once every week. or even once every day, instead of letting it all pile up. Marcus

1 0

Pharo11 32 bits images missing?
by Pierre Misse Chanabier Jan. 23, 2023

Jan. 23, 2023

Hello, Apparently Pharo 11 does not build 32 bit images [1]. Did I miss an announcement? Pierre http://files.pharo.org/image/110/

2 1