September 2021 - Pharo-dev - lists.pharo.org

Re: in the quest of cutOn:

by Esteban Maringolo

The where is a better suffix than the "on". I'd prefer something like: 'abcDefKjm' splitWhere: [:a | a isUppercase ] -> #('abc' 'Def' 'Kjm') Regards, Esteban A. Maringolo On Wed, Sep 29, 2021 at 1:58 PM stephane ducasse <stephane.ducasse(a)inria.fr> wrote: > > 'abcDefKjlkj' piecesCutWhere:[ :a :b | b isUppercase ] > > > > > On 29 Sep 2021, at 18:55, stephane ducasse <stephane.ducasse(a)inria.fr> wrote: > > > > 'abcDef' splitOn: [ :c | c isUppercase ] > >>>> âabcâ âefâ > > > > but I need > > > > 'abcDef' splitOn: [ :c | c isUppercase ] > >>>> âabcâ âDefâ > > > > :(

Sept. 29, 2021

Re: in the quest of cutOn:

by stephane ducasse

'abcDefKjlkj' piecesCutWhere:[ :a :b | b isUppercase ] > On 29 Sep 2021, at 18:55, stephane ducasse <stephane.ducasse(a)inria.fr> wrote: > > 'abcDef' splitOn: [ :c | c isUppercase ] >>>> âabcâ âefâ > > but I need > > 'abcDef' splitOn: [ :c | c isUppercase ] >>>> âabcâ âDefâ > > :(

Sept. 29, 2021

in the quest of cutOn:

by stephane ducasse

'abcDef' splitOn: [ :c | c isUppercase ] >>> âabcâ âefâ but I need 'abcDef' splitOn: [ :c | c isUppercase ] >>> âabcâ âDefâ :(

Sept. 29, 2021

Re: Hardening Zinc's Core HTTP Server

by Sven Van Caekenberghe

Both instances have been up for 5 days now, looking for more testers. > On 23 Sep 2021, at 17:03, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Hi, > > Zinc HTTP Components [https://github.com/svenvc/zinc] has been a part of Pharo since version 1.3 (2011). It is an open-source framework to deal with the HTTP networking protocol, modelling all aspects involved. It also offers both client and server functionality. > > The reliability of the code base has improved steadily over the years, thanks to virtually all Pharo developers using it, directly or indirectly. Over the summer a number of issues that popped up after Pharo 9 was released were resolved. > > The robustness of the core HTTP server is one important aspect. To put this quality further to the test, I deployed two servers with the same demo Seaside application, Reddit.st, open to the internet, without any further protections. > > - On Amazon AWS: http://34.245.183.130:1701 > > - On Microsoft Azure: http://51.137.72.94:8080 > > The application's source code can be found at [https://github.com/svenvc/Reddit] For the technically curious there are also deploy instructions at [https://github.com/svenvc/Reddit/blob/main/DEPLOY.md] The demo app itself is described in an older article [https://medium.com/@svenvc/reddit-st-in-10-cool-pharo-classes-1b5327ca0740] Note that, by definition, there is no HTTPS/TLS variant. > > If you manage to break this server with (a) malicious request(s) in such a way that you can explain what you did for others to confirm your approach, you not only help me/us improve the code, but earn eternal fame as well ;-) > > Sven > > PS: I hope I won't regret this, I am looking for constructive criticism. > > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org >

Sept. 29, 2021

Re: Ephemeron Status?

by Guillermo Polito

Hi Sean, Ephemerons are working well in Pharo 9, as far as I am concerned, at least from the VM side. We have thoroughly tested them and stressed the implementation with several thousand ephemerons. And we have used them to prototype a precise memory profiler with a student during the summer (yet to be published). But, there is still missing a good Ephemeron library from the image side. We were planning on having that for Pharo 10, but if somebody wants to take the lead on that, youâre welcome. Cheers, G > El 27 sept 2021, a las 20:56, sean(a)clipperadams.com escribiÃ³: > > What is the status of ephemerons/weakly held objects? Is this fully working or are there still limitations/gotchas? I have lost track >

Sept. 28, 2021

Ephemeron Status?

by sean＠clipperadams.com

What is the status of ephemerons/weakly held objects? Is this fully working or are there still limitations/gotchas? I have lost track

Sept. 27, 2021

Re: Git Method Timestamps

by sean＠clipperadams.com

Sven Van Caekenberghe wrote: > I don't know how to do this programmatically Thatâs what Iâm trying to figure out :)

Sept. 27, 2021

This week (38/2021) on the Pharo Issue Tracker

by Marcus Denker

We merged 38 pull requests and fixed 26 issues. Pharo9 ====== update Spec version to v1.0.3 and NewTools to v0.6.10 #9974 https://github.com/pharo-project/pharo/pull/9974 BACKPORT-6311-Enhance-Completion-to-be-more-fluid-in-large-images #10003 https://github.com/pharo-project/pharo/pull/10003 - Backport: Pharo 9 + Seaside - Process dying on cloud instance #9987 https://github.com/pharo-project/pharo/pull/9987 Remove Deprecated and Dead Code =============================== - Cleanup methods declared as deprecated #10013 https://github.com/pharo-project/pharo/pull/10013 - Redo #9845 -- Fix 9798: Deprecated class TextConverter is still used #10012 https://github.com/pharo-project/pharo/pull/10012 - cleanup-Display-and-Cursor #9889 https://github.com/pharo-project/pharo/pull/9889 - Cleanup-Duplicated-Methods-09-18 #9989 https://github.com/pharo-project/pharo/pull/9989 - Cleanup: remove unreferenced deprecated class in Spec-Deprecated #9997 https://github.com/pharo-project/pharo/pull/9997 - Cleanup-Deprecated-Spec-Examples-Tests #9975 https://github.com/pharo-project/pharo/pull/9975 - Cleanup-Duplicated-Methods-09-17 #9978 https://github.com/pharo-project/pharo/pull/9978 Speed ===== - 6311-Enhance-Completion-to-be-more-fluid-in-large-images #10002 https://github.com/pharo-project/pharo/pull/10002 - do not re-parse in ReShouldSendSuperSetUpAsFirstMessage and ReShouldSendSuperTearDownAsLastMessage #9988 https://github.com/pharo-project/pharo/pull/9988 Features ======== - String #beginsWith:caseSensitive and #endsWith:caseSensitive: #9960 https://github.com/pharo-project/pharo/pull/9960 Refactoring Tools ================== - Migrating RBMoveMethodToClassRefactoring to RBMoveMethodToClassTransformation #9945 https://github.com/pharo-project/pharo/pull/9945 - Migrated RBTemporaryToInstanceVariableRefactoring to RBTemporaryToInsâ¦ #9944 https://github.com/pharo-project/pharo/pull/9944 Fixes ====== - 9961-cleanup-and-support-CompiledMethodLayout-in-CDClassDefinitionParserhandleClassNamewithType #10022 https://github.com/pharo-project/pharo/pull/10022 - 9936-MCClassDefinitionkindOfSubclass-wrong-for-user-defined-layouts #9939 https://github.com/pharo-project/pharo/pull/9939 - Fix ZnBufferedReadStream>>#setToEnd for ZipArchive usage #8658 https://github.com/pharo-project/pharo/pull/8658 - Fix #8524: Fix Process>>#priority: incorrectly allowing lower priority process run while â¦ #10004 https://github.com/pharo-project/pharo/pull/10004 - Fix #7634: Use "Smalltalk vm wordSize" to determine the version of the VM: 32 or 64 #10008 https://github.com/pharo-project/pharo/pull/10008 - fix: #9992 add pharo10 for metacello #9994 https://github.com/pharo-project/pharo/pull/9994 - 9965-CI-ZipArchiveTesttestArchiveWithThousandFilesShouldWork-sometimes-times-out #9969 https://github.com/pharo-project/pharo/pull/9969 - 9933-isDeprecated-should-not-check-for-the-category #9981 https://github.com/pharo-project/pharo/pull/9981 - Pharo 9 + Seaside - Process dying on cloud instance #9986 https://github.com/pharo-project/pharo/pull/9986 - Improve UI manager to allow testing by reacting to notifications #9979 https://github.com/pharo-project/pharo/pull/9979 - 9925-Defining-variables-in-the-debugger-DNU-isForScripting #9926 https://github.com/pharo-project/pharo/pull/9926 - Improve the flaky test for the ProcessMonitorTestService #9976 https://github.com/pharo-project/pharo/pull/9976 Cleanup ======= - Fixes #9972: SycSourceCodeRefactoringCommand should be tagged abstract #9977 https://github.com/pharo-project/pharo/pull/9977 - cleaning-up-workaround in copyTo: #10006 https://github.com/pharo-project/pharo/pull/10006 - 9970-ReConsistencyCheckRule-is-a-very-bad-name #9998 https://github.com/pharo-project/pharo/pull/9998 - Fix: #7974 deprecate openAndTruncateForWriteFile: #10009 https://github.com/pharo-project/pharo/pull/10009 - Small cleanups - class side initialize and other #9883 https://github.com/pharo-project/pharo/pull/9883 - Release test for #basicNew categorization #9897 https://github.com/pharo-project/pharo/pull/9897 - Improve ProperClassCategorizationTest>>#testProperClassTagCasing #9858 https://github.com/pharo-project/pharo/pull/9858 - [Enable Flaky Tests] Enable continuation flaky test #6768 https://github.com/pharo-project/pharo/pull/6768 - 9955-add-comments-to-mcType-subclassDefiningSymbol-kindOfSubclass #9983 https://github.com/pharo-project/pharo/pull/9983

Sept. 24, 2021

Hardening Zinc's Core HTTP Server

by Sven Van Caekenberghe

Hi, Zinc HTTP Components [https://github.com/svenvc/zinc] has been a part of Pharo since version 1.3 (2011). It is an open-source framework to deal with the HTTP networking protocol, modelling all aspects involved. It also offers both client and server functionality. The reliability of the code base has improved steadily over the years, thanks to virtually all Pharo developers using it, directly or indirectly. Over the summer a number of issues that popped up after Pharo 9 was released were resolved. The robustness of the core HTTP server is one important aspect. To put this quality further to the test, I deployed two servers with the same demo Seaside application, Reddit.st, open to the internet, without any further protections. - On Amazon AWS: http://34.245.183.130:1701 - On Microsoft Azure: http://51.137.72.94:8080 The application's source code can be found at [https://github.com/svenvc/Reddit] For the technically curious there are also deploy instructions at [https://github.com/svenvc/Reddit/blob/main/DEPLOY.md] The demo app itself is described in an older article [https://medium.com/@svenvc/reddit-st-in-10-cool-pharo-classes-1b5327ca0740] Note that, by definition, there is no HTTPS/TLS variant. If you manage to break this server with (a) malicious request(s) in such a way that you can explain what you did for others to confirm your approach, you not only help me/us improve the code, but earn eternal fame as well ;-) Sven PS: I hope I won't regret this, I am looking for constructive criticism. -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org

Sept. 23, 2021

About punishment vs. help

by stephane ducasse

Hi guys I would like to have mindset revolution. I would like that Pharo HELPS us to produce good code and not just PUNISH us when we do mistakes. Let me show you an example. I write a little method and as a good and nice programmer I place my little utility method in the utilities protocol. I commit and then I get a FAILED ERROR RED BAR telling that Iâm an asshole because I did not place that &*T^(^&(* method in utils. Something that Cop stuff is not even able to tell me precisely what is the problem There is a method in class X that use an undefined instance variables. I always thought that computers were about doing clever stuffâ¦ but the Cop inside Pharo proves me the inverse. I wonder why instead of investing in stupid rule we do not invest in building simple tool that do the job for us. Why the system cannot recategorise the method for me. Why the system does not remove the unused variable automatically prompting before I commit. Oh my dear StÃ©phane I saw that you left this horrible unused instance variable, do you want me to clean for you? Yes be my guest. This is why I invested by improving the automatic categorizer. This is why I did a tool to analyse the frequency of methods in terms of their protocol and you can ask the tool please fix all badly categorized methods. https://github.com/Ducasse/MethodCategorizer/blob/master/MethodCategorizer/… This is always why I HATE all these %^&*^&(&*^&*(%^(& warnings that get into my way when the system could fix them for me in no time. SO THIS IS A CALL FOR A CHANGE OF PARADIGM Can Pharo help me in my development instead of bitting me? Can we STOP adding more and more dull rules and produce something that HELP US? https://github.com/Ducasse/MethodCategorizer/blob/master/MethodCategorizer/… THIS IS NOT BECAUSE WE HAVE A HAMMER THAT WE SHOULD NAIL EVERYTHING. THIS IS OUR DUTY TO INVENT NEW TOOLS AND NEW WAYS TO HELP DEVELOPERS! S.

Sept. 22, 2021