- Pharo-dev - lists.pharo.org

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

by Bernardo Ezequiel Contreras

these |selectors| selectors := SystemNavigation new allSentNotImplementedSelectors. selectors select: [ :each | each senders isEmpty ]. can be removed? On Fri, Jun 30, 2023 at 11:15â¯AM Marcus Denker <marcus.denker(a)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 1, 2023

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

by Marcus Denker

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

June 30, 2023

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

by Marcus Denker

This week (26/2023) on the Pharo Issue Tracker # Fixes - 4074-Transcript-should-be-able-to-clear-the-contents-of-the-transcript #14100 https://github.com/pharo-project/pharo/pull/14100 - Remove ReUtilityMethodsRule #13947 https://github.com/pharo-project/pharo/pull/13947 - Updating graph algorithm library version #14115 https://github.com/pharo-project/pharo/pull/14115 - Allow repeated file-in (Named ChangeSet) #14124 https://github.com/pharo-project/pharo/pull/14124 - Calypso: Clean methods in protocol groups #14111 https://github.com/pharo-project/pharo/pull/14111 # Packages - Reference RPackage in RPackage packages #14151 https://github.com/pharo-project/pharo/pull/14151 - Packages should know their organizer #14110 https://github.com/pharo-project/pharo/pull/14110 - RPackage: Removing category should remove the tags #14119 https://github.com/pharo-project/pharo/pull/14119 - Demoting to package with tag should keep the organizer #14129 https://github.com/pharo-project/pharo/pull/14129 # Refactoring Engine - Simple duplication removal in Driver hierarchy #14117 https://github.com/pharo-project/pharo/pull/14117 - Fix #14146: Abstract accessors from variable is not working #14147 https://github.com/pharo-project/pharo/pull/14147 - Remove instance var driver #14144 https://github.com/pharo-project/pharo/pull/14144 # Compiler - Compiler: allow shadowing of PseudoVariables #14096 https://github.com/pharo-project/pharo/pull/14096 - 14133-CompiledCode-improve-and-add-tests-for-user-flag #14135 https://github.com/pharo-project/pharo/pull/14135 # ClassBuilder / Fluid - Non-Fluid: Improve check for CompiledMethodLayout #14108 https://github.com/pharo-project/pharo/pull/14108 - T2TraitSlotScopeTest: use classinstaller instead of class creation method #14137 https://github.com/pharo-project/pharo/pull/14137 - 14123-ReTestBasedTestCasesetUp-uses-old-style-class-creation-method #14126 https://github.com/pharo-project/pharo/pull/14126 - Calypso: add test for trait and class creation #14125 https://github.com/pharo-project/pharo/pull/14125 # Source Logging / Epicea - Remove some more categories in Epicea #14121 https://github.com/pharo-project/pharo/pull/14121 - Epicea: Introduce Package removal #14102 https://github.com/pharo-project/pharo/pull/14102 - Epicea: Reduces calls to #addCategory: #14105 https://github.com/pharo-project/pharo/pull/14105 - Epicea: Use the right API to create a package #14114 https://github.com/pharo-project/pharo/pull/14114 # Bootstrap / tests / ci - peedup FLGZippedBasicSerializationTest>>#testWideString #14112 https://github.com/pharo-project/pharo/pull/14112 - Move registration to SessionManager of more elements #13994 https://github.com/pharo-project/pharo/pull/13994 # Cleanups - fix noRemoteBlockReturn to use a known selector #14150 https://github.com/pharo-project/pharo/pull/14150 - Fix #12171 remove unused methods. #14118 https://github.com/pharo-project/pharo/pull/14118 - TTaskScheduler>>#scheduleTaskExecution: sends #requirement #14142 https://github.com/pharo-project/pharo/pull/14142

June 30, 2023

Re: [ANN] CBOR for Pharo

by Sven Van Caekenberghe

