April 2022 - Pharo-users - lists.pharo.org

Pharo Enterprise book HTML chapter links

by Sven Van Caekenberghe

Hi, All the Chapter Topics links on https://books.pharo.org/enterprise-pharo/ (bottom left side) are broken. Is it still possible to link to individual chapters ? Can someone have a look, it would be a shame to let this bit rot. Thx, Sven PS: Looking at the other books it seems HTML reading is completely gone, what a shame. This used to work fine.

April 30, 2022

Re: [Pharo-dev] [ANN] Pharo Launcher 3.0.1 released!

by vinref＠gmail.com

Hi This happened to me also on Windows. I killed all running instances of Pharo VM using the TaskManager, then uninstalled the currently installed version, then installed the one I just downloaded. Worked fine after that. Vince

April 30, 2022

Re: Loading from a git repository with Metacello on a running seaside image

by Emilio Oca

Hey, Breaking the ice, by following the logic behind 'Pull' button at 'Working copy of..." from iceberg repo UI, I found I can put this: aRemote := IceGitRemote name: 'origin' url: ' https://github.com/User/MyProject.git'. aRemote localRepository: (IceRepository registry detect: [ :each | each includesPackageNamed: 'MyProject' ]). localBranch := IceGitLocalBranch named: 'refs/heads/main' inRepository: aRemote localRepository. aRemote fetchBranch: localBranch. remoteBranch := aRemote remoteBranchNamed: localBranch name ifAbsent: [ ]. aRemote localRepository workingCopy mergeCommit: remoteBranch commit. under a seaside anchor callback and get the running image self update. I still have to make it work within docker, but it is a start. Thanks all Best Emilio On Fri, Apr 29, 2022 at 8:01 PM Dale Henrichs < dale.henrichs(a)gemtalksystems.com> wrote: > Emilio, > > Okay ... we're peeling the onion :) ... > > At this point it sounds like you need to do a flushCache on your filetree > repository in order to force Metacello to re-download from the github into > the local package-cache. > > But if Iceberg is involved, I am not the person to ask ... I am not > familiar with the changes that have been made to Metacello to get it to > work with Iceberg ... > > Dale > > > > On Fri, Apr 29, 2022 at 3:16 PM Emilio Oca <emiliooca(a)gmail.com> wrote: > >> Hi Dale >> >> Thanks again, still not working. >> After updating github I am unable to pull the changes into the image. >> So far the only way is to hit Pull button at the "Working copy of >> MyProyect" repo window. >> I wish I could reproduce what that button does. >> >> Even this: >> Metacello new >> repository: 'github://...'; >> baseline: 'MyProyect'; >> get >> does not update my file system at iceberg/ >> >> Best >> >> Emilio >> >> On Thu, Apr 28, 2022 at 3:29 PM Dale Henrichs < >> dale.henrichs(a)gemtalksystems.com> wrote: >> >>> Emilio, >>> >>> I wasn't quite sure whether or not you were concerned about having the >>> BaselineOf refreshed or a reload of the packages managed by the BaselineOf >>> and as Gabriel mentions, the missing #projectClass method is the most >>> common problem ... >>> >>> By default Metacello does not refresh a BaselieOf in your image if it is >>> already present, however, you can force a refresh of a BaselineOf by using >>> the the Metcello #get command: >>> >>>> Metacello new baseline:'MyProject'; >>>> repository: 'github://myUser/MyProject:main/myProject'; >>>> get; >>>> load. >>> >>> This would be a good pattern to follow when reloading projects after >>> updating from github ... and I am a bit surprised that this question is not >>> asked more often :) >>> >>> Dale >>> >>> On Mon, Apr 25, 2022 at 6:06 PM Emilio Oca <emiliooca(a)gmail.com> wrote: >>> >>>> Hi Gabriel, Dale! >>>> >>>> My BaselineOf had only #baseline: >>>> Added #projectClass >>>> But is still not working. >>>> It seems to be doing the load, but not the pull before the load. >>>> >>>> I had implemented no more than #baseLine: and now projectClass. >>>> >>>> If I go through the UI and do the pull it works perfectly. >>>> Can I replicate that with a script? >>>> >>>> Best >>>> >>>> Emilio >>>> >>>> On Mon, Apr 25, 2022 at 6:49 PM Dale Henrichs < >>>> dale.henrichs(a)gemtalksystems.com> wrote: >>>> >>>>> Emilio, >>>>> >>>>> Are you using a repository without Monticello meta data? If so, then >>>>> you need to change the #projectClass of you your baseline to: >>>>> >>>>>> projectClass >>>>>> Smalltalk at: #'MetacelloCypressBaselineProject' ifPresent: [ :cl | >>>>>> ^ cl ]. >>>>>> ^ super projectClass >>>>> >>>>> >>>>> unless the #projectClass is MetacelloCypressBaselineProject, Metacello >>>>> will think that your package versions are 'cypress.1' and Metacello will >>>>> not load packages with the same version .... when the #projectClass is >>>>> MetacelloCypressBaselineProject, Metacello will always load the package and >>>>> let Monticello filter out the changes ... >>>>> >>>>> Dale >>>>> >>>>> On Mon, Apr 25, 2022 at 2:39 PM Esteban Lorenzano <estebanlm(a)netc.eu> >>>>> wrote: >>>>> >>>>>> mmm, you may be having another problem elsewhere, because what I >>>>>> typed should be working (is how we enforce the load of new versions to run >>>>>> the tests, for example). >>>>>> >>>>>> Esteban >>>>>> >>>>>> On Apr 25 2022, at 11:30 pm, Emilio Oca <emiliooca(a)gmail.com> wrote: >>>>>> >>>>>> Hi Esteban >>>>>> >>>>>> Thanks for the hint. >>>>>> It is still not working. >>>>>> Even if I remove BaselineOfMyProject and MyProject. >>>>>> When it reloads, it doesn't loads the last version of head at github >>>>>> but the one that was already at the image. >>>>>> >>>>>> I just want to update up to what is at gibhub head. Is there another >>>>>> way? >>>>>> >>>>>> Best >>>>>> >>>>>> Emilio >>>>>> >>>>>> On Sat, Apr 23, 2022 at 1:56 AM Esteban Lorenzano <estebanlm(a)netc.eu> >>>>>> wrote: >>>>>> >>>>>> Hi Emilio, >>>>>> >>>>>> You need something like this: >>>>>> >>>>>> Metacello new >>>>>> repository: 'github://pharo-spec/Spec:Pharo10'; >>>>>> baseline: 'Spec2'; >>>>>> onConflict: [ :e | e useIncoming ]; >>>>>> onUpgrade: [ :e | e useIncoming ]; >>>>>> ignoreImage; >>>>>> load >>>>>> >>>>>> ignoreImage, onConflict, onUpgrade. >>>>>> >>>>>> BUT if your image already has a baseline for your project then >>>>>> Metacello will not reload it (hence your project may not be loaded >>>>>> correctly, since baseline may have changed). >>>>>> >>>>>> In that case, I always execute before something like: >>>>>> >>>>>> #( 'BaselineOfSpec2' 'BaselineOfSpecCore' ) do: [ :each | >>>>>> (RPackageOrganizer default packageNamed: each ifAbsent: [ nil ]) >>>>>> ifNotNil: [ :aPackage | aPackage removeFromSystem ] ] >>>>>> >>>>>> >>>>>> I ack this is hacky, but it works :) >>>>>> >>>>>> Esteban >>>>>> >>>>>> On Apr 23 2022, at 3:21 am, Emilio Oca <emiliooca(a)gmail.com> wrote: >>>>>> >>>>>> Hi List >>>>>> >>>>>> I need some help with Metacello, and may be git too >>>>>> >>>>>> I would like to be able to, in a running headless image, load the >>>>>> last commit of a git repo >>>>>> >>>>>> Something like >>>>>> Metacello new baseline:'MyProject'; >>>>>> repository: 'github://myUser/MyProject:main/myProject'; >>>>>> load. >>>>>> works just once and may open some dialogs >>>>>> >>>>>> Something like this >>>>>> [ >>>>>> [ >>>>>> Metacello new baseline:'MyProject'; >>>>>> repository: 'github://myUser/MyProject:main/myProject'; >>>>>> onConflictUseIncoming; >>>>>> load. >>>>>> ] on: MetacelloSkipDirtyPackageLoad do: [ :ex | ex resume: false ]. >>>>>> ] on: MCMergeOrLoadWarning do: [ :ex | ex load ]. >>>>>> Avoids the dialogs and alerts but the code is still not updated. >>>>>> >>>>>> My intention is to be able to 'refresh' a running seaside image with >>>>>> its latest development version from a git repo (avoiding to personally >>>>>> reach the server and rebuild the docker image) >>>>>> What am I missing? >>>>>> >>>>>> Best >>>>>> >>>>>> Emilio >>>>>> >>>>>>

