- Pharo-dev - lists.pharo.org

Fun with dates

by Guillermo Polito

Try to guess what each of the following lines of code do: '''/5%9/$#=7*''*(?&&)58-,=93/1(0 1&<"1%?#$-::#)' asDate. '*%!(a)$4*4#!$!.&0-";)7.<7?%(; $535(0536.%#56&++''3!%0/' asDate. '/-@+%3:3.''9"04=. @5+$;"& (6.-,?@*6"?43@@>*>:' asDate. '1(%&0:19)) 7-?1.8;=?8+!&42-(?#>357).!=21603* 6=?38.1**,//'':@663>.09!2%=!%%%2!>4'':@#/8!@==2>%651)</' asDate. ',$*3,3''="0+0>:#14-8+(1@$&827%6-!)9-<>:"2+>&*39 !"(27' asDate. '''"?. <>!@"2(%7#)0 )46+#'';=+"94?%)9 +!<.+!9,2*5("9$11-,?49 =6*77. 0;/''%%/*' asDate. '4.+@)3&11)."+.6=$&$0>5:5;:$,%5-+,4$0>")>4838''*2/' asDate. '!7$:''!@0=)?0?<#&@*./0.:&?$?4 =<!><(7)@3$!:"$%%=""/?4*4=0?*$).,<+& ::"8>:925$8!,2,95' asDate. ' &+?!$3"(<*)1");35 $:&<"$!' asDate. '>6(# %2736:-1#@@9%9''+"#?37''2,<3>8-*5"$2-6#''365++*8 &' asDate. '?(2/=-@=@:4?/(3$3(8"&,!-2/&6&&' asDate. '&?7+=''9,:$(430,3#/$4#866'';2/*,?):. -!#"7=?6:$3"5 -$/=0' asDate. '3-;;=72@,9=%*.;+)74@7") -&?(''7+!3-3<-0,<8:(,,;+5-$:81#&6''7830;"01+@>7<37''!(#/9"6%0?' asDate. ';";5!9!,4/;25!0(<$4)''2"(2&-''4/>/.'')99(>><' asDate. '03="9-/,*(;74"%@>=''91%>#=*=6*0/#02@?)0.' asDate G

July 19, 2023

Re: Pharo-dev Digest, Vol 123, Issue 4

by Miloslav.Raus＠cuzk.cz

Sorry if I seemed too harsh, if there was not a direct miss-spelling, I would've kept my mouth on leash. But ... And then I checked for some "authoritative source", in the name of consistency (multiple variants in one conference?). Should've probably just said I consider it rude & unprofessional , but oftentimes my cheekiness gets the better of me. PS: And here it comes again: Mr. Ducasse, so after another six years (in the spirit of https://xkcd.com/605/) we can expect two miss-spellings in one conference ? ð ________________________________ From: Oleksandr Zaitsev <olk.zaytsev(a)gmail.com> Sent: Tuesday, July 18, 2023 9:19:03 PM To: pharo-dev(a)lists.pharo.org Subject: [Pharo-dev] Re: Pharo-dev Digest, Vol 123, Issue 4 Thanks Miloslav, It's nice to see that someone is concerned about the spelling of my name :) StÃ©phane is right, I have three passports: - one with "Zaytsev" - one with "Zaitsev" - and the main one with "ÐÐ°Ð¹ÑÐµÐ²" So there are multiple spellings And you can't imagine the kinds of problems I had with the French administration :) But I prefer to use Zaitsev Oleks On Tue, Jul 18, 2023 at 4:15â¯PM <pharo-dev-request(a)lists.pharo.org<mailto:pharo-dev-request@lists.pharo.org>> wrote: Send Pharo-dev mailing list submissions to pharo-dev(a)lists.pharo.org<mailto:pharo-dev@lists.pharo.org> To subscribe or unsubscribe via email, send a message with subject or body 'help' to pharo-dev-request(a)lists.pharo.org<mailto:pharo-dev-request@lists.pharo.org> You can reach the person managing the list at pharo-dev-owner(a)lists.pharo.org<mailto:pharo-dev-owner@lists.pharo.org> When replying, please edit your Subject line so it is more specific than "Re: Contents of Pharo-dev digest..." Today's Topics: 1. Re: Do not miss ESUG 2023 (Arturo Zambrano) 2. Re: Do not miss ESUG 2023 (Arturo Zambrano) 3. Re: Do not miss ESUG 2023 (Miloslav.Raus(a)cuzk.cz<mailto:Miloslav.Raus@cuzk.cz>) 4. Re: Do not miss ESUG 2023 (Miloslav.Raus(a)cuzk.cz<mailto:Miloslav.Raus@cuzk.cz>) ---------------------------------------------------------------------- Message: 1 Date: Tue, 18 Jul 2023 13:20:06 +0200 From: Arturo Zambrano <arturo.zambrano(a)gmail.com<mailto:arturo.zambrano@gmail.com>> Subject: [Pharo-dev] Re: Do not miss ESUG 2023 To: Pharo Development List <pharo-dev(a)lists.pharo.org<mailto:pharo-dev@lists.pharo.org>> Message-ID: <CALB2C6sO3L-jojXA4yUZsoOaEfb1ZRJgqzrJ8ktrhyM9phWwXQ(a)mail.gmail.com<mailto:CALB2C6sO3L-jojXA4yUZsoOaEfb1ZRJgqzrJ8ktrhyM9phWwXQ@mail.gmail.com>> Content-Type: multipart/alternative; boundary="0000000000007d51d70600c11ade" Hi!, is there a schedule for the ESUG 2023? I don't know if I can attend the 5 days, I will probably need to choose. Thanks On Wed, Jun 14, 2023 at 7:49â¯AM stephane ducasse <stephane.ducasse(a)inria.fr<mailto:stephane.ducasse@inria.fr>> wrote: > Just a little reminderâ¦ > > Do not miss ESUG 2023. > http://registration.esug.org/ > > come and meet the community > https://www.youtube.com/watch?v=9p-AkoHjRVk > > The city is really nice, the food great, super nice conference. > Really nice museums. > https://esug.github.io/2023-Conference/city2023.html > > by train â¦ > 2:30 hours from Paris > 4 hours from Brussels > 5 hours from Barcelona > 2 hours from Geneves > An international airport > > It is uncertain that we will organize a PharoDays in 2023/2024 so > enjoy the fact that you can come to that conference now. > > S. > > PS: do not hesitate to contact the ESUG board in case of special situations > > > -- Arturo Zambrano LinkedIn: https://www.linkedin.com/in/arturozambrano/

July 19, 2023

Re: Pharo-dev Digest, Vol 123, Issue 4

by Oleksandr Zaitsev

Thanks Miloslav, It's nice to see that someone is concerned about the spelling of my name :) StÃ©phane is right, I have three passports: - one with "Zaytsev" - one with "Zaitsev" - and the main one with "ÐÐ°Ð¹ÑÐµÐ²" So there are multiple spellings And you can't imagine the kinds of problems I had with the French administration :) But I prefer to use Zaitsev Oleks On Tue, Jul 18, 2023 at 4:15â¯PM <pharo-dev-request(a)lists.pharo.org> wrote: > Send Pharo-dev mailing list submissions to > pharo-dev(a)lists.pharo.org > > To subscribe or unsubscribe via email, send a message with subject or > body 'help' to > pharo-dev-request(a)lists.pharo.org > > You can reach the person managing the list at > pharo-dev-owner(a)lists.pharo.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Pharo-dev digest..." > > Today's Topics: > > 1. Re: Do not miss ESUG 2023 (Arturo Zambrano) > 2. Re: Do not miss ESUG 2023 (Arturo Zambrano) > 3. Re: Do not miss ESUG 2023 (Miloslav.Raus(a)cuzk.cz) > 4. Re: Do not miss ESUG 2023 (Miloslav.Raus(a)cuzk.cz) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 18 Jul 2023 13:20:06 +0200 > From: Arturo Zambrano <arturo.zambrano(a)gmail.com> > Subject: [Pharo-dev] Re: Do not miss ESUG 2023 > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > Message-ID: > < > CALB2C6sO3L-jojXA4yUZsoOaEfb1ZRJgqzrJ8ktrhyM9phWwXQ(a)mail.gmail.com> > Content-Type: multipart/alternative; > boundary="0000000000007d51d70600c11ade" > > Hi!, > is there a schedule for the ESUG 2023? I don't know if I can attend the 5 > days, I will probably need to choose. > > Thanks > > On Wed, Jun 14, 2023 at 7:49â¯AM stephane ducasse < > stephane.ducasse(a)inria.fr> > wrote: > > > Just a little reminderâ¦ > > > > Do not miss ESUG 2023. > > http://registration.esug.org/ > > > > come and meet the community > > https://www.youtube.com/watch?v=9p-AkoHjRVk > > > > The city is really nice, the food great, super nice conference. > > Really nice museums. > > https://esug.github.io/2023-Conference/city2023.html > > > > by train â¦ > > 2:30 hours from Paris > > 4 hours from Brussels > > 5 hours from Barcelona > > 2 hours from Geneves > > An international airport > > > > It is uncertain that we will organize a PharoDays in 2023/2024 so > > enjoy the fact that you can come to that conference now. > > > > S. > > > > PS: do not hesitate to contact the ESUG board in case of special > situations > > > > > > > > -- > Arturo Zambrano > LinkedIn: https://www.linkedin.com/in/arturozambrano/ >

July 18, 2023

Re: Do not miss ESUG 2023

by Miloslav.Raus＠cuzk.cz

I went by the spelling he uses on his own pages. And if I, as hinted by the ending of my domain name, were to spell his name, I'm sure as hell it would come out as 'Zajcev", so please ... ________________________________ From: stephane.ducasse(a)free.fr <stephane.ducasse(a)free.fr> Sent: Tuesday, July 18, 2023 4:03:53 PM To: Pharo Development List Cc: RauÅ¡ Miloslav Subject: Re: [Pharo-dev] Do not miss ESUG 2023 I will fix it. Now oleksandrâ s name has multiple spelling. S On 18 Jul 2023, at 13:31, Miloslav.Raus--- via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: Thx, just had a nice game of "do you know the given name of the person presenting / why do you remember it" ð If anyone organizing this event is around, you butchered at least Oleksandr Zaitsev's name multiple times. At least once as Zaytsev & Zaystev. Cheers. ________________________________ From: Arturo Zambrano <arturo.zambrano(a)gmail.com> Sent: Tuesday, July 18, 2023 1:21:45 PM To: Pharo Development List Subject: [Pharo-dev] Re: Do not miss ESUG 2023 OOPs, I have found it. sorry for the noise. In case anyone needs it: https://esug.github.io/2023-Conference/agenda/agenda.html On Tue, Jul 18, 2023 at 1:20â¯PM Arturo Zambrano <arturo.zambrano(a)gmail.com<mailto:arturo.zambrano@gmail.com>> wrote: Hi!, is there a schedule for the ESUG 2023? I don't know if I can attend the 5 days, I will probably need to choose. Thanks On Wed, Jun 14, 2023 at 7:49â¯AM stephane ducasse <stephane.ducasse(a)inria.fr<mailto:stephane.ducasse@inria.fr>> wrote: Just a little reminderâ¦ Do not miss ESUG 2023. http://registration.esug.org/ come and meet the community https://www.youtube.com/watch?v=9p-AkoHjRVk The city is really nice, the food great, super nice conference. Really nice museums. https://esug.github.io/2023-Conference/city2023.html by train â¦ 2:30 hours from Paris 4 hours from Brussels 5 hours from Barcelona 2 hours from Geneves An international airport It is uncertain that we will organize a PharoDays in 2023/2024 so enjoy the fact that you can come to that conference now. S. PS: do not hesitate to contact the ESUG board in case of special situations -- Arturo Zambrano LinkedIn: https://www.linkedin.com/in/arturozambrano/ -- Arturo Zambrano LinkedIn: https://www.linkedin.com/in/arturozambrano/

July 18, 2023

Re: Do not miss ESUG 2023

by Miloslav.Raus＠cuzk.cz

Thx, just had a nice game of "do you know the given name of the person presenting / why do you remember it" ð If anyone organizing this event is around, you butchered at least Oleksandr Zaitsev's name multiple times. At least once as Zaytsev & Zaystev. Cheers. ________________________________ From: Arturo Zambrano <arturo.zambrano(a)gmail.com> Sent: Tuesday, July 18, 2023 1:21:45 PM To: Pharo Development List Subject: [Pharo-dev] Re: Do not miss ESUG 2023 OOPs, I have found it. sorry for the noise. In case anyone needs it: https://esug.github.io/2023-Conference/agenda/agenda.html On Tue, Jul 18, 2023 at 1:20â¯PM Arturo Zambrano <arturo.zambrano(a)gmail.com<mailto:arturo.zambrano@gmail.com>> wrote: Hi!, is there a schedule for the ESUG 2023? I don't know if I can attend the 5 days, I will probably need to choose. Thanks On Wed, Jun 14, 2023 at 7:49â¯AM stephane ducasse <stephane.ducasse(a)inria.fr<mailto:stephane.ducasse@inria.fr>> wrote: Just a little reminderâ¦ Do not miss ESUG 2023. http://registration.esug.org/ come and meet the community https://www.youtube.com/watch?v=9p-AkoHjRVk The city is really nice, the food great, super nice conference. Really nice museums. https://esug.github.io/2023-Conference/city2023.html by train â¦ 2:30 hours from Paris 4 hours from Brussels 5 hours from Barcelona 2 hours from Geneves An international airport It is uncertain that we will organize a PharoDays in 2023/2024 so enjoy the fact that you can come to that conference now. S. PS: do not hesitate to contact the ESUG board in case of special situations -- Arturo Zambrano LinkedIn: https://www.linkedin.com/in/arturozambrano/ -- Arturo Zambrano LinkedIn: https://www.linkedin.com/in/arturozambrano/

July 18, 2023

Re: Do not miss ESUG 2023

by Arturo Zambrano

OOPs, I have found it. sorry for the noise. In case anyone needs it: https://esug.github.io/2023-Conference/agenda/agenda.html On Tue, Jul 18, 2023 at 1:20â¯PM Arturo Zambrano <arturo.zambrano(a)gmail.com> wrote: > Hi!, > is there a schedule for the ESUG 2023? I don't know if I can attend the 5 > days, I will probably need to choose. > > Thanks > > On Wed, Jun 14, 2023 at 7:49â¯AM stephane ducasse < > stephane.ducasse(a)inria.fr> wrote: > >> Just a little reminderâ¦ >> >> Do not miss ESUG 2023. >> http://registration.esug.org/ >> >> come and meet the community >> https://www.youtube.com/watch?v=9p-AkoHjRVk >> >> The city is really nice, the food great, super nice conference. >> Really nice museums. >> https://esug.github.io/2023-Conference/city2023.html >> >> by train â¦ >> 2:30 hours from Paris >> 4 hours from Brussels >> 5 hours from Barcelona >> 2 hours from Geneves >> An international airport >> >> It is uncertain that we will organize a PharoDays in 2023/2024 so >> enjoy the fact that you can come to that conference now. >> >> S. >> >> PS: do not hesitate to contact the ESUG board in case of special >> situations >> >> >> > > -- > Arturo Zambrano > LinkedIn: https://www.linkedin.com/in/arturozambrano/ > -- Arturo Zambrano LinkedIn: https://www.linkedin.com/in/arturozambrano/

July 18, 2023

Re: Do not miss ESUG 2023

by Arturo Zambrano

Hi!, is there a schedule for the ESUG 2023? I don't know if I can attend the 5 days, I will probably need to choose. Thanks On Wed, Jun 14, 2023 at 7:49â¯AM stephane ducasse <stephane.ducasse(a)inria.fr> wrote: > Just a little reminderâ¦ > > Do not miss ESUG 2023. > http://registration.esug.org/ > > come and meet the community > https://www.youtube.com/watch?v=9p-AkoHjRVk > > The city is really nice, the food great, super nice conference. > Really nice museums. > https://esug.github.io/2023-Conference/city2023.html > > by train â¦ > 2:30 hours from Paris > 4 hours from Brussels > 5 hours from Barcelona > 2 hours from Geneves > An international airport > > It is uncertain that we will organize a PharoDays in 2023/2024 so > enjoy the fact that you can come to that conference now. > > S. > > PS: do not hesitate to contact the ESUG board in case of special situations > > > -- Arturo Zambrano LinkedIn: https://www.linkedin.com/in/arturozambrano/

July 18, 2023

This week (28/2023) on the Pharo Issue Tracker

by Marcus Denker

# This week (28/2023) on the Pharo Issue Tracker Due to holiday season, the next weekly report will be done beginning of August. But activity does not stop! If you do not want to miss anything, consider watching the pharo github repo at https://github.com/pharo-project/pharo # Pharo11 Backports - [Pharo11] backport Slot related fixes #13950 and #13949 #14275 https://github.com/pharo-project/pharo/pull/14275 - [Pharo11] This is a backport: 14034 debugger does not evaluate in the context of the receiver #14274 https://github.com/pharo-project/pharo/pull/14274 - Depends on DocumentBrowser v1.0.1 #14277 https://github.com/pharo-project/pharo/pull/14277 # Fixes - 14226-nil-cannot-be-pinned-in-memory #14227 https://github.com/pharo-project/pharo/pull/14227 - FileBrowser. View as hex not working #14210 https://github.com/pharo-project/pharo/pull/14210 - added convenience methods to easy the usage of TFProcessLocalWorker #14255 https://github.com/pharo-project/pharo/pull/14255 - Treat Integers and Fractions as having scale 0 in ScaledDecimal arithmetic (fixes #14238) #14259 https://github.com/pharo-project/pharo/pull/14259 - Fix haltOn tests after debug them #14167 https://github.com/pharo-project/pharo/pull/14167 - fix calculous of layout when morph is not visible #14229 https://github.com/pharo-project/pharo/pull/14229 - Fix SpChangeSorterPresenter, MessageBrowserPresenter #567 https://github.com/pharo-spec/NewTools/pull/567 - Disable automated transform for deprecation of Object>>asOrderedCollection #14237 https://github.com/pharo-project/pharo/pull/14237 # Refactoring Engine - Fix the preconditions related to packages in refactorings #14236 https://github.com/pharo-project/pharo/pull/14236 - Refactor: clean RBCondition and add popUp flag #14240 https://github.com/pharo-project/pharo/pull/14240 - Refactoring: reuse RBAddMethodTransformRefactoring #14245 https://github.com/pharo-project/pharo/pull/14245 - Fix: update changes preview table when changing active scope #14267 https://github.com/pharo-project/pharo/pull/14267 - Splitting preconditions #14233 https://github.com/pharo-project/pharo/pull/14233 - Fix failing release test about refactorings #14252 https://github.com/pharo-project/pharo/pull/14252 # Compiler / Variables - This fixes #isClean as described in #14141 #14282 https://github.com/pharo-project/pharo/pull/14282 - ClassParser: parse non-fluid defintion of CompiledBlock #14270 https://github.com/pharo-project/pharo/pull/14270 - Improve deprecated slot #14265 https://github.com/pharo-project/pharo/pull/14265 # RPackage - Simplification in Monticello #14244 https://github.com/pharo-project/pharo/pull/14244 - Factorize some unregistering code #14290 https://github.com/pharo-project/pharo/pull/14290 - Remove some overriden methods in Monticello #14293 https://github.com/pharo-project/pharo/pull/14293 - Merge addition of class definition in rpackage #14291 https://github.com/pharo-project/pharo/pull/14291 - Cleaning in RPackage tests #14288 https://github.com/pharo-project/pharo/pull/14288 - Start unification of package removal #14283 https://github.com/pharo-project/pharo/pull/14283 - Push usage of #ensurePackage: #14280 https://github.com/pharo-project/pharo/pull/14280 - Simplify package removal #14281 https://github.com/pharo-project/pharo/pull/14281 - Remove unused method parameter in repackaging #14278 https://github.com/pharo-project/pharo/pull/14278 - Clean MCWorkingCopy #14248 https://github.com/pharo-project/pharo/pull/14248 - Remove rpackage presence check #14272 https://github.com/pharo-project/pharo/pull/14272 - Clean PackageOrganizer methods in testing protocol #14224 https://github.com/pharo-project/pharo/pull/14224 - Deprecate RPackageOrganizer>>#registerPackageNamed: #14260 https://github.com/pharo-project/pharo/pull/14260 - Fix bug in tag creation while creating a category #14256 https://github.com/pharo-project/pharo/pull/14256 - Introduce RPackageOrganizer>>ensurePackage: #14254 https://github.com/pharo-project/pharo/pull/14254 - Deprecate #includesPackageNamed: #14246 https://github.com/pharo-project/pharo/pull/14246 - Introduce RPackageOrganizer#hasPackage: #14232 https://github.com/pharo-project/pharo/pull/14232 # Protocols - Deprecated CompiledMethod tag API #14243 https://github.com/pharo-project/pharo/pull/14243 - Bugfix: Fix double protocol request in Calypso #14268 https://github.com/pharo-project/pharo/pull/14268 - Do not prevent all announcements during method classification #14273 https://github.com/pharo-project/pharo/pull/14273 - Remove unclassify hack #14264 https://github.com/pharo-project/pharo/pull/14264 - Deprecate class reorganized #14285 https://github.com/pharo-project/pharo/pull/14285 - Rename more methods and classes to use "Protocol" vocabulary #14266 https://github.com/pharo-project/pharo/pull/14266 - Fix logging of protocol in Opal #13886 https://github.com/pharo-project/pharo/pull/13886 - Rename some more tags into protocol #14247 https://github.com/pharo-project/pharo/pull/14247 - Do not register to ClassReorganized #566 https://github.com/pharo-spec/NewTools/pull/566 # Cleanup - Remove dead code in bootstrap #14258 https://github.com/pharo-project/pharo/pull/14258 - Update bootstrap scripts #14249 https://github.com/pharo-project/pharo/pull/14249 - 14239-remove-ReAnySatisfyRule #14279 https://github.com/pharo-project/pharo/pull/14279 - Cleanup: Explore it menu entries #14271 https://github.com/pharo-project/pharo/pull/14271 - DeadCodeCleanup-07-10 #14253 https://github.com/pharo-project/pharo/pull/14253 - Dependency Analyser title management #14225 https://github.com/pharo-project/pharo/pull/14225 - 1422-SpDemoconnectPresenters-uses-non-existing-setSelectedItem #1423 https://github.com/pharo-spec/Spec/pull/1423

July 14, 2023

This week (27/2023) on the Pharo Issue Tracker

by Marcus Denker

# Features - #14173 Introduce a nice command to spot the closest method overriden â¦ #14183 https://github.com/pharo-project/pharo/pull/14183 - Update Fuel from upstream #14132 https://github.com/pharo-project/pharo/pull/14132 # Fixes - 14034 debugger does not evaluate in the context of the receiver #14203 https://github.com/pharo-project/pharo/pull/14203 - double click selection on symbols should include # #14160 https://github.com/pharo-project/pharo/pull/14160 - Fixed String>>#keywords #14157 https://github.com/pharo-project/pharo/pull/14157 # Refactoring Engine - Fixing remove hack #14154 https://github.com/pharo-project/pharo/pull/14154 - First version of the renameMethod as a driver. #14161 https://github.com/pharo-project/pharo/pull/14161 - New flow for MoveMethodsToClassSide #14192 https://github.com/pharo-project/pharo/pull/14192 - Improve deprecate method flow in driver #14186 https://github.com/pharo-project/pharo/pull/14186 - Cleanup: StRefactoringPreviewPresenter #14206 https://github.com/pharo-project/pharo/pull/14206 - Composing and reusing add method refactoring/transformation #14134 https://github.com/pharo-project/pharo/pull/14134 - 14191 failing tests rb code snippet testtest styler #14202 https://github.com/pharo-project/pharo/pull/14202 - Fix #14178: cleaning ui of refactoring to use Spec instead of UIManager #14181 https://github.com/pharo-project/pharo/pull/14181 # RPackage - Remove references to #allManagers in RPackage #14189 https://github.com/pharo-project/pharo/pull/14189 - Keep pushing for rpackage knowing their organizer #14187 https://github.com/pharo-project/pharo/pull/14187 - Simplify setup of RPackageOrganizer in tests #14204 https://github.com/pharo-project/pharo/pull/14204 - Simplification of the package validation #14223 https://github.com/pharo-project/pharo/pull/14223 - Rename #allManagers into #allWorkingCopies #14217 https://github.com/pharo-project/pharo/pull/14217 - Remove RPackageORganizer>>#hasRegistered #14231 https://github.com/pharo-project/pharo/pull/14231 # Protocol Cleanup - Rename ClyTaggedMethodsQuery into ClyMethodsInProtocolQuery #14188 https://github.com/pharo-project/pharo/pull/14188 - Clean #affectsMethodsTaggedWith: #14219 https://github.com/pharo-project/pharo/pull/14219 # Cleanup - better naming for presenter that are presenters #564 https://github.com/pharo-spec/NewTools/pull/564 - SmalltalkImage>>#newSpecialObjectsArray remove elements not used by the VM #14208 https://github.com/pharo-project/pharo/pull/14208 - 10568-hardcoded-class-definition-in-opal #14207 https://github.com/pharo-project/pharo/pull/14207 - fix-deprecated-send-testCreateGroupsForEveryMethodTag #14159 https://github.com/pharo-project/pharo/pull/14159 - changebrowser -> stChangeBrowserPresenter #14182 https://github.com/pharo-project/pharo/pull/14182 - Some users of inform: that could simply use the inform: from Object. #14180 https://github.com/pharo-project/pharo/pull/14180 - 14164--ChunkImportTestCasetestImportAMethodWithSpacesInItsCategory--calls-category #14194 https://github.com/pharo-project/pharo/pull/14194 - DeadCode-Cleanup-07-05 #14216 https://github.com/pharo-project/pharo/pull/14216 - 14162-UUIDGenerator-uses-of-deprecated-method-in-tests #14214 https://github.com/pharo-project/pharo/pull/14214 - This PR removes dead code related to VTerm output classes #14215 https://github.com/pharo-project/pharo/pull/14215 # Comments / Tests - Add tests for primitive adoptInstance and the sibling primitiveChangeClassTo #14220 https://github.com/pharo-project/pharo/pull/14220 - SmalltalkImage>>garbageCollect : correct method comment #14193 https://github.com/pharo-project/pharo/pull/14193 - Add test on installing a class in a non default environment #14222 https://github.com/pharo-project/pharo/pull/14222 - Added comments to the new instrumentation package #14228 https://github.com/pharo-project/pharo/pull/14228

July 10, 2023

Re: [Help needed] 160 method with "sent but not implemented" selectors

by Marcus Denker

> On 1 Jul 2023, at 04:54, Bernardo Ezequiel Contreras <vonbecmann(a)gmail.com> wrote: > > these > > |selectors| > selectors := SystemNavigation new allSentNotImplementedSelectors. > selectors select: [ :each | each senders isEmpty ]. > > can be removed? > Most likely, but not 100%: - some are tests - there could be a pragma that is used to discover a method - it could be test code and removing the method could lead to a test failing - it could be called reflectively - it could be an API that we want to keep and fix (not very likely) So yes, it is a good way to find methods to remove, but it can not be done automatically Marcus > On Fri, Jun 30, 2023 at 11:15â¯AM Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: >> This is a not-that important cleanup: It would be nice if we would tag or fix all methods with "sent but not implementedâ selectors >> >> if you inspect: >> >> SystemNavigation new allSentNotImplementedSelectors >> >> >> you get 160 methods in Pharo12. >> >> - some are dead code >> -> we should remove those >> >> - some are methods used for tests >> - there might be some that are send to objects with a DNU handler >> -> we should tag them using the < #ignoreNotImplementedSelectors: #()> Pragma >> >> - some are bugs >> -> we should fix those >> >> Helo is welcome! >> >> If we fix them all we can add a release test and make sure that code like this never is merged. >> >> >> Marcus > > > -- > Bernardo E.C. > > Sent from a cheap desktop computer in South America.

July 3, 2023