> On 23 Jun 2023, at 00:06, stephane ducasse <stephane.ducasse(a)inria.fr> wrote: > > Super nice > for a moment I thought that you forgot the final G of the name :) Haha, that would have been nice. It is a bit of a weird acronym. I must admit that I did not hear about it until recently. There are several binary JSON specifications, but this one has an elegance to it, I liked it immediately. And the best way to understand it or get a feel for it is to implement it. From time to time I need to do a project like this: small scope, clear spec, no drama. I would also like to iterate that doing binary coding in Pharo is really nice, elegant and powerful. >> On 21 Jun 2023, at 11:25, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> [ANN] CBOR for Pharo >> >> https://github.com/svenvc/CBOR >> >> Concise Binary Object Representation (CBOR) is a binary data serialization format. CBOR is based on the JSON data model: a number of primitive types (integers, floats, booleans, strings and null), lists and maps (which represent objects or structures). Being binary, CBOR is more efficient than JSON, which is text based. CBOR also supports binary data and optional extensions (called tags). This implementation has native support for string and epoch based timestamps (DateAndTime) and big integers (Integer). >> >> This project contains encoding/decoding support for the half-precision, IEEE 754 16-bit (binary16) floating-point format. >> >> Sven >> >> >> -- >> Sven Van Caekenberghe >> Proudly supporting Pharo >> http://pharo.org >> http://association.pharo.org >> http://consortium.pharo.org >> >> >>

June 23, 2023

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

by Marcus Denker

# Misc / Fixes - 14089-problem-showing-dock-icon-for-some-compiler-warnings-eg-name-aready-defined #14090 https://github.com/pharo-project/pharo/pull/14090 - Updated version of graph algos to use the latest one #14103 https://github.com/pharo-project/pharo/pull/14103 - Fix package file out #14076 https://github.com/pharo-project/pharo/pull/14076 - 14061-SequenceableCollectiongroupByRuns-should-be-packaged-in-Collections #14075 https://github.com/pharo-project/pharo/pull/14075 - adding-perm-space-statistics #14052 https://github.com/pharo-project/pharo/pull/14052 - Move Margin from Kernel to Graphics #14044 https://github.com/pharo-project/pharo/pull/14044 - Simplify #doBrowseImplementors and #doBrowseSenders #1411 https://github.com/pharo-spec/Spec/pull/1411 - [P12] Fix DNU when recompiling block with dead home #552 https://github.com/pharo-spec/NewTools/pull/552 - Trivial dead code cleanup #550 https://github.com/pharo-spec/NewTools/pull/550 # ClassBuilder / Fluid Class Definitions - reduce the usage of the non-fluid class definiton methods #14058 https://github.com/pharo-project/pharo/pull/14058 - another simplification of class builder users: Traits #14079 https://github.com/pharo-project/pharo/pull/14079 - Fix trait definition in Calypso when fluid is enabled #14088 https://github.com/pharo-project/pharo/pull/14088 - Non-Fluid class creation: use class builder, last batch #14099 https://github.com/pharo-project/pharo/pull/14099 - ClassInstaller: improve #update:to: to do the #fillFor: #14095 https://github.com/pharo-project/pharo/pull/14095 - ClassBuilder: reduce the need of #asSlotCollection and #asTraitComposition #14074 https://github.com/pharo-project/pharo/pull/14074 - ClassBuilder users: Do not set 'Unclassified' category/package explicitly #14066 https://github.com/pharo-project/pharo/pull/14066 - Fix class parser for non-fluid nil subclass definitions #14054 https://github.com/pharo-project/pharo/pull/14054 # Protocols / Categories - Update MethodAddition to use #protocol #14050 https://github.com/pharo-project/pharo/pull/14050 - Remove hardcoded 'as yet unclassified' #14085 https://github.com/pharo-project/pharo/pull/14085 - Remove ClyMethodTagsEditorMorph #14083 https://github.com/pharo-project/pharo/pull/14083 - Deprecate CompiledMethod>>#tags #14078 https://github.com/pharo-project/pharo/pull/14078 - Simplify ClyMethodEditorToolMorph #14069 https://github.com/pharo-project/pharo/pull/14069 - Deprecate CompiledMethod>>untagFrom: #14060 https://github.com/pharo-project/pharo/pull/14060 - Deprecated CompiledMethod>>tagWith: #14049 https://github.com/pharo-project/pharo/pull/14049 - Deprecated CompiledMethod>>category #14047 https://github.com/pharo-project/pharo/pull/14047 # RPackage Cleanup: Monticello - Merge MCWorkingCopy and MCPackageManager #14041 https://github.com/pharo-project/pharo/pull/14041 - Simplify MCWorkingCopy management #14040 https://github.com/pharo-project/pharo/pull/14040 - Remove some Monticello GUI #14059 https://github.com/pharo-project/pharo/pull/14059 - Decouple Monticello and RPackage on package removal #14072 https://github.com/pharo-project/pharo/pull/14072 - Finish Monticello decoupling in RPackage #14077 https://github.com/pharo-project/pharo/pull/14077 - Extract Monticello from package renmaing #14065 https://github.com/pharo-project/pharo/pull/14065 - Move WorkingCopy creation to Monticello #14036 https://github.com/pharo-project/pharo/pull/14036 - Move Monticello diffs to its own package #14067 https://github.com/pharo-project/pharo/pull/14067 - Remove double initialization of MCWorkingCopy #14064 https://github.com/pharo-project/pharo/pull/14064 - Iteration on package tag announcements #14081 https://github.com/pharo-project/pharo/pull/14081 # RPackage cleanup: Epicea (Source logging) - Epicea: Fix application of package addition and cleanup EpPackageAddition #1410 https://github.com/pharo-project/pharo/pull/14101 - Epicea: Add test on PackageAddition event #14092 https://github.com/pharo-project/pharo/pull/14092 - Epicea: Clean package addition and fix bugs #14087 https://github.com/pharo-project/pharo/pull/14087 # Compiler: Variables - rename ReservedVariable to PseudoVariable #14071 https://github.com/pharo-project/pharo/pull/14071 - PseudoVariable: add deprecations / cleanups #14082 https://github.com/pharo-project/pharo/pull/14082 - 14039-P12-RBVariableisDefinition-does-not-return-true-when-it-should #14051 https://github.com/pharo-project/pharo/pull/14051 # Refactoring Engine - Cleanup: change method name refactoring #14097 https://github.com/pharo-project/pharo/pull/14097 - Refactor: Add "(T)" prefix to Find and Replace transformation #14091 https://github.com/pharo-project/pharo/pull/14091 - Enh/refact pass on preconditions #14048 https://github.com/pharo-project/pharo/pull/14048