April 30, 2022

Re: [Pharo-dev] [ANN] Pharo Launcher 3.0.1 released!

by Shaping

PL 3.0.1 is still failing to open on Windows. The VM instance appears in TaskMan. Shaping From: Christophe Demarey <christophe.demarey(a)inria.fr> Sent: Friday, 29 April, 2022 03:50 To: Pharo Development List <pharo-dev(a)lists.pharo.org>; Pharo-users <pharo-users(a)lists.pharo.org> Subject: [Pharo-dev] [ANN] Pharo Launcher 3.0.1 released! Hi all, Pharo Launcher 3.0.1 has just been released! It is available from http://pharo.org/download. It fixes some issues reported on Pharo Launcher 3.0. Here is the changelog: Pharo Launcher v3.0.1 Bug fixes: * #554 <https://github.com/pharo-project/pharo-launcher/issues/554> UI does not show up on Windows * #551 <https://github.com/pharo-project/pharo-launcher/issues/551> Show folder button is broken in Windows 10 * #550 <https://github.com/pharo-project/pharo-launcher/issues/550> About Box shows "untitled Window" * #549 <https://github.com/pharo-project/pharo-launcher/issues/549> Better display of download error messages. * #358 <https://github.com/pharo-project/pharo-launcher/issues/358> Restore proxy authentication settings. Regards, The Pharo team.

April 30, 2022

Re: Loading from a git repository with Metacello on a running seaside image

by Dale Henrichs