June 23, 2023

Re: [ANN] CBOR for Pharo

by Guillermo Polito

Thanks Sven :) > El 23 jun. 2023, a las 00:06, stephane ducasse <stephane.ducasse(a)inria.fr> escribiÃ³: > > Super nice > for a moment I thought that you forgot the final G of the name :) > >> On 21 Jun 2023, at 11:25, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> [ANN] CBOR for Pharo >> >> https://github.com/svenvc/CBOR >> >> Concise Binary Object Representation (CBOR) is a binary data serialization format. CBOR is based on the JSON data model: a number of primitive types (integers, floats, booleans, strings and null), lists and maps (which represent objects or structures). Being binary, CBOR is more efficient than JSON, which is text based. CBOR also supports binary data and optional extensions (called tags). This implementation has native support for string and epoch based timestamps (DateAndTime) and big integers (Integer). >> >> This project contains encoding/decoding support for the half-precision, IEEE 754 16-bit (binary16) floating-point format. >> >> Sven >> >> >> -- >> Sven Van Caekenberghe >> Proudly supporting Pharo >> http://pharo.org >> http://association.pharo.org >> http://consortium.pharo.org >> >> >>

June 23, 2023

Re: [ANN] CBOR for Pharo

by stephane ducasse

Super nice for a moment I thought that you forgot the final G of the name :) > On 21 Jun 2023, at 11:25, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > [ANN] CBOR for Pharo > > https://github.com/svenvc/CBOR > > Concise Binary Object Representation (CBOR) is a binary data serialization format. CBOR is based on the JSON data model: a number of primitive types (integers, floats, booleans, strings and null), lists and maps (which represent objects or structures). Being binary, CBOR is more efficient than JSON, which is text based. CBOR also supports binary data and optional extensions (called tags). This implementation has native support for string and epoch based timestamps (DateAndTime) and big integers (Integer). > > This project contains encoding/decoding support for the half-precision, IEEE 754 16-bit (binary16) floating-point format. > > Sven > > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org > > >