Emilio, Okay ... we're peeling the onion :) ... At this point it sounds like you need to do a flushCache on your filetree repository in order to force Metacello to re-download from the github into the local package-cache. But if Iceberg is involved, I am not the person to ask ... I am not familiar with the changes that have been made to Metacello to get it to work with Iceberg ... Dale On Fri, Apr 29, 2022 at 3:16 PM Emilio Oca <emiliooca(a)gmail.com> wrote: > Hi Dale > > Thanks again, still not working. > After updating github I am unable to pull the changes into the image. > So far the only way is to hit Pull button at the "Working copy of > MyProyect" repo window. > I wish I could reproduce what that button does. > > Even this: > Metacello new > repository: 'github://...'; > baseline: 'MyProyect'; > get > does not update my file system at iceberg/ > > Best > > Emilio > > On Thu, Apr 28, 2022 at 3:29 PM Dale Henrichs < > dale.henrichs(a)gemtalksystems.com> wrote: > >> Emilio, >> >> I wasn't quite sure whether or not you were concerned about having the >> BaselineOf refreshed or a reload of the packages managed by the BaselineOf >> and as Gabriel mentions, the missing #projectClass method is the most >> common problem ... >> >> By default Metacello does not refresh a BaselieOf in your image if it is >> already present, however, you can force a refresh of a BaselineOf by using >> the the Metcello #get command: >> >>> Metacello new baseline:'MyProject'; >>> repository: 'github://myUser/MyProject:main/myProject'; >>> get; >>> load. >> >> This would be a good pattern to follow when reloading projects after >> updating from github ... and I am a bit surprised that this question is not >> asked more often :) >> >> Dale >> >> On Mon, Apr 25, 2022 at 6:06 PM Emilio Oca <emiliooca(a)gmail.com> wrote: >> >>> Hi Gabriel, Dale! >>> >>> My BaselineOf had only #baseline: >>> Added #projectClass >>> But is still not working. >>> It seems to be doing the load, but not the pull before the load. >>> >>> I had implemented no more than #baseLine: and now projectClass. >>> >>> If I go through the UI and do the pull it works perfectly. >>> Can I replicate that with a script? >>> >>> Best >>> >>> Emilio >>> >>> On Mon, Apr 25, 2022 at 6:49 PM Dale Henrichs < >>> dale.henrichs(a)gemtalksystems.com> wrote: >>> >>>> Emilio, >>>> >>>> Are you using a repository without Monticello meta data? If so, then >>>> you need to change the #projectClass of you your baseline to: >>>> >>>>> projectClass >>>>> Smalltalk at: #'MetacelloCypressBaselineProject' ifPresent: [ :cl | >>>>> ^ cl ]. >>>>> ^ super projectClass >>>> >>>> >>>> unless the #projectClass is MetacelloCypressBaselineProject, Metacello >>>> will think that your package versions are 'cypress.1' and Metacello will >>>> not load packages with the same version .... when the #projectClass is >>>> MetacelloCypressBaselineProject, Metacello will always load the package and >>>> let Monticello filter out the changes ... >>>> >>>> Dale >>>> >>>> On Mon, Apr 25, 2022 at 2:39 PM Esteban Lorenzano <estebanlm(a)netc.eu> >>>> wrote: >>>> >>>>> mmm, you may be having another problem elsewhere, because what I typed >>>>> should be working (is how we enforce the load of new versions to run the >>>>> tests, for example). >>>>> >>>>> Esteban >>>>> >>>>> On Apr 25 2022, at 11:30 pm, Emilio Oca <emiliooca(a)gmail.com> wrote: >>>>> >>>>> Hi Esteban >>>>> >>>>> Thanks for the hint. >>>>> It is still not working. >>>>> Even if I remove BaselineOfMyProject and MyProject. >>>>> When it reloads, it doesn't loads the last version of head at github >>>>> but the one that was already at the image. >>>>> >>>>> I just want to update up to what is at gibhub head. Is there another >>>>> way? >>>>> >>>>> Best >>>>> >>>>> Emilio >>>>> >>>>> On Sat, Apr 23, 2022 at 1:56 AM Esteban Lorenzano <estebanlm(a)netc.eu> >>>>> wrote: >>>>> >>>>> Hi Emilio, >>>>> >>>>> You need something like this: >>>>> >>>>> Metacello new >>>>> repository: 'github://pharo-spec/Spec:Pharo10'; >>>>> baseline: 'Spec2'; >>>>> onConflict: [ :e | e useIncoming ]; >>>>> onUpgrade: [ :e | e useIncoming ]; >>>>> ignoreImage; >>>>> load >>>>> >>>>> ignoreImage, onConflict, onUpgrade. >>>>> >>>>> BUT if your image already has a baseline for your project then >>>>> Metacello will not reload it (hence your project may not be loaded >>>>> correctly, since baseline may have changed). >>>>> >>>>> In that case, I always execute before something like: >>>>> >>>>> #( 'BaselineOfSpec2' 'BaselineOfSpecCore' ) do: [ :each | >>>>> (RPackageOrganizer default packageNamed: each ifAbsent: [ nil ]) >>>>> ifNotNil: [ :aPackage | aPackage removeFromSystem ] ] >>>>> >>>>> >>>>> I ack this is hacky, but it works :) >>>>> >>>>> Esteban >>>>> >>>>> On Apr 23 2022, at 3:21 am, Emilio Oca <emiliooca(a)gmail.com> wrote: >>>>> >>>>> Hi List >>>>> >>>>> I need some help with Metacello, and may be git too >>>>> >>>>> I would like to be able to, in a running headless image, load the last >>>>> commit of a git repo >>>>> >>>>> Something like >>>>> Metacello new baseline:'MyProject'; >>>>> repository: 'github://myUser/MyProject:main/myProject'; >>>>> load. >>>>> works just once and may open some dialogs >>>>> >>>>> Something like this >>>>> [ >>>>> [ >>>>> Metacello new baseline:'MyProject'; >>>>> repository: 'github://myUser/MyProject:main/myProject'; >>>>> onConflictUseIncoming; >>>>> load. >>>>> ] on: MetacelloSkipDirtyPackageLoad do: [ :ex | ex resume: false ]. >>>>> ] on: MCMergeOrLoadWarning do: [ :ex | ex load ]. >>>>> Avoids the dialogs and alerts but the code is still not updated. >>>>> >>>>> My intention is to be able to 'refresh' a running seaside image with >>>>> its latest development version from a git repo (avoiding to personally >>>>> reach the server and rebuild the docker image) >>>>> What am I missing? >>>>> >>>>> Best >>>>> >>>>> Emilio >>>>> >>>>>

April 29, 2022

Re: Loading from a git repository with Metacello on a running seaside image

by Emilio Oca

Hi Dale Thanks again, still not working. After updating github I am unable to pull the changes into the image. So far the only way is to hit Pull button at the "Working copy of MyProyect" repo window. I wish I could reproduce what that button does. Even this: Metacello new repository: 'github://...'; baseline: 'MyProyect'; get does not update my file system at iceberg/ Best Emilio On Thu, Apr 28, 2022 at 3:29 PM Dale Henrichs < dale.henrichs(a)gemtalksystems.com> wrote: > Emilio, > > I wasn't quite sure whether or not you were concerned about having the > BaselineOf refreshed or a reload of the packages managed by the BaselineOf > and as Gabriel mentions, the missing #projectClass method is the most > common problem ... > > By default Metacello does not refresh a BaselieOf in your image if it is > already present, however, you can force a refresh of a BaselineOf by using > the the Metcello #get command: > >> Metacello new baseline:'MyProject'; >> repository: 'github://myUser/MyProject:main/myProject'; >> get; >> load. > > This would be a good pattern to follow when reloading projects after > updating from github ... and I am a bit surprised that this question is not > asked more often :) > > Dale > > On Mon, Apr 25, 2022 at 6:06 PM Emilio Oca <emiliooca(a)gmail.com> wrote: > >> Hi Gabriel, Dale! >> >> My BaselineOf had only #baseline: >> Added #projectClass >> But is still not working. >> It seems to be doing the load, but not the pull before the load. >> >> I had implemented no more than #baseLine: and now projectClass. >> >> If I go through the UI and do the pull it works perfectly. >> Can I replicate that with a script? >> >> Best >> >> Emilio >> >> On Mon, Apr 25, 2022 at 6:49 PM Dale Henrichs < >> dale.henrichs(a)gemtalksystems.com> wrote: >> >>> Emilio, >>> >>> Are you using a repository without Monticello meta data? If so, then you >>> need to change the #projectClass of you your baseline to: >>> >>>> projectClass >>>> Smalltalk at: #'MetacelloCypressBaselineProject' ifPresent: [ :cl | ^ >>>> cl ]. >>>> ^ super projectClass >>> >>> >>> unless the #projectClass is MetacelloCypressBaselineProject, Metacello >>> will think that your package versions are 'cypress.1' and Metacello will >>> not load packages with the same version .... when the #projectClass is >>> MetacelloCypressBaselineProject, Metacello will always load the package and >>> let Monticello filter out the changes ... >>> >>> Dale >>> >>> On Mon, Apr 25, 2022 at 2:39 PM Esteban Lorenzano <estebanlm(a)netc.eu> >>> wrote: >>> >>>> mmm, you may be having another problem elsewhere, because what I typed >>>> should be working (is how we enforce the load of new versions to run the >>>> tests, for example). >>>> >>>> Esteban >>>> >>>> On Apr 25 2022, at 11:30 pm, Emilio Oca <emiliooca(a)gmail.com> wrote: >>>> >>>> Hi Esteban >>>> >>>> Thanks for the hint. >>>> It is still not working. >>>> Even if I remove BaselineOfMyProject and MyProject. >>>> When it reloads, it doesn't loads the last version of head at github >>>> but the one that was already at the image. >>>> >>>> I just want to update up to what is at gibhub head. Is there another >>>> way? >>>> >>>> Best >>>> >>>> Emilio >>>> >>>> On Sat, Apr 23, 2022 at 1:56 AM Esteban Lorenzano <estebanlm(a)netc.eu> >>>> wrote: >>>> >>>> Hi Emilio, >>>> >>>> You need something like this: >>>> >>>> Metacello new >>>> repository: 'github://pharo-spec/Spec:Pharo10'; >>>> baseline: 'Spec2'; >>>> onConflict: [ :e | e useIncoming ]; >>>> onUpgrade: [ :e | e useIncoming ]; >>>> ignoreImage; >>>> load >>>> >>>> ignoreImage, onConflict, onUpgrade. >>>> >>>> BUT if your image already has a baseline for your project then >>>> Metacello will not reload it (hence your project may not be loaded >>>> correctly, since baseline may have changed). >>>> >>>> In that case, I always execute before something like: >>>> >>>> #( 'BaselineOfSpec2' 'BaselineOfSpecCore' ) do: [ :each | >>>> (RPackageOrganizer default packageNamed: each ifAbsent: [ nil ]) >>>> ifNotNil: [ :aPackage | aPackage removeFromSystem ] ] >>>> >>>> >>>> I ack this is hacky, but it works :) >>>> >>>> Esteban >>>> >>>> On Apr 23 2022, at 3:21 am, Emilio Oca <emiliooca(a)gmail.com> wrote: >>>> >>>> Hi List >>>> >>>> I need some help with Metacello, and may be git too >>>> >>>> I would like to be able to, in a running headless image, load the last >>>> commit of a git repo >>>> >>>> Something like >>>> Metacello new baseline:'MyProject'; >>>> repository: 'github://myUser/MyProject:main/myProject'; >>>> load. >>>> works just once and may open some dialogs >>>> >>>> Something like this >>>> [ >>>> [ >>>> Metacello new baseline:'MyProject'; >>>> repository: 'github://myUser/MyProject:main/myProject'; >>>> onConflictUseIncoming; >>>> load. >>>> ] on: MetacelloSkipDirtyPackageLoad do: [ :ex | ex resume: false ]. >>>> ] on: MCMergeOrLoadWarning do: [ :ex | ex load ]. >>>> Avoids the dialogs and alerts but the code is still not updated. >>>> >>>> My intention is to be able to 'refresh' a running seaside image with >>>> its latest development version from a git repo (avoiding to personally >>>> reach the server and rebuild the docker image) >>>> What am I missing? >>>> >>>> Best >>>> >>>> Emilio >>>> >>>>

April 29, 2022

Re: A question about #beginsWith: and #endsWith:

by Kasper Osterbye

The two methods are changed to do the right thing. We are still waiting for the CI server to check if that broke anything. During the change, 4 places was identified which was simplified by doing it right (aka empty prefix always true). Best, Kasper

April 29, 2022

Re: A question about #beginsWith: and #endsWith:

by Richard Sargent

Making the code correct is "untwisting the rope". Keeping the code wrong and adding a bizarre workaround is "twisting the rope tighter". The former is the right direction. On Fri, Apr 29, 2022 at 12:15 AM Steffen MÃ¤rcker <merkste(a)web.de> wrote: > Hi Kasper, > > I've thought about that approach too. But then asked myself whether it is > more likely that there is code that relies on this bug than code where this > went unnoticed and is therefore broken. What do the other think about that > matter and the fix in Squeak? > > Best, Steffen > > > > > Kasper Osterbye schrieb am Donnerstag, 28. April 2022 19:03:07 (+02:00): > > Kasper Osterbye schrieb am Dienstag, 26. April 2022 14:50:51 (+02:00): > > I have now raised it as an issue on the issue tracker > > Issue #11165 <https://github.com/pharo-project/pharo/issues/11165> in > https://github.com/pharo-project/pharo/issues/11165 > > > If I may suggest a solution it will be to: > > - add two new methods - *prefixedBy: * and *suffixedBy:* to handle the > empty prefix/suffix correctly > - add comments to *beginsWith: * and *endsWith: * referring to the two > new methods > > > The problem is that there is client code which depend on the (wrong) > implementation of the beginsWith and endsWith methods. > > >

April 29, 2022

Re: [Pharo-dev] [ANN] Pharo Launcher 3.0 released!

by Christophe Demarey