June 22, 2023

Re: [ANN] CBOR for Pharo

by Martin Dias

El miÃ©, 21 jun 2023 a la(s) 05:25, Sven Van Caekenberghe (sven(a)stfx.eu) escribiÃ³: > [ANN] CBOR for Pharo > > https://github.com/svenvc/CBOR > > Concise Binary Object Representation (CBOR) is a binary data serialization > format. CBOR is based on the JSON data model: a number of primitive types > (integers, floats, booleans, strings and null), lists and maps (which > represent objects or structures). Being binary, CBOR is more efficient than > JSON, which is text based. CBOR also supports binary data and optional > extensions (called tags). This implementation has native support for string > and epoch based timestamps (DateAndTime) and big integers (Integer). > > This project contains encoding/decoding support for the half-precision, > IEEE 754 16-bit (binary16) floating-point format. > Thanks Sven, it looks awesome. regards, MartÃn > > Sven > > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org > > > >

June 22, 2023

[ANN] CBOR for Pharo

by Sven Van Caekenberghe

[ANN] CBOR for Pharo https://github.com/svenvc/CBOR Concise Binary Object Representation (CBOR) is a binary data serialization format. CBOR is based on the JSON data model: a number of primitive types (integers, floats, booleans, strings and null), lists and maps (which represent objects or structures). Being binary, CBOR is more efficient than JSON, which is text based. CBOR also supports binary data and optional extensions (called tags). This implementation has native support for string and epoch based timestamps (DateAndTime) and big integers (Integer). This project contains encoding/decoding support for the half-precision, IEEE 754 16-bit (binary16) floating-point format. Sven -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org

June 21, 2023

Re: Fwd: [Pharo-users] Kind reminder: Survey on the usage of the system browser

by Noury Bouraqadi

Thank you Marcus for the repost. Koen's mail was in my spam. @Koen Welcome back to Smalltalk and Pharo :-) See you all at ESUG 2023 next August in Lyon, France. Noury On Jun 20 2023, at 12:09 pm, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > > Begin forwarded message: > > From: Koen De Hondt <koen(a)all-objects-all-the-time.st> > > Subject: [Pharo-users] Kind reminder: Survey on the usage of the system browser > > > > Date: 20 June 2023 at 12:08:00 CEST > > > > To: pharo-users(a)lists.pharo.org > > > > Reply-To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > > > > > > Hi Pharo users, > > > > A few weeks ago I sent the invitation below. I have received 45 responses. A big thanks to all who have taken the survey! > > > > If you have not taken the survey yet, I invite you again to do so. It will make the survey results better, and it will make the ESUG presentation better. > > > > Thank you! > > > > Best regards, > > Koen > > > > > Begin forwarded message: > > > From: Koen De Hondt <koen(a)all-objects-all-the-time.st> > > > Subject: [Pharo-users] Survey on the usage of the system browser > > > > > > Date: 31 May 2023 at 08:15:01 CEST > > > > > > To: pharo-users(a)lists.pharo.org > > > > > > Reply-To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > > > > > > > > > Dear Pharo users, > > > > > > I have submitted a proposal for a presentation at ESUGâ23. Part of the presentation will report on the results of a survey about the usage of the Pharo system browser. I need your help to produce the results ð. Therefore I invite you to take the survey at https://forms.gle/cBYs7DRwZvAVAyQb9. It is not too long, and totally anonymous. Your feedback is very much appreciated! > > > > > > Thanks in advance. > > > > > > Kind regards, > > > Koen > > > > > > PS: Maybe you wonder who this new kid on the block is. Actually, it is an old kid on the block. ð See https://all-objects-all-the-time.st (https://all-objects-all-the-time.st/)

June 21, 2023