Hi Jimmie, Thank you for your feedback. Could you open a feature request on https://github.com/pharo-project/pharo-launcher/issues <https://github.com/pharo-project/pharo-launcher/issues> ? Regards, Christophe > Le 29 avr. 2022 Ã 11:23, Jimmie Houchin <jlhouchin(a)gmail.com> a Ã©crit : > > Hello, > > Thanks for all your work. I have only recently started using Pharo Launcher. I have been using Pharo a long time and was very accustomed to managing my own images. So I am still learning. It is nice to work with and it is nice to easily have whichever vm or image you are wanting to start with. > > However I would like one thing if possible. The advantage I had when managing my own and I can do a combination. Is that I always started a new terminal and then opened up Pharo and whichever image I wanted. This makes it neat and clean when running multiple images like I do, to have clean messaging and clean stdio when I write to stdio. With Pharo Launcher all stdio goes to its terminal and from whichever image has been started. I don't know how difficult this would be. But it would be nice if they were an option for Pharo Launcher to startup the new image from its own new terminal. Just an idea. > > Again. Thanks for all the work you do. > > Jimmie > > > > On 4/14/22 07:26, Christophe Demarey wrote: >> Hi all, >> >> Pharo Launcher 3.0 has just been released! It is available from http://pharo.org/download <http://pharo.org/download>. >> It is based on latest Spec2 and Pharo 10 image. >> It now comes with a native Apple Silicon version and Mac OS packages are notarized. >> Big thanks to all contributors, including issue reports. >> >> Here is the changelog: >> Pharo Launcher v3.0 >> New features: >> >> Full rewrite of the UI using Spec 2 and Pharo 10 >> Pharo Launcher can now run natively on Apple Silicon #544 <https://github.com/pharo-project/pharo-launcher/issues/544> >> Pharo Launcher is now signed with a Mac Os developper account and notarized #529 <https://github.com/pharo-project/pharo-launcher/issues/529> >> Windows "portable" package (only an archive without installer) #534 <https://github.com/pharo-project/pharo-launcher/issues/534> >> Improvements: >> >> While importing image .sources and .version are not moved #543 <https://github.com/pharo-project/pharo-launcher/issues/543> >> recreate the image does not re apply the script if one is provided #536 <https://github.com/pharo-project/pharo-launcher/issues/536> (thanks to @hogoww <https://github.com/hogoww>) >> Save keybind for scripts #545 <https://github.com/pharo-project/pharo-launcher/pull/545> (thanks to @hogoww <https://github.com/hogoww> and @Inao0 <https://github.com/Inao0>) >> Bug fixes: >> >> GitHub releases artefacts download were not always working #535 <https://github.com/pharo-project/pharo-launcher/issues/535> >> "Basic launch" does not do its job in Pharo 10 #540 <https://github.com/pharo-project/pharo-launcher/issues/540> >> Proxy settings not applied through settings screen #541 <https://github.com/pharo-project/pharo-launcher/issues/541> >> >> Regards, >> The Pharo team.

April 29, 2022

Re: A question about #beginsWith: and #endsWith:

by Richard O'Keefe

I like proverbs. One of mine is "zero is also a number." Way back in the 1980s the University in my home town was given a new IBM mainframe by IBM. The Computer Centre wrote a archival program for it that scanned each user's minidisk (= fixed partition) for files that had not been used for a while and logged them to a master file, then ran a job that moved the files to a tape. One day everything went horribly wrong. It turned out that the reason was very simple, but so alien that nobody had noticed when they read the documentation. It was the kind of thing that was so unbelievable you couldn't even *see* it when it was hinted at in front of you. Consider the following process: (1) create-or-replace a file. (2) write N records to it. (3) close the file. Simple. Obvious. And wrong. Because step (1) didn't actually *happen* until step (3), and if N = 0, it didn't happen then either. In that IBM mainframe operating system, you literally could not create an empty file. So when one day there weren't any files that needed moving to tape (because they had all been done the previous day), the process that was expected to write an empty list of files simply left the previous day's list unchanged. Result: thousands of multipage error reports when the archiver tried to move files that weren't there any more. All because someone at IBM had not been able to conceive of a file with no records! I hope the analogy is clear. But it gets better. If you wrote a file in C on that system, it was in effect line-buffered. Your text got written to the file when (and only when) you wrote a newline character. So if you imitated common MS-DOS practice and *began* lines with a newline, the last line of your file would never be written out. The equivalent of s := FileStream write: 'foo text a'. s nextPutAll: 'Hello world!'. s close. would write no records, and thus not create or replace the file. (Because a file with N = 0 newline characters is another of those N = 0 things that cannot exist!) I had to redesign the I/O library for a certain programming language that ran on a lot of Unix systems, on VAX/VMS, and we *thought* was running well through the C library on IBM mainframes. All sorts of finicky little details to deal with N=0. So at the end of a file, if nothing had been written, we wrote an empty record, unless you turned that option off. At the end of each record, if nothing had been written, we wrote a space. Yes, that N = 0 case was another problem. It has been over 30 years since I had anything to do with IBM mainframes, but some experiences leave scars. I note that in Pharo 9.0, there is a subtle difference between SequenceableCollection>>copyReplaceAll:with: and String>>copyReplaceAll:with: and the latter is not consistent with itself. Let x and y be Strings. x copyReplaceAll: '' with: y is always x, except when x is empty, in which case it is y. Let x and y be Arrays. x copyReplaceAll: #() with: y is always x. This is not the subtle difference I mentioned above. *That* difference is that the string version takes linear time (assuming fast search) while the general version takes quadratic time (also assuming fast search). The ANSI specification for #copyReplaceAll:with: is quite clear: Answer a new collection with the elements of the receiver in their original order, except where a subsequence in the receiver matches targetElements. A subsequence in the receiver is said to match the elements of targetElements if: 1. They have the same number of elements. 2. For all indices of the subsequence, the element in the subsequence at a given index is equivalent to the element in targetElements at the same index. By this definition, an empty sequence has matches in any sequence. I'm not advancing this as evidence that I'm right about #beginsWith: and #endsWith:, because the following text in the standard makes it clear that for some reason, empty sequences were literally UNTHINKABLE for the framers of the ANSI Smalltalk standard, at least in the context of search. I'm mentioning it as evidence that for many people, zero is the hardest number to think of. I've finally realised why some people stubbornly cling to the idea that the natural numbers begin with 1, not zero (as if the Peano axioms are not a thing). If you are thinking of the natural numbers in terms of *multiplication* (and primes, and so on), well, the positive integers are a cancellative monoid with identity 1, but not if you include 0. If you are thinking of the natural numbers in terms of *addition*, then the non-negative integers are a cancellative monoid with identity 0. So there are two *different* monoids, for one of which including 0 would be many kinds of trouble, and for the other of which excluding 0 would be absurd and awkward. Strings are cancellative monoids under concatenation with '' as the identity. (Don't ask me about Unicode.) So why is '' so hard to think about? I don't think it is just Strings. In functional programming, it was surprisingly hard to teach students to remember the empty list. (For myself, I got into the habit of writing the base case of a recursive function *first* to avoid the mistake of leaving out the base case.) I suspect that there are other places with surprising behaviour for 'trivial' cases. On Fri, 29 Apr 2022 at 13:35, David T. Lewis <lewis(a)mail.msen.com> wrote: > FYI it was fixed in Squeak a couple of days ago: > > > http://lists.squeakfoundation.org/pipermail/squeak-dev/2022-April/220089.ht… > > Richard O'Keefe's point of view was overwhelmingly supported, notably > including this post: > > > http://lists.squeakfoundation.org/pipermail/squeak-dev/2022-April/220038.ht… > > Dave > > On Sat, Apr 23, 2022 at 12:37:48PM +1200, Richard O'Keefe wrote: > > Dan Ingalls is of course a big NAME in the > > world of Smalltalk, but the stated reason > > for changing the behaviour of #beginsWith: > > and #endsWith: makes no sense. > > > > > > We have many ways to define a partial order > > on strings. > > x <= y iff y beginsWith: x > > x <= y iff y endsWith: x > > x <= y iff y includesSubCollection: x > > x <= y iff y includesSubSequence: x > > These things are supposed to obey laws: > > if a beginsWith: b , c > > then a beginsWith: b > > if a endsWith: b , c > > then a endsWith: c > > if a includesSubCollection: b , c > > then a includesSubCollection: b > > and a includesSubCollection: c > > if a includesSubSequence: b , c > > then a includesSubSequence: b > > and a includesSubSequence: c. > > > > We also expect the usual rules of equality > > to hold. So > > (1) a beginsWith: a > > (2) a = '' , a > > (3) THEREFORE a beginsWith: '' > > > > (1) a endsWith: a > > (2) a = a , '' > > (3) THEREFORE a endsWith: '' > > > > (1) a includesSubCollection: a > > (2) a = '' , a > > (3) THEREFORE a includesSubCollect: '' > > > > Reasoning about strings (as values) gets > > enormously more complicated if the operations > > do not follow simple sensible rules, and > > having '' be the least string under these > > orderings and having '' be a prefix and a > > suffix of any string is essential if the > > rules are going to be simple and coherent. > > > > '' is to strings (and more generally > > empty sequences are to sequences) pretty > > much what 0 is to integers. Denying that > > 'abc' beginsWith: '' is *structurally* > > just like denying that 0 <= 123. > > > > Now as it happens I *can* see a use for > > versions of #beginsWith: and #endsWith: > > that diverge from the ones we have, but > > *this* is not where they need to diverge. > > a beginsWithGraphemesOf: b > > iff a asGraphemes = b asGraphemes , c asGraphemes > > for some c, where s asGraphemes returns a > > sequence of strings each of which is a maximally > > long grapheme cluster, such that concatenating > > s asGraphemes recovers s. That is, > > #beginsWithGraphemesOf: and > > #endsWithGraphemesOf: would respect the > > Unicode Text Segmentation boundaries. > > But s beginsWithGraphemesOf: '' > > would still need to be true. > > > > The thing is, in practice you often DON'T > > KNOW whether a potential affix is empty or > > not. Here are some of my test cases. > > > > testTestData > > "Ensure that the sample string has no duplicates." > > [(Set withAll: string) size = stringSize] assert. > > > > testBeginsWith > > "Test that every prefix of the sample IS a prefix of it." > > 0 to: stringSize do: [:n | > > [string beginsWith: (string copyFrom: 1 to: n)] assert]. > > > > testEndsWith > > "Test that every suffix of the sample IS a suffix of it." > > 0 to: stringSize do: [:n | > > [string endsWith: (string copyFrom: stringSize - n + 1 to: > > stringSize)] assert]. > > > > testIndexOfSubCollectionAtBeginning > > "Test that every prefix of 'abcd' is found at the beginning." > > 0 to: stringSize do: [:n | |s i t| > > s := string copyFrom: 1 to: n. > > i := string indexOfSubCollection: s startingAt: 1. > > [1 = i] assert. > > t := string copyFrom: i to: i - 1 + n. > > [t = s] assert]. > > > > testIndexOfSubCollectionAtEnd > > "Test that every proper suffix of the sample is found at the end." > > 1 to: stringSize do: [:n | |s i t| > > s := string copyFrom: stringSize - n + 1 to: stringSize. > > i := string indexOfSubCollection: s startingAt: 1. > > [stringSize + 1 - n = i] assert. > > t := string copyFrom: i to: i - 1 + n. > > [t = s] assert]. > > > > testLastIndexOfSubCollectionAtBeginning > > "Test that every proper prefix of the sample is found at the > > beginning." > > 1 to: stringSize do: [:n | |s i t| > > s := string copyFrom: 1 to: n. > > i := string lastIndexOfSubCollection: s startingAt: stringSize. > > [1 = i] assert. > > t := string copyFrom: i to: i - 1 + n. > > [t = s] assert]. > > > > testLastIndexOfSubCollectionAtEnd > > "Test that every suffix of the sample is found at the end." > > 0 to: stringSize do: [:n | |s i t| > > s := string copyFrom: stringSize - n + 1 to: stringSize. > > i := string lastIndexOfSubCollection: s startingAt: stringSize. > > [stringSize + 1 - n = i] assert. > > t := string copyFrom: i to: i - 1 + n. > > [t = s] assert]. > > > > testOccurrencesOfEmptyCollection > > "Test that the empty string occurs at the beginning, > > at the end, and in between every pair of adjacent characters." > > [(string occurrencesOfSubCollection: '') = (stringSize + 1)] > assert. > > > > testOccurrencesOfUniqueParts > > "Test that unique parts occur as many times as they should." > > |repeated| > > repeated := string , string , string. > > 1 to: stringSize do: [:start | > > start to: stringSize do: [:finish | |s n| > > s := string copyFrom: start to: finish. > > n := string occurrencesOfSubCollection: s. > > [n = 1] assert. > > n := repeated occurrencesOfSubCollection: s. > > [n = 3] assert]]. > > > > On Fri, 22 Apr 2022 at 13:57, David T. Lewis <lewis(a)mail.msen.com> > wrote: > > > > > Hi Richard, > > > > > > (CC squeak-dev list, replies to the relevant list please) > > > > > > On Thu, Apr 21, 2022 at 12:07:32AM +1200, Richard O'Keefe wrote: > > > > I've just tracked down a nasty little problem > > > > porting some code to Pharo. As a result, I > > > > have added to the comments in my own versions > > > > of these methods. beginsWith: aSequence > > > > "Answer true if aSequence is a prefix of the receiver. > > > > This makes sense for all sequences. > > > > There is a compatibility issue concerning 'abc' beginsWith: '' > > > > + VisualWorks, Dolphin, astc, GNU ST (where the method is > > > > called #startsWith:) and VisualAge (where the method > > > > is called #wbBeginsWith:) > > > > agree than EVERY sequence begins with an empty prefix. > > > > - Squeak and Pharo > > > > agree that NO sequence begins with an empty sequence. > > > > # ST/X chooses compatibility with Squeak, heaving a big > unhappy > > > > sigh, and adds #startsWith: to have something sensible to > use. > > > > Now ST/X *thinks* it is compatible with VW, though it isn't, > so > > > > I wonder if this was a bug that VW fixed and Squeak didn't? > > > > astc goes with the majority here. This is also compatible > with > > > > Haskell, ML, and with StartsWith in C# and startsWith in > Java." > > > > ^self beginsWith: aSequence ignoringCase: false > > > > > > > > endsWith: aSequence > > > > "Answer true if aSequence is a suffix of the receiver. > > > > This makes sense for all sequences. > > > > There is a compatibility issue concerning 'abc' endsWith: ''. > > > > + VisualWorks, Dolphin, astc, GNU ST, and VisualAge (where > > > > the method is called #wbEndsWith:) > > > > agree that EVERY sequence ends with an empty suffix. > > > > - Squeak and Pharo > > > > agree that NO sequence ends with an empty suffix. > > > > # ST/X chooses compatibility with the majority, apparently > > > > unaware that this makes #beginsWith: and #endsWith: > > > inconsistent. > > > > astc goes with the majority here. This is also compatible > with > > > > Haskell, ML, C#, and Java." > > > > ^self endsWith: aSequence ignoringCase: false > > > > > > > > Does anyone have any idea > > > > - why Squeak and Pharo are the odd ones out? > > > > - why anyone thought making #beginsWith: and #endsWith:, um, > "quirky" > > > > was a good idea (it's pretty standard in books on the theory of > > > > strings to define "x is a prefix of y iff there is a z such that > > > > y = x concatenated with z") > > > > > > The Squeak behavior was introduced in November 1998 by Dan Ingalls > > > in conjunction with some VM improvements that he was doing, and was > > > included in the Squeak2.2 release at that time. > > > > > > Prior to that update, Squeak did this: > > > 'abc' beginsWith: '' ==> true > > > 'abc' endsWith: '' ==> true > > > > > > For Squeak2.2 and later it is: > > > 'abc' beginsWith: '' ==> false > > > 'abc' endsWith: '' ==> false > > > > > > Pharo presumably inherits this from Squeak. > > > > > > I am attaching Dan's original change set from the early Squeak > > > update stream so you can see the context. > > > > > > The change set comment says that "endsWith:, beginsWith:, and match > > > have been rewritten to take advantage of this considerably faster > method" > > > (referring to a new primitive that Dan had added to the VM in this > > > change set). > > > > > > > > > > > I was about to try to file a bug report for the first time, > > > > then realised that maybe other people don't think this IS a bug. > > > > > > I don't think it is a bug. I can't think of a case where it makes > > > sense to say that a string of characters "begins with" or "ends with" > > > a string that contains nothing. > > > > > > In any case, that's the history of the change in Squeak and Pharo as > > > best as I can reconstruct it. > > > > > > HTH, > > > Dave > > > > > > >

April 29, 2022