February 2022 - Pharo-users

Re: Too many parenthesis - a matter of syntax

by Richard O'Keefe

The fact that there is more than you want is precisely why you want to make classes for the data you *do* want. I do have kit for streaming JSON out directly without creating JSON data internally, but I'm still trying to find a good way to stream JSON in creating wanted objects on-the-fly so that the unwanted data are never stored. I think it can be done from the same schema language that I use to generate classes. On Mon, 28 Feb 2022 at 20:09, Kasper Osterbye <kasper.osterbye(a)gmail.com> wrote: > Thanks Richard, > > I tend to agree with your design experience. As it happens, in my concrete > code I get JSON back from a github api which serves me more than I want. I > am therefore not interested in making classes for those aspects of the data > I throw out. > > The way I handle this in practice myself is to introduce a local variable > for each level. Makes it easier to debug too. > > Best, > > Kasper > > On 27 Feb 2022, at 00.42, Richard O'Keefe <raoknz(a)gmail.com> wrote: > > I was bemused to realise that I've actually been programming > for literally 50 years. It finally seeped through my thick > skull I make enough mistakes that if it's hard to read, I > probably got it wrong. And THIS code fragment is hard to > read. I don't care if you use parentheses or pipes, it's > hard to read either way. Oh, the pipes make the structure > easier to see, true. But I am still left guessing what it > is FOR. What's it SUPPOSED to mean? And the problem is that > there are some abstractions missing. Of course this is JSON's > fault. > > This is the first code smell, and in my experience it is > almost ALWAYS a code smell: you are using JSON as a > "processing" data structure instead of as a "communication" > syntax. Using JSON inside your program, instead of at the > edges, means that the semantics gets scattered all over the > code, which leads to complexity and inconsistency. > > The convention I follow is that data structure more complicated > than a string or an array of numbers has a Smalltalk class > Whatsit>>asJson converts an instance to a JSON value > Whatsit class>>fromJson: converts a JSON value to an instance. > I'll start with > topLevel := TopLevelWhatsit fromJson: someStream nextJson. > and from then on I'm working with pure Smalltalk. > > This has the extra benefit of validating the input right away. > I don't want my program running for several hours and then > running into trouble because some component of the JSON value > is missing or ill-formed. > > In practice, the time cost of converting JSON to (application- > specific) Smalltalk is quite small compared with the cost of > reading the JSON in the first place, and there can be seriously > worthwhile savings in memory. > > For this example, we'd be looking at > topLevel tree blobs > collect: [:each | each path] > thenSelect: [:path | path hasAnyExtension: #('md' 'mic')] > > My Filename class has methods > has[Any]Extension:[ignoringCase:] > which I have shamelessly exploited here. I like the > way that they hide the structure of a Filename. > > The portmanteau methods > Collection>>collect:thenSelect: > Collection>>select:thenCollect: > have existed in Pharo as long as Pharo has existed. > They have two rationales: > (a) improve readability > (b) permit optimisation by eliminating an intermediate collection. > Sequences exploit (b). Sets could too but happen not to. > > THEREFORE, here are free implementations of > Set>>collect:thenSelect: and Set>>select:thenCollect: > consistent with Pharo's Set>>collect: > > collect: collectBlock thenSelect: selectBlock > "Override Collection>>collect:thenSelect: like OrderedCollection. > Beware: 'self species' is often inappropriate, as in #collect:." > |newSet| > newSet := self species new: self size. > self do: [:each | > |item| > item := collectBlock value: each. > (selectBlock value: each) ifTrue: [newSet add: item]]. > ^newSet > > select: selectBlock thenCollect: collectBlock > "Override Collection>>select:thenCollect: like OrderedCollection. > Beware: 'self species' is often inappropriate, as in #collect:." > |newSet| > newSet := self species new: self size. > self do: [:each | > (selectBlock value: each) ifTrue: [ > newSet add: (collectBlock value: each)]]. > ^newSet > > > > On Wed, 26 Jan 2022 at 22:19, Kasper Osterbye <kasper.osterbye(a)gmail.com> > wrote: > >> Cheers all >> >> I have noticed that I often ends up with quite a number of nested >> expressions, for example: >> >> (((json at: 'tree') >> select: [ :e | (e at: 'type') = âblob' ]) >> collect: [:e | Path from: (e at: 'path')]) >> select: [ :p | p segments last >> in: [ :name | (name endsWith: '.md') | >> (name endsWith: '.mic') ] ] >> >> What kind of proposals (if any) have been for a different syntax which >> could give a more streamlined syntax? >> >> My own thinking has been around an alternative to the cascade semicolon. >> What symbol to use does not matter for me, but something like >> json at: âtree' Âº >> select: [ :e | ((e at: 'type') = 'blobâ)]Âº >> collect: [:e | Path from: (e at: 'pathâ)]Âº >> select: [ :p | p segments last >> in: [ :name | (name endsWith: '.md') | (name endsWith: >> '.mic') ] ] >> >> Basically, a send the right hand expression to the result of the left >> hand expression. >> >> Has anyone ever tried this, or is it just one of the many small >> annoyances best left alone? >> >> Best, >> >> Kasper > > >

Feb. 28, 2022

Re: Too many parenthesis - a matter of syntax

by Kasper Osterbye

Thanks Richard, I tend to agree with your design experience. As it happens, in my concrete code I get JSON back from a github api which serves me more than I want. I am therefore not interested in making classes for those aspects of the data I throw out. The way I handle this in practice myself is to introduce a local variable for each level. Makes it easier to debug too. Best, Kasper > On 27 Feb 2022, at 00.42, Richard O'Keefe <raoknz(a)gmail.com> wrote: > > I was bemused to realise that I've actually been programming > for literally 50 years. It finally seeped through my thick > skull I make enough mistakes that if it's hard to read, I > probably got it wrong. And THIS code fragment is hard to > read. I don't care if you use parentheses or pipes, it's > hard to read either way. Oh, the pipes make the structure > easier to see, true. But I am still left guessing what it > is FOR. What's it SUPPOSED to mean? And the problem is that > there are some abstractions missing. Of course this is JSON's > fault. > > This is the first code smell, and in my experience it is > almost ALWAYS a code smell: you are using JSON as a > "processing" data structure instead of as a "communication" > syntax. Using JSON inside your program, instead of at the > edges, means that the semantics gets scattered all over the > code, which leads to complexity and inconsistency. > > The convention I follow is that data structure more complicated > than a string or an array of numbers has a Smalltalk class > Whatsit>>asJson converts an instance to a JSON value > Whatsit class>>fromJson: converts a JSON value to an instance. > I'll start with > topLevel := TopLevelWhatsit fromJson: someStream nextJson. > and from then on I'm working with pure Smalltalk. > > This has the extra benefit of validating the input right away. > I don't want my program running for several hours and then > running into trouble because some component of the JSON value > is missing or ill-formed. > > In practice, the time cost of converting JSON to (application- > specific) Smalltalk is quite small compared with the cost of > reading the JSON in the first place, and there can be seriously > worthwhile savings in memory. > > For this example, we'd be looking at > topLevel tree blobs > collect: [:each | each path] > thenSelect: [:path | path hasAnyExtension: #('md' 'mic')] > > My Filename class has methods > has[Any]Extension:[ignoringCase:] > which I have shamelessly exploited here. I like the > way that they hide the structure of a Filename. > > The portmanteau methods > Collection>>collect:thenSelect: > Collection>>select:thenCollect: > have existed in Pharo as long as Pharo has existed. > They have two rationales: > (a) improve readability > (b) permit optimisation by eliminating an intermediate collection. > Sequences exploit (b). Sets could too but happen not to. > > THEREFORE, here are free implementations of > Set>>collect:thenSelect: and Set>>select:thenCollect: > consistent with Pharo's Set>>collect: > > collect: collectBlock thenSelect: selectBlock > "Override Collection>>collect:thenSelect: like OrderedCollection. > Beware: 'self species' is often inappropriate, as in #collect:." > |newSet| > newSet := self species new: self size. > self do: [:each | > |item| > item := collectBlock value: each. > (selectBlock value: each) ifTrue: [newSet add: item]]. > ^newSet > > select: selectBlock thenCollect: collectBlock > "Override Collection>>select:thenCollect: like OrderedCollection. > Beware: 'self species' is often inappropriate, as in #collect:." > |newSet| > newSet := self species new: self size. > self do: [:each | > (selectBlock value: each) ifTrue: [ > newSet add: (collectBlock value: each)]]. > ^newSet > > > > On Wed, 26 Jan 2022 at 22:19, Kasper Osterbye <kasper.osterbye(a)gmail.com <mailto:kasper.osterbye@gmail.com>> wrote: > Cheers all > > I have noticed that I often ends up with quite a number of nested expressions, for example: > > (((json at: 'tree') > select: [ :e | (e at: 'type') = âblob' ]) > collect: [:e | Path from: (e at: 'path')]) > select: [ :p | p segments last > in: [ :name | (name endsWith: '.md') | (name endsWith: '.mic') ] ] > > What kind of proposals (if any) have been for a different syntax which could give a more streamlined syntax? > > My own thinking has been around an alternative to the cascade semicolon. What symbol to use does not matter for me, but something like > json at: âtree' Âº > select: [ :e | ((e at: 'type') = 'blobâ)]Âº > collect: [:e | Path from: (e at: 'pathâ)]Âº > select: [ :p | p segments last > in: [ :name | (name endsWith: '.md') | (name endsWith: '.mic') ] ] > > Basically, a send the right hand expression to the result of the left hand expression. > > Has anyone ever tried this, or is it just one of the many small annoyances best left alone? > > Best, > > Kasper

Feb. 28, 2022

Re: Too many parenthesis - a matter of syntax

by Richard O'Keefe

I was bemused to realise that I've actually been programming for literally 50 years. It finally seeped through my thick skull I make enough mistakes that if it's hard to read, I probably got it wrong. And THIS code fragment is hard to read. I don't care if you use parentheses or pipes, it's hard to read either way. Oh, the pipes make the structure easier to see, true. But I am still left guessing what it is FOR. What's it SUPPOSED to mean? And the problem is that there are some abstractions missing. Of course this is JSON's fault. This is the first code smell, and in my experience it is almost ALWAYS a code smell: you are using JSON as a "processing" data structure instead of as a "communication" syntax. Using JSON inside your program, instead of at the edges, means that the semantics gets scattered all over the code, which leads to complexity and inconsistency. The convention I follow is that data structure more complicated than a string or an array of numbers has a Smalltalk class Whatsit>>asJson converts an instance to a JSON value Whatsit class>>fromJson: converts a JSON value to an instance. I'll start with topLevel := TopLevelWhatsit fromJson: someStream nextJson. and from then on I'm working with pure Smalltalk. This has the extra benefit of validating the input right away. I don't want my program running for several hours and then running into trouble because some component of the JSON value is missing or ill-formed. In practice, the time cost of converting JSON to (application- specific) Smalltalk is quite small compared with the cost of reading the JSON in the first place, and there can be seriously worthwhile savings in memory. For this example, we'd be looking at topLevel tree blobs collect: [:each | each path] thenSelect: [:path | path hasAnyExtension: #('md' 'mic')] My Filename class has methods has[Any]Extension:[ignoringCase:] which I have shamelessly exploited here. I like the way that they hide the structure of a Filename. The portmanteau methods Collection>>collect:thenSelect: Collection>>select:thenCollect: have existed in Pharo as long as Pharo has existed. They have two rationales: (a) improve readability (b) permit optimisation by eliminating an intermediate collection. Sequences exploit (b). Sets could too but happen not to. THEREFORE, here are free implementations of Set>>collect:thenSelect: and Set>>select:thenCollect: consistent with Pharo's Set>>collect: collect: collectBlock thenSelect: selectBlock "Override Collection>>collect:thenSelect: like OrderedCollection. Beware: 'self species' is often inappropriate, as in #collect:." |newSet| newSet := self species new: self size. self do: [:each | |item| item := collectBlock value: each. (selectBlock value: each) ifTrue: [newSet add: item]]. ^newSet select: selectBlock thenCollect: collectBlock "Override Collection>>select:thenCollect: like OrderedCollection. Beware: 'self species' is often inappropriate, as in #collect:." |newSet| newSet := self species new: self size. self do: [:each | (selectBlock value: each) ifTrue: [ newSet add: (collectBlock value: each)]]. ^newSet On Wed, 26 Jan 2022 at 22:19, Kasper Osterbye <kasper.osterbye(a)gmail.com> wrote: > Cheers all > > I have noticed that I often ends up with quite a number of nested > expressions, for example: > > (((json at: 'tree') > select: [ :e | (e at: 'type') = âblob' ]) > collect: [:e | Path from: (e at: 'path')]) > select: [ :p | p segments last > in: [ :name | (name endsWith: '.md') | > (name endsWith: '.mic') ] ] > > What kind of proposals (if any) have been for a different syntax which > could give a more streamlined syntax? > > My own thinking has been around an alternative to the cascade semicolon. > What symbol to use does not matter for me, but something like > json at: âtree' Âº > select: [ :e | ((e at: 'type') = 'blobâ)]Âº > collect: [:e | Path from: (e at: 'pathâ)]Âº > select: [ :p | p segments last > in: [ :name | (name endsWith: '.md') | (name endsWith: > '.mic') ] ] > > Basically, a send the right hand expression to the result of the left hand > expression. > > Has anyone ever tried this, or is it just one of the many small annoyances > best left alone? > > Best, > > Kasper

Feb. 26, 2022

Re: Too many parenthesis - a matter of syntax

by Kasper Osterbye

All the answers have been good. I am somewhat provoked (in the good sense of forcing me to think) by Siemen who sort of think of it as a code-smell. Best, Kasper > On 26 Feb 2022, at 17.14, Siemen Baader <siemenbaader(a)gmail.com> wrote: > > Hi Kasper, > > perhaps not what you are asking, but I find that this kind of nesting happens to me when parsing serialized data (web page sources or JSON as in your example). For me, the root cause of the problem is that these data structures are not represented by real classes in my code. I often start with what you are showing in a Playground, but then refactor it into specific parsers for the web sites I am scraping. The parsing selectors go into classes that mirror the parts of the data I am interested in. I find this to be more declarative and maintainable, and more natural in the Pharo environment with its browsers and code extractors. > > I hope this is of any use :)

Feb. 26, 2022

Re: Too many parenthesis - a matter of syntax

by Siemen Baader

Hi Kasper, perhaps not what you are asking, but I find that this kind of nesting happens to me when parsing serialized data (web page sources or JSON as in your example). For me, the root cause of the problem is that these data structures are not represented by real classes in my code. I often start with what you are showing in a Playground, but then refactor it into specific parsers for the web sites I am scraping. The parsing selectors go into classes that mirror the parts of the data I am interested in. I find this to be more declarative and maintainable, and more natural in the Pharo environment with its browsers and code extractors. I hope this is of any use :) cheers Siemen On Fri, Jan 28, 2022 at 11:55 PM Vitor Medina Cruz <vitormcruz(a)gmail.com> wrote: > I think that's OK when you can choose when to use parentheses. If you > think it would improve readability it is ok to use it, the problem is to be > forced to use it even when you think it decreases readability, what I > believe to be the case in discussion. > > On Thu, Jan 27, 2022 at 3:24 PM Russ Whaley <whaley.russ(a)gmail.com> wrote: > >> What I like about parentheses (and I hate parentheses) is that it allows >> me to view/describe the intent of the code. When parens are not used, it is >> up to me (perhaps years later) to determine whether the original developer >> (sometimes me) understood (or not) the actual 'order of processing'. >> Parens - or another vehicle - should help me understand the intent (as >> would detailed comments) - so I can devise tests (oh yeah, are those >> available, too?) for the intent - even if it is just me in the debugger. >> >> So, I'm for whatever helps me understand the intent of the code - even if >> there is some slick way to nest everything. I generally prefer breaking >> nested processes down into multiple steps. Benchmarking rarely shows >> significant performance differences, for me. >> >> (and I've used parentheses 7 times in this one email!) :-) >> >> Russ >> >> On Wed, Jan 26, 2022 at 4:20 AM Kasper Osterbye < >> kasper.osterbye(a)gmail.com> wrote: >> >>> Cheers all >>> >>> I have noticed that I often ends up with quite a number of nested >>> expressions, for example: >>> >>> (((json at: 'tree') >>> select: [ :e | (e at: 'type') = âblob' ]) >>> collect: [:e | Path from: (e at: 'path')]) >>> select: [ :p | p segments last >>> in: [ :name | (name endsWith: '.md') | >>> (name endsWith: '.mic') ] ] >>> >>> What kind of proposals (if any) have been for a different syntax which >>> could give a more streamlined syntax? >>> >>> My own thinking has been around an alternative to the cascade semicolon. >>> What symbol to use does not matter for me, but something like >>> json at: âtree' Âº >>> select: [ :e | ((e at: 'type') = 'blobâ)]Âº >>> collect: [:e | Path from: (e at: 'pathâ)]Âº >>> select: [ :p | p segments last >>> in: [ :name | (name endsWith: '.md') | (name endsWith: >>> '.mic') ] ] >>> >>> Basically, a send the right hand expression to the result of the left >>> hand expression. >>> >>> Has anyone ever tried this, or is it just one of the many small >>> annoyances best left alone? >>> >>> Best, >>> >>> Kasper >> >> >> >> -- >> Russ Whaley >> whaley.russ(a)gmail.com >> >

Feb. 26, 2022

R: Re: Image

by kikka

Thank you a lot for you tip about newest version; Iâll take it for sure :) And thanks for your indications; Iâm watching the video you sent. Regards Federica Cordiali saluti Federica Schiavina Da: Tim Mackinnon [mailto:tim@testit.works] Inviato: giovedÃ¬ 24 febbraio 2022 15.21 A: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Oggetto: [Pharo-users] Re: Image Hi Federica - that is a very old version of Pharo that you are using - you should consider using a much newer version (ideally the latest - as there are many more tools for recovering lost work, and in fact the environment can detect it and prompt you, equally there is GIT integration which is something you should also consider learning about). This said - the above doesn't help you now. You are correct, that the .changes file will have your work in it. I don't quite recall back then what worked - I see in this video https://www.youtube.com/watch?v=jwKDFbPkHzw that you might be able to drag and drop that file to access them - or - worst case is, you can open that file with a pharo editor and then you can hilite sections and use "doit" to re-evaluate them. Or use a text editor to open the file and then find the code you are missing and paste it into pharo. Its a bit painful, but you should be able to get things back reasonably quickly. Someone else might remember more. If you are cutting and pasting - I would consider doing it with a newer version of Pharo. Hope this helps, Tim On Thu, 24 Feb 2022, at 1:45 PM, kikka wrote: Hi everybody, I have a big problem. After working on my application I closed Pharo. When I got back the shortcut wasnât working any more and I realized my image got ruined. I could recover just a very old version of my C:\Seaside-3.1-portable\Seaside-3.1-portable.app\Contents\Resources\Pharo4.0-portable.image (no recent backup). I have seen that all the changes I have developed can be seen in C:\Seaside-3.1-portable\Seaside-3.1-portable.app\Contents\Resources\Pharo4.0-portable.changes I was wondering if it was possible to load all the changes on the old Pharo4.0-portable.image without losing all my work. Hanks in advance for any help. Regards. Federica <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Mail priva di virus. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> www.avast.com -- Questa e-mail Ã¨ stata controllata per individuare virus con Avast antivirus. https://www.avast.com/antivirus

Feb. 24, 2022

Re: Image

by Tim Mackinnon

Hi Federica - that is a very old version of Pharo that you are using - you should consider using a much newer version (ideally the latest - as there are many more tools for recovering lost work, and in fact the environment can detect it and prompt you, equally there is GIT integration which is something you should also consider learning about). This said - the above doesn't help you now. You are correct, that the .changes file will have your work in it. I don't quite recall back then what worked - I see in this video https://www.youtube.com/watch?v=jwKDFbPkHzw that you might be able to drag and drop that file to access them - or - worst case is, you can open that file with a pharo editor and then you can hilite sections and use "doit" to re-evaluate them. Or use a text editor to open the file and then find the code you are missing and paste it into pharo. Its a bit painful, but you should be able to get things back reasonably quickly. Someone else might remember more. If you are cutting and pasting - I would consider doing it with a newer version of Pharo. Hope this helps, Tim On Thu, 24 Feb 2022, at 1:45 PM, kikka wrote: > Hi everybody, > > I have a big problem. > > After working on my application I closed Pharo. > > When I got back the shortcut wasnât working any more and I realized my image got ruined. > > I could recover just a very old version of my C:\Seaside-3.1-portable\Seaside-3.1-portable.app\Contents\Resources\Pharo4.0-portable.image (no recent backup). > > I have seen that all the changes I have developed can be seen in C:\Seaside-3.1-portable\Seaside-3.1-portable.app\Contents\Resources\Pharo4.0-portable.changes I was wondering if it was possible to load all the changes on the old Pharo4.0-portable.image without losing all my work. > > Hanks in advance for any help. > > Regards. > > Federica > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> > Mail priva di virus. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <https://www.fastmail.com/mail/list.1-pharo/compose/Me918b843c4f1c7537ab8ea4…>

Feb. 24, 2022

Image

by kikka

Hi everybody, I have a big problem. After working on my application I closed Pharo. When I got back the shortcut wasn't working any more and I realized my image got ruined. I could recover just a very old version of my C:\Seaside-3.1-portable\Seaside-3.1-portable.app\Contents\Resources\Pharo4.0 -portable.image (no recent backup). I have seen that all the changes I have developed can be seen in C:\Seaside-3.1-portable\Seaside-3.1-portable.app\Contents\Resources\Pharo4.0 -portable.changes I was wondering if it was possible to load all the changes on the old Pharo4.0-portable.image without losing all my work. Hanks in advance for any help. Regards. Federica -- Questa e-mail Ã¨ stata controllata per individuare virus con Avast antivirus. https://www.avast.com/antivirus

Feb. 24, 2022

Re: Changes to class not recorded in change.log?

by Stewart MacLean

Hi Tim, Apologies for not replying sooner - I'm a recent migrant to GMail and it keeps flagging good mail as spam! I haven't explored this further, I think I was using the old Changes Browser. As I'm back to "square one" I've moved on to other problems, but when I get a chance I'll conduct some tests. Thanks, Stew On Tue, Feb 15, 2022 at 4:57 AM Tim Mackinnon <tim(a)testit.works> wrote: > Hi Stewart - are you using the Code Changes (Epicea) browser - or trying > to use the older changes files? > > Your message wasn't clear - and I have seen oddities with Epicea too - but > normally I have been able to recover instance variables too (sometimes the > restore options were a bit confusing and I did it in the wrong order). > > Note - I haven't tried this in V9 though - so possibly something has > regressed. Thought it worth checking though. > > Tim > > On Mon, 14 Feb 2022, at 7:36 AM, Stewart MacLean wrote: > > Hi, > > The worst case scenario has just happened - my image is hosed. > > I've managed to recover a previous set of change/image files (thanks > CrashPlan!). > > Then I've replayed all the intervening changes - however I find that some > instance variables that I had defined haven't been reflected in class shape > changes. > > I notice all the changes for the complete change log are for Method, and > Do It (image saves) > > Surely class shape changes should be recorded as well? Is this a bug? > > Cheers, > > Stewart > > Platform Mac Mini > Pharo 9.0.0 > Build information: > Pharo-9.0.0+build.1573.sha.0e09d756fc99383cbb498565200d9e5e9841ce11 (64 Bit) > > >

Feb. 21, 2022

Fwd: ESUG 2022 call for presentations And Call for student volunteers

by stephane ducasse

A reminderâ¦ S > Begin forwarded message: > > From: "stephane.ducasse(a)free.fr" <stephane.ducasse(a)free.fr> > Subject: ESUG 2022 call for presentations And Call for student volunteers > Date: 13 January 2022 at 13:23:44 CET > > ESUG 2022 > Serbia 22. â 26.8. > > You can support the ESUG conference in many different ways: > Sponsor the conference. New sponsoring packages are described at http://www.esug.org/supportesug/becomeasponsor/ <http://www.esug.org/supportesug/becomeasponsor/> > Submit a talk, a software or a paper to one of the events. See below. > Attend the conference. We'd like to beat the previous record of attendance (170 people at Amsterdam 2008)! > Students can get free registration and hosting if they enroll into the the Student Volunteers program. See below. > <>Developers Forum: International Smalltalk Developers Conference > > We are looking for YOUR experience on using Smalltalk. You will have 30 min for presentations and 45 min for hands-on tutorials. > The list of topics for the normal talks and tutorials includes, but is not limited to the following: > XP practices, Development tools, Experience reports > Model driven development, Web development, Team management > Meta-Modeling, Security, New libraries & frameworks > Educational material, Embedded systems and robotics > SOA and Web services, Interaction with other programming languages > <>Teaching Pearls and Show us Your Business > > New this year!!! We added two types of sessions in addition to the regular talks and show us your projects sessions. > Show your business 10 min session (Get prepared!!) > Teaching pearls : we want some session on how to teach some design aspects. We want your tip and tricks to teach Smalltalk or OOP. > We expect to have several 10 to 15 min sessions aggregated. > <>How to submit? > > Make a Pull Request here https://github.com/ESUG/esug.github.io/tree/source/2022-Conference/talks > > Or but only if you are not connected to the worldâ¦ send an email to stephane.ducasse(a)inria.fr > > Title: [ESUG 2022] Please follow the template below the email will be automatically processed! > Name: > Email: > Abstract: > Bio: > > Call for Student Volunteers > Student volunteers help keep the conference running smoothly; in return, they have free accommodations, while still having most of the time to enjoy the conference. > > Pay attention: the places are limited so do not wait till the last minute to apply. > > Conference details: > Send an email to stephane.ducasse at inria.fr and serge.stinckwich at gmail.com with: > > title: [ESUG 2022 Student] > name, gender, university/school, country, email address > short description of you and why you are interested in participating > For which period is accommodation covered? Accommodation is covered from Sunday 21 August until Friday 26 August 2022 (including nights from Sunday to Monday and from Thursday to Friday). Students will be hosted in student rooms. ESUG additionally covers for the lunches during the week and one dinner. > > Duties include handling registration as people arrive at the conference, filling coffee machines, collecting presentation slides for ESUG right after the presentation is given, being present at an information desk to answer questions, and generally being helpful. Student volunteering makes the conference better, takes a fairly small amount of time and doesn't significantly interfere with enjoying and learning from the conference. Please Note, this role requires discipline and constant attention to all attendees. > > Information about hotel > Student Volunteer rooms are booked at (to be announced). If you are student volunteer, do not book yourself, we have arranged the booking already! >

Feb. 20, 2022

Re: [ANN] Pharo LZ4 Tools

by ducasse

Yes this is a nice conversation. I know that marcus is working on slim binary. The idea is to compress but I forgot if it was bytecode or trees. Now I wonder if the code text is worth compression. >> On 18 Feb 2022, at 21:25, Guillermo Polito <guillermopolito(a)gmail.com> wrote: >> >> Thanks Sven, great stuff :) > > Thanks! > > This allows you to easily play/explore/experiment with certain ideas. > > In the past we discussed about the option of bringing source code inside the image, what if we applied compression ? > > The total size of all Object methods is about 100k: > > Object allMethods sum: [ :each | each sourceCode size ]. > > "104633" > > We can compress each individual method as an LZ4 block and see what that gives us. > > LZ4Compressor new in: [ :compressor | > Object allMethods sum: [ :each | | compressed | > compressed := compressor compressBlock: each sourceCode utf8Encoded. > compressed size ] ]. > > "81584" > > (104633/81584) reciprocal asFloat. > > "0.7797157684478129" > > That is about 22% smaller. This is not a very good result. But that is to be expected because methods are small and there is often not much to compress. > > If we concatenate all source code and feed that as one big chunk to the compressor we get much better results. > > (LZ4Compressor new compress: > (String streamContents: [ :out | > Object allMethods do: [ :each | out nextPutAll: each sourceCode ] ]) utf8Encoded) size. > > "53544" > > (104633/53544) reciprocal asFloat. > > "0.5117314805080615" > > Now we get an almost 50% reduction in size. But methods are independent, so that is not an option. What if we used a dictionary, a predefined set of words/substrings that are common in source code. > > I found a list of the 500 most common English words. Let's add some common selectors and globals. > > IdentityBag new in: [ :bag | > SystemNavigation default allMethods do: [ :each | > each literals select: [ :x | x isSymbol ] thenDo: [ :x | bag add: x ] ]. > bag sortedCounts select: [ :x | x key > 100 ] ]. > > IdentityBag new in: [ :bag | > SystemNavigation default allMethods do: [ :each | > each literals select: [ :x | x isVariableBinding ] thenDo: [ :x | bag add: x key ] ]. > bag sortedCounts select: [ :x | x key > 100 ] ]. > > The smallest possible match in LZ4 is 4 bytes (3 letters and a space). > > words := Character space join: (((FileLocator desktop / 'en-500.csv' readStreamDo: [ :in | (NeoCSVReader on: in) addIgnoredField; addField; upToEnd ]) collect: #first) select: [ :each | each size > 2 ]). > > That are 473 words. Next are 137 selectors. > > selectors := ' ifTrue: assert: class assert:equals: ifTrue:ifFalse: ifNil: ifFalse: yourself name and: ifNotNil: traitComposition add: first deny: includes: isEmpty asString nextPutAll: with: isNil collect: initialize subclassResponsibility to:do: selector localMethodDict should:raise: theme notNil printString on:do: streamContents: at:ifAbsent: copy contents error: last model default ifNil:ifNotNil: organization skipOrReturnWith:ifSkippable: current parserExceptions nonEmpty select: asSymbol name: readStream includesKey: basicNew title: empty reject: whileTrue: keys space class: extent: close anySatisfy: parse:documentURI: isLocalSelector: traitSource second position print: whileFalse: asArray format: printOn: selectors isKindOf: copyFrom:to: color: shouldnt:raise: width height max: named: signal hasProperty: anyOne text detect:ifNone: label: ensure: ifEmpty: extent text: entity addAll: negated includesLocalSelector: addSelector:withMethod: traitDefining:ifNone: hash addSelector:on: asInteger min: translated iconNamed: method arguments position: withIndexDo: perform: methods delete url: occurrencesOf: selector: hResizing: with:with: pass notEmpty flag: values removeKey: fromString: classNamed: reset changed removeKey:ifAbsent: width: announce: repository: signal: setUp addLast: session uniqueInstance assert:description: asOrderedCollection compiledMethod assert:gives: '. > > Finally 73 globals. > > globals := ' String OrderedCollection Array Smalltalk Color Error Character Dictionary TraitChange ByteArray Object UIManager DateAndTime Set Form Time ZTimestamp Date RBParser World Protocol Duration Processor SAXHandler Display MetaLink HelpTopic ReflectivityExamples IdentitySet OCOpalExamples GLMTabulator Float SpecLayout UUID WAMimeType SystemAnnouncer STON XMLDOMParser ZnMimeType Transcript ZnEntity ExternalType CompiledMethod GRPlatform Semaphore FileSystem ReadWriteStream ZnClient WriteStream Delay CmdContextMenuActivation ZnResponse FileLocator IdentityDictionary Morph MCSnapshot ReflectiveMethod XMLValidationException Integer MCMethodDefinition Path ClyClassScope MCClassDefinition RBCondition MCVersionInfo MCVersion SmallInteger Cursor TraitedClass GoferVersionReference SortedCollection MCOrganizationDefinition XMLWellFormednessException '. > > dictionary := (globals , words , selectors) utf8Encoded. > > This dictionary is less than 5K. > > (LZ4Compressor new dictionary: dictionary) in: [ :compressor | > Object allMethods sum: [ :each | | compressed | > compressed := compressor compressBlock: each sourceCode utf8Encoded. > compressed size ] ]. > > "69146" > > (104633/69146) reciprocal asFloat. > > "0.6608431374422983" > > Now we get a 33% reduction in size, which is better. > > I am sure that with a more carefully, better tuned dictionary the compression rate could be improved a couple of percent. There also exist tools that can compute an optimal dictionary from a given input set. > > Sorry for the long post, I hope at least someone found this interesting. > > Sven > > >> EnvoyÃ© depuis mon tÃ©lÃ©phone Huawei >> >> >> -------- Message original -------- >> De : Sven Van Caekenberghe <sven(a)stfx.eu> >> Date : ven. 18 fÃ©vr. 2022 Ã 21:13 >> Ã : Any question about pharo is welcome <pharo-users(a)lists.pharo.org> >> Objet : [Pharo-users] [ANN] Pharo LZ4 Tools >> Hi, >> >> Pharo LZ4 Tools (https://github.com/svenvc/pharo-lz4-tools) is an implementation of LZ4 compression and decompression in pure Pharo. >> >> LZ4 is a lossless compression algorithm that is focused on speed. It belongs to the LZ77 family of byte-oriented compression schemes. >> >> - https://en.wikipedia.org/wiki/LZ4_(compression_algorithm) >> - https://lz4.github.io/lz4/ >> - https://github.com/lz4/lz4 >> >> Both the frame format (https://github.com/lz4/lz4/blob/dev/doc/lz4_Frame_format.md) as well as the block format (https://github.com/lz4/lz4/blob/dev/doc/lz4_Block_format.md) are implemented. Dictionary based compression/decompression is available too. The XXHash32 algorithm is also implemented. >> >> Of course this implementation is not as fast as highly optimised native implementations, but it works quite well and is readable/understandable, if you like this kind of stuff. It can be useful to interact with other systems using LZ4. >> >> Sven

Feb. 20, 2022

Re: [ANN] Pharo LZ4 Tools

by Sven Van Caekenberghe

> On 18 Feb 2022, at 21:25, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > Thanks Sven, great stuff :) Thanks! This allows you to easily play/explore/experiment with certain ideas. In the past we discussed about the option of bringing source code inside the image, what if we applied compression ? The total size of all Object methods is about 100k: Object allMethods sum: [ :each | each sourceCode size ]. "104633" We can compress each individual method as an LZ4 block and see what that gives us. LZ4Compressor new in: [ :compressor | Object allMethods sum: [ :each | | compressed | compressed := compressor compressBlock: each sourceCode utf8Encoded. compressed size ] ]. "81584" (104633/81584) reciprocal asFloat. "0.7797157684478129" That is about 22% smaller. This is not a very good result. But that is to be expected because methods are small and there is often not much to compress. If we concatenate all source code and feed that as one big chunk to the compressor we get much better results. (LZ4Compressor new compress: (String streamContents: [ :out | Object allMethods do: [ :each | out nextPutAll: each sourceCode ] ]) utf8Encoded) size. "53544" (104633/53544) reciprocal asFloat. "0.5117314805080615" Now we get an almost 50% reduction in size. But methods are independent, so that is not an option. What if we used a dictionary, a predefined set of words/substrings that are common in source code. I found a list of the 500 most common English words. Let's add some common selectors and globals. IdentityBag new in: [ :bag | SystemNavigation default allMethods do: [ :each | each literals select: [ :x | x isSymbol ] thenDo: [ :x | bag add: x ] ]. bag sortedCounts select: [ :x | x key > 100 ] ]. IdentityBag new in: [ :bag | SystemNavigation default allMethods do: [ :each | each literals select: [ :x | x isVariableBinding ] thenDo: [ :x | bag add: x key ] ]. bag sortedCounts select: [ :x | x key > 100 ] ]. The smallest possible match in LZ4 is 4 bytes (3 letters and a space). words := Character space join: (((FileLocator desktop / 'en-500.csv' readStreamDo: [ :in | (NeoCSVReader on: in) addIgnoredField; addField; upToEnd ]) collect: #first) select: [ :each | each size > 2 ]). That are 473 words. Next are 137 selectors. selectors := ' ifTrue: assert: class assert:equals: ifTrue:ifFalse: ifNil: ifFalse: yourself name and: ifNotNil: traitComposition add: first deny: includes: isEmpty asString nextPutAll: with: isNil collect: initialize subclassResponsibility to:do: selector localMethodDict should:raise: theme notNil printString on:do: streamContents: at:ifAbsent: copy contents error: last model default ifNil:ifNotNil: organization skipOrReturnWith:ifSkippable: current parserExceptions nonEmpty select: asSymbol name: readStream includesKey: basicNew title: empty reject: whileTrue: keys space class: extent: close anySatisfy: parse:documentURI: isLocalSelector: traitSource second position print: whileFalse: asArray format: printOn: selectors isKindOf: copyFrom:to: color: shouldnt:raise: width height max: named: signal hasProperty: anyOne text detect:ifNone: label: ensure: ifEmpty: extent text: entity addAll: negated includesLocalSelector: addSelector:withMethod: traitDefining:ifNone: hash addSelector:on: asInteger min: translated iconNamed: method arguments position: withIndexDo: perform: methods delete url: occurrencesOf: selector: hResizing: with:with: pass notEmpty flag: values removeKey: fromString: classNamed: reset changed removeKey:ifAbsent: width: announce: repository: signal: setUp addLast: session uniqueInstance assert:description: asOrderedCollection compiledMethod assert:gives: '. Finally 73 globals. globals := ' String OrderedCollection Array Smalltalk Color Error Character Dictionary TraitChange ByteArray Object UIManager DateAndTime Set Form Time ZTimestamp Date RBParser World Protocol Duration Processor SAXHandler Display MetaLink HelpTopic ReflectivityExamples IdentitySet OCOpalExamples GLMTabulator Float SpecLayout UUID WAMimeType SystemAnnouncer STON XMLDOMParser ZnMimeType Transcript ZnEntity ExternalType CompiledMethod GRPlatform Semaphore FileSystem ReadWriteStream ZnClient WriteStream Delay CmdContextMenuActivation ZnResponse FileLocator IdentityDictionary Morph MCSnapshot ReflectiveMethod XMLValidationException Integer MCMethodDefinition Path ClyClassScope MCClassDefinition RBCondition MCVersionInfo MCVersion SmallInteger Cursor TraitedClass GoferVersionReference SortedCollection MCOrganizationDefinition XMLWellFormednessException '. dictionary := (globals , words , selectors) utf8Encoded. This dictionary is less than 5K. (LZ4Compressor new dictionary: dictionary) in: [ :compressor | Object allMethods sum: [ :each | | compressed | compressed := compressor compressBlock: each sourceCode utf8Encoded. compressed size ] ]. "69146" (104633/69146) reciprocal asFloat. "0.6608431374422983" Now we get a 33% reduction in size, which is better. I am sure that with a more carefully, better tuned dictionary the compression rate could be improved a couple of percent. There also exist tools that can compute an optimal dictionary from a given input set. Sorry for the long post, I hope at least someone found this interesting. Sven > EnvoyÃ© depuis mon tÃ©lÃ©phone Huawei > > > -------- Message original -------- > De : Sven Van Caekenberghe <sven(a)stfx.eu> > Date : ven. 18 fÃ©vr. 2022 Ã 21:13 > Ã : Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > Objet : [Pharo-users] [ANN] Pharo LZ4 Tools > Hi, > > Pharo LZ4 Tools (https://github.com/svenvc/pharo-lz4-tools) is an implementation of LZ4 compression and decompression in pure Pharo. > > LZ4 is a lossless compression algorithm that is focused on speed. It belongs to the LZ77 family of byte-oriented compression schemes. > > - https://en.wikipedia.org/wiki/LZ4_(compression_algorithm) > - https://lz4.github.io/lz4/ > - https://github.com/lz4/lz4 > > Both the frame format (https://github.com/lz4/lz4/blob/dev/doc/lz4_Frame_format.md) as well as the block format (https://github.com/lz4/lz4/blob/dev/doc/lz4_Block_format.md) are implemented. Dictionary based compression/decompression is available too. The XXHash32 algorithm is also implemented. > > Of course this implementation is not as fast as highly optimised native implementations, but it works quite well and is readable/understandable, if you like this kind of stuff. It can be useful to interact with other systems using LZ4. > > Sven

Feb. 20, 2022

UK Smalltalk User Group meeting - 23 February 2022

by Giovanni Corriga

For this month's UKSTUG meeting, we'll open the floor to the whole audience and let people show what they are working on. If you have an interesting project to show, or if you'd like to get some help with some hard problem, just show up and be ready to present! This will be an online meeting from home. If you'd like to join us, please sign up in advance on the meeting's Meetup page ( https://www.meetup.com/UKSTUG/events/284113812/ ) to receive the meeting details. Donât forget to bring your laptop and drinks!

Feb. 19, 2022

Re: [ANN] Pharo LZ4 Tools

by Guillermo Polito

Feb. 18, 2022

[ANN] Pharo LZ4 Tools

by Sven Van Caekenberghe

Hi, Pharo LZ4 Tools (https://github.com/svenvc/pharo-lz4-tools) is an implementation of LZ4 compression and decompression in pure Pharo. LZ4 is a lossless compression algorithm that is focused on speed. It belongs to the LZ77 family of byte-oriented compression schemes. - https://en.wikipedia.org/wiki/LZ4_(compression_algorithm) - https://lz4.github.io/lz4/ - https://github.com/lz4/lz4 Both the frame format (https://github.com/lz4/lz4/blob/dev/doc/lz4_Frame_format.md) as well as the block format (https://github.com/lz4/lz4/blob/dev/doc/lz4_Block_format.md) are implemented. Dictionary based compression/decompression is available too. The XXHash32 algorithm is also implemented. Of course this implementation is not as fast as highly optimised native implementations, but it works quite well and is readable/understandable, if you like this kind of stuff. It can be useful to interact with other systems using LZ4. Sven

Feb. 18, 2022

[ANN] Stargate v7.0.1 [v7.0.1] released!

by Buenos Aires Smalltalk

Feb. 18, 2022

[ANN] Stargate-Consul v3.0.1 [v3.0.1] released!

by Buenos Aires Smalltalk

Feb. 18, 2022

Re: [Issue tracker] Please check your older issues

by Marcus Denker

Thanks to everyone who helped digging through the old issues! We managed to close over 140 issue in 2022 already, with just 801 issues open (and >3500 issues closed overall since we moved to this issue tracker). Often it feels a bit useless âjust one issue downâ¦ what difference does that make?â. But you can only close 3500 issues by looking at each of them, one after the other... Marcus > On 7 Feb 2022, at 11:56, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > We are seeing lots of issue that are still open, but already fixed or just not valid anymore. > e.g. > > - the fix that was merged but the issue was not closed (sometimes GitHub has problems doing that) > - Bug was fixed independent of the issue > - The issue is just not relevant anymore > > > It is often quite time consuming to even find out that an issue is already fixedâ¦ > > It would be nice if everyone could check the issues that > > - you submitted yourself > - that are assigned to you > - [Bonus] where you were part of some discussion > > > https://github.com/pharo-project/pharo/issues > > > Marcus

Feb. 15, 2022

Re: Changes to class not recorded in change.log?

by Tim Mackinnon

Hi Stewart - are you using the Code Changes (Epicea) browser - or trying to use the older changes files? Your message wasn't clear - and I have seen oddities with Epicea too - but normally I have been able to recover instance variables too (sometimes the restore options were a bit confusing and I did it in the wrong order). Note - I haven't tried this in V9 though - so possibly something has regressed. Thought it worth checking though. Tim On Mon, 14 Feb 2022, at 7:36 AM, Stewart MacLean wrote: > Hi, > > The worst case scenario has just happened - my image is hosed. > > I've managed to recover a previous set of change/image files (thanks CrashPlan!). > > Then I've replayed all the intervening changes - however I find that some instance variables that I had defined haven't been reflected in class shape changes. > > I notice all the changes for the complete change log are for Method, and Do It (image saves) > > Surely class shape changes should be recorded as well? Is this a bug? > > Cheers, > > Stewart > > Platform Mac Mini > Pharo 9.0.0 > Build information: Pharo-9.0.0+build.1573.sha.0e09d756fc99383cbb498565200d9e5e9841ce11 (64 Bit) >

Feb. 14, 2022

Re: Changes to class not recorded in change.log?

by Marcus Denker

> On 14 Feb 2022, at 08:36, Stewart MacLean <stewart(a)xtra.co.nz> wrote: > > Hi, > > The worst case scenario has just happened - my image is hosed. > > I've managed to recover a previous set of change/image files (thanks CrashPlan!). > > Then I've replayed all the intervening changes - however I find that some instance variables that I had defined haven't been reflected in class shape changes. > > I notice all the changes for the complete change log are for Method, and Do It (image saves) > > Surely class shape changes should be recorded as well? Is this a bug? > Yes, normally the lass change should be recorded, too. So that looks like a bug. Marcus

Feb. 14, 2022

Changes to class not recorded in change.log?

by Stewart MacLean

Hi, The worst case scenario has just happened - my image is hosed. I've managed to recover a previous set of change/image files (thanks CrashPlan!). Then I've replayed all the intervening changes - however I find that some instance variables that I had defined haven't been reflected in class shape changes. I notice all the changes for the complete change log are for Method, and Do It (image saves) Surely class shape changes should be recorded as well? Is this a bug? Cheers, Stewart Platform Mac Mini Pharo 9.0.0 Build information: Pharo-9.0.0+build.1573.sha.0e09d756fc99383cbb498565200d9e5e9841ce11 (64 Bit)

Feb. 14, 2022

Spec border widths of 0 are showing as lines?

by Stewart MacLean

Hi all, I have set the border widths of SpBoxLayout to 0, but there are still lines showing between the various components. Please see attached. As a work around, I thought to set the color of the border to the background color of each panel, but SpBoxLayout doesn't have a borderColor: method. How do I get borders to not show so that adjacent panels blend? And how do I set the color of borders? I am using SpRoassalPresenters and have tried setting the borderColor against them to no effect. Thanks, Stewart

Feb. 11, 2022

Re: [Pharo-users] Re: What is "Fluid"?

by contactme＠kathe.in

On Thursday, February 10, 2022 15:33 CET, Marcus Denker <marcus.denker(a)inria.fr> wrote: Â Â It is a real interesting research question: How an you build Systems that can evolve over a long time ? Systems which evolve over time need to have a very tiny core which is supremely malleable. For one, I would start with a "Forth" and add an object-system to it using the "Metaobject Protocol" along with a Common Lisp like "Condition System". Â Â Forth in the context of the core of an object system is interestingâ¦ someone did in 1979 a Smalltalk and Forth inspired system called âRosetta Smalltalk"Â https://dl.acm.org/doi/10.1145/1113572.1113555Â But: the nice thing of evolving a system is that you *always* can show a real, working result. You can have users, including yourselfâ¦ you can find ways of financingÂ your work that is not just promising something for the future. (which you can only do so often before people get sceptical).Â I think being part of the early Squeak community kind of burned for me the âletâs not improve that (relatively) simple thing A, instead wait for <genius X> to finish <amazing Project Z>.Â Imagine instead you would build a feedback-loop *inside* of your system...Â Â Marcus Agree about what you felt within the Squeak community, I was there too around 1999~2000. There were a bunch of geniuses there, but the way I understand it, geniuses produce the initial spark, but you need strong-willed, perseverent people to kindle the project there-after. The reason I was drawn to Pharo is because of what Ducasse and you and others like you have done with the core spark of Smalltalk-80 based Squeak running Morphic. Though, I've always liked the MVC environment more and fell in love with the "Third-Way" project to deliver a full-blown widget-set for MVC developed by a guy called Gartner (I think) from Germany. Â Do you have a pointer?---- Yes, I got the URL after searching through Google a lot of times. :-) His name is Boris Gaertner and he is/was from Germany. https://wiki.squeak.org/squeak/1829.diff?id=19 I couldn't find his webpage though, and I couldn't locate the code of his framework. Maybe you could ask on the Squeak mailing list! Â Can you elaborate on your feedback-loop *inside* the system idea? Especially in the context of Pharo? Â Â So your âSystems which evolve over time need to have a very tiny core which is supremely malleableâ I actually think is very true.. and Pharo clearly is not there yet.(and what that even is supposed to be.. has many answers).Â But what we technical people are the quickly to say âaÂ malleableÂ system needs a very tiny core, so letâs first do thatâ. And abandon what we have.Â Â But if you step back, for the end-âuserâ (that is programmer) it would not change much, it would solve nothing on that level of the problem of howto evolve a platform *and* the systems using it. Which might be even harder to do right than the kernel...Â Another aspect is that âlets build the perfect evolvable systemâ is as impossible as âlets build the perfect systemââ¦ when you are done, yourealise that you could do even better!Â Â Marcus---- Yes, I agree on the point of things just never being done in the world of software. Though, I do tend to think "Common Lisp" is a done language, but their development environments (even commercial ones) leave a lot to be desired. For a moment think from the perspective of art, as one of the greats had mentioned; perfection is achieved when there's nothing more to take away. I think what you and the core team did using the stuff (core Squeak + Morphic) available to you back then without knowledge about Boris Gaertner's work is quite an achievement. But Pharo is really too big, especially when you compare it with a standard Smalltalk-80 system. Maybe the core team "could" consider going along the same path of cleaning-up and simplifying the core Smalltalk system further but instead of working with the bloat of Morphic, instead go with that MVC-based "ThirdWay" framework! In fact, I would wholeheartedly support the core team changing a lot of what it means to be Smalltalk if the end result can be made smaller and more malleable. As an example of a minimalistic and extremely malleable language, take a look at "io"; https://iolanguage.org/ Yes, it's a lot bigger than a Forth, but at least it won't drive normal people to insanity. :-D Just a suggestion, no intention of denigrating the work that has been done till date. Â

Feb. 11, 2022

Re: What am I doing wrong with Spec2 in Pharo 9?

by Robert Briggs

Thanks Kasper Thatâs kind of what I thought.Â I think itâs because I did not enclose the instance in a layout such as SpBoxLayout which meant I couldnât get the reference to the instance in order to execute valueAtCollumn:row:. Iâve implemented a new subclass to verify this and it works. Regards Bob From: Kasper Osterbye <kasper.osterbye(a)gmail.com> Reply to: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Date: Thursday, 10 February 2022 at 14:30 To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Subject: [Pharo-users] Re: What am I doing wrong with Spec2 in Pharo 9? It might be something else, but the browser to the left is looking at the instance side, whereas the browser to the right is looking at the class side. Hence, your class side method openAttributeEditorOn: do not know about the instance side method valueAtColumn:row: It is hard to guess from your code, but I guess you need to capture the table instance in the double click and pass that to the class side, or implement the openAttributeEditorOn: on the instance side to give access self on the instance side. Best, Kasper On 10 Feb 2022, at 12.27, Robert Briggs via Pharo-users <pharo-users(a)lists.pharo.org> wrote: I have a subclass of SpTablePresenter which correctly displays a list of items. It is set up to activateOnDoubleClick as I want to open another SpPresenter I have created on the selected table row using the value in the first column to complete the presenter. My SpTablePresenter headed Element Attributes is shown bottom left in the attached screenshot. The class method top right reports that valueAtColumn:row: is sent but not implemented and yet it clearly is implemented by the superclass of my presenter (and I have used the method elsewhere in my project (NB: this method is just an instrument at the moment so that I can check what is happening. Double clicking a table row executes the method openAttributeEditorOn: but the debugger reports instance of my presenter class did not understand valueAtColumn:row: So what am I doing wrong here? Advice please. Regards Bob Briggs <PharoScreenshot.2.png>

Feb. 10, 2022

Re: What is "Fluid"?

by Offray Vladimir Luna CÃ¡rdenas

On 10/02/22 9:33, Marcus Denker wrote: > > So your âSystems which evolve over time need to have a very tiny core > which is supremely malleableâ I actually think is very true.. and > Pharo clearly is not there yet. > (and what that even is supposed to be.. has many answers). > > But what we technical people are the quickly to say > âaÂ malleableÂ system needs a very tiny core, so letâs first do thatâ. > And abandon what we have. > > But if you step back, for the end-âuserâ (that is programmer) it would > not change much, it would solve nothing on that level of the problem > of how > to evolve a platform *and* the systems using it. Which might be even > harder to do right than the kernel... > > Another aspect is that âlets build the perfect evolvable systemâ is as > impossible as âlets build the perfect systemââ¦ when you are done, you > realise that you could do even better! > > Marcus Recently I was seeing some videos abut GToolkit and Cuis and I thought about how both approach to malleability/understandability in different interesting ways: Cuis by providing a small extensible core that gets simpler over time and GToolkit by providing a compelling default user experience that invites to use and query the system in different ways. I think that the ways Smalltalk systems approach malleability (particularly Pharo/Cuis based) can have deep impacts for populations beyond programmers, as showcased in my recent list post about sharing data stories powered by Pharo, that in fact related with Malleable Systems Wiki [1], [1] https://mutabit.com/repos.fossil/malleable-systems/doc/trunk/wiki/en/mallea… Cheers, Offray

Feb. 10, 2022

Re: What is "Fluid"?

by Marcus Denker

>>> >>> It is a real interesting research question: How an you build Systems that can evolve over a long time ? >> >> Systems which evolve over time need to have a very tiny core which is supremely malleable. >> For one, I would start with a "Forth" and add an object-system to it using the "Metaobject Protocol" along with a Common Lisp like "Condition System". >> > Forth in the context of the core of an object system is interestingâ¦ someone did in 1979 a Smalltalk and Forth inspired system called âRosetta Smalltalk" > > https://dl.acm.org/doi/10.1145/1113572.1113555 <https://dl.acm.org/doi/10.1145/1113572.1113555> > > But: the nice thing of evolving a system is that you *always* can show a real, working result. You can have users, including yourselfâ¦ you can find ways of financing > your work that is not just promising something for the future. (which you can only do so often before people get sceptical). > > I think being part of the early Squeak community kind of burned for me the âletâs not improve that (relatively) simple thing A, instead wait for <genius X> to finish <amazing Project Z>. > > Imagine instead you would build a feedback-loop *inside* of your system... > > > Marcus > > > Agree about what you felt within the Squeak community, I was there too around 1999~2000. > There were a bunch of geniuses there, but the way I understand it, geniuses produce the initial spark, but you need strong-willed, perseverent people to kindle the project there-after. > > The reason I was drawn to Pharo is because of what Ducasse and you and others like you have done with the core spark of Smalltalk-80 based Squeak running Morphic. Though, I've always liked the MVC environment more and fell in love with the "Third-Way" project to deliver a full-blown widget-set for MVC developed by a guy called Gartner (I think) from Germany. > Do you have a pointer? > Can you elaborate on your feedback-loop *inside* the system idea? Especially in the context of Pharo? > So your âSystems which evolve over time need to have a very tiny core which is supremely malleableâ I actually think is very true.. and Pharo clearly is not there yet. (and what that even is supposed to be.. has many answers). But what we technical people are the quickly to say âa malleable system needs a very tiny core, so letâs first do thatâ. And abandon what we have. But if you step back, for the end-âuserâ (that is programmer) it would not change much, it would solve nothing on that level of the problem of how to evolve a platform *and* the systems using it. Which might be even harder to do right than the kernel... Another aspect is that âlets build the perfect evolvable systemâ is as impossible as âlets build the perfect systemââ¦ when you are done, you realise that you could do even better! Marcus

Feb. 10, 2022

Re: What am I doing wrong with Spec2 in Pharo 9?

by Kasper Osterbye

It might be something else, but the browser to the left is looking at the instance side, whereas the browser to the right is looking at the class side. Hence, your class side method openAttributeEditorOn: do not know about the instance side method valueAtColumn:row: It is hard to guess from your code, but I guess you need to capture the table instance in the double click and pass that to the class side, or implement the openAttributeEditorOn: on the instance side to give access self on the instance side. Best, Kasper > On 10 Feb 2022, at 12.27, Robert Briggs via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > I have a subclass of SpTablePresenter which correctly displays a list of items. It is set up to activateOnDoubleClick as I want to open another SpPresenter I have created on the selected table row using the value in the first column to complete the presenter. My SpTablePresenter headed Element Attributes is shown bottom left in the attached screenshot. > > The class method top right reports that valueAtColumn:row: is sent but not implemented and yet it clearly is implemented by the superclass of my presenter (and I have used the method elsewhere in my project (NB: this method is just an instrument at the moment so that I can check what is happening. > > Double clicking a table row executes the method openAttributeEditorOn: but the debugger reports instance of my presenter class did not understand valueAtColumn:row: > > > So what am I doing wrong here? > > Advice please. > > Regards > Bob Briggs > > > > <PharoScreenshot.2.png>

Feb. 10, 2022

Re: Sharing and publishing Pharo powered data stories

by Offray Vladimir Luna CÃ¡rdenas

Hi again, Something happen with the foreground/background colors. So here it comes again. ================ Hi, We are combining Markdeep and STON in a light format to share and publish Pharo powered data stories and visualizations written/crafted in Glamorous Toolkit's Lepiter. In this link you can find a demo of the published output, that, of course can be imported back to Lepiter: https://mutabit.com/repos.fossil/malleable-systems/doc/trunk/wiki/en/mallea… And below you can find a preview of this data story. Our light format have some differential values over other popular data stories publishing formats, like Jupyter Notebook: a) Its human and browser readable, in contrast IPynb JSON and Python exports are readable by one, but not the other. b) it only requires (3mb) Fossil + (350K) Markdeep to be stored, versioned, shared and published. Other DVCS, web folders can be used and is a big contrast with complicated and/or oligopolistic support to make a format (Ipynb) web renderable. c) The same published document can be imported back to Lepiter. When a Jupyter document is published as HTML, it can not be imported back from there to Jupyter (I imagine something similar happens with RStudio or OrgMode, but I have not experienced data workflows on the last tools by myself). And here is the respective Nitter/Twitter thread with details and alternative narrative: https://nitter.net/offrayLC/status/1490130769603444742#m <https://nitter.net/offrayLC/status/1490130769603444742#m> Cheers, Offray https://i.imgur.com/GhbaSZc.png On 8/02/22 16:19, Offray Vladimir Luna CÃ¡rdenas wrote: > > Hi, > > We are combining Markdeep and STON in a light format to share and > publish Pharo powered data stories and visualizations written/crafted > in Glamorous Toolkit's Lepiter. In this link you can find a demo of > the published output, that, of course can be imported back to Lepiter: > > https://mutabit.com/repos.fossil/malleable-systems/doc/trunk/wiki/en/mallea… > > And below you can find a preview of this data story. > > Our light format have some differential values over other popular data > stories publishing formats, like Jupyter Notebook: > > a) Its human and browser readable, in contrast IPynb JSON and Python > exports are readable by one, but not the other. b) it only requires > (3mb) Fossil + (350K) Markdeep to be stored, versioned, shared and > published. Other DVCS, web folders can be used and is a big contrast > with complicated and/or oligopolistic support to make a format (Ipynb) > web renderable. c) The same published document can be imported back to > Lepiter. When a Jupyter document is published as HTML, it can not be > imported back from there to Jupyter (I imagine something similar > happens with RStudio or OrgMode, but I have not experienced data > workflows on the last tools by myself). > > And here is the respective Nitter/Twitter thread with details and > alternative narrative: > https://nitter.net/offrayLC/status/1490130769603444742#m > <https://nitter.net/offrayLC/status/1490130769603444742#m> > > Cheers, > > Offray > > https://i.imgur.com/GhbaSZc.png >

Feb. 10, 2022

internship grant / offre de stage de Master

by Pierre Bommel

Dear all, (see French and Spanish version below) We offer a grant to work on Pharo at Cirad <https://www.cirad.fr/nous-connaitre/unites-de-recherche/savoirs-environneme…> in the SENS research unit (https://umr-sens.fr) So we are looking for a Master student to work for 6 or 8 months on Cormas <https://github.com/cormas/cormas>, a simulation platform (see here for our presentation <https://hackmd.iscpif.fr/GGwvzBFqRASE5zCzlRwArQ?view> at ESUG). The title of this internship is "*Participatory simulation of renewable resource management in hybrid environments*" (see announcement here <https://www.hdigitag.fr/en/digitag-master2-internship-offers/>) We wish to investigate the possibilities offered by new applications related to the detection of physical objects. This detection will then be used for hybrid simulations allowing participants to interact with a model by placing different objects on a game board. It is thus a new hybrid form of games, between computer simulator and role-playing game. This work is part of an original modeling approach called ComMod <https://www.commod.org/en> (for Companion Modeling). This work will require the development of reliable detection methods for physical objects that can then be integrated into a simulator. *Participatory simulation of renewable resource management in hybrid environments* Â Â Â Keywords: Participatory simulation, Computer Vision , Smalltalk, Cormas Â Â Â Duration: 8 months Â Â Â Desired start date: 03/2022 Â Â Â Research Unit: SENS, Cirad Â Â Â Contact: Bommel Pierre â bommel(a)cirad.fr Â Â Â #DigitAg: Axe 2,Axe 6 â Challenge 1,Challenge 2 ,Challenge 6 ,Challenge 7, Challenge 8 Â Â Â *** FranÃ§ais *** Nous disposons d'une bourse pour travailler sur Pharo au Cirad <https://www.cirad.fr/nous-connaitre/unites-de-recherche/savoirs-environneme…> dans l'UR SENS (https://umr-sens.fr) Nous recherchons donc un Ã©tudiant en master pour travailler pendant 6 ou 8 mois sur Cormas <https://github.com/cormas/cormas>, une plateforme de simulation (Voir notrepresentation <https://hackmd.iscpif.fr/GGwvzBFqRASE5zCzlRwArQ?view> Ã ESUG). Le titre de ce stage est "*Simulation participative de la gestion des ressources renouvelables dans des environnements hybrides*" (voir l'annonce ici <https://www.hdigitag.fr/fr/les-offres-de-stage-digitag/>). Nous souhaitons investiguer les possibilitÃ©s offertes par les nouvelles applications liÃ©es Ã la dÃ©tection dâobjets physiques. Cette dÃ©tection servira alors pour des simulations hybrides permettant Ã des participants d'interagir avec un modÃ¨le en plaÃ§ant diffÃ©rents objets sur un plateau de jeu. Il s'agit donc d'une nouvelle forme hybride de jeux, entre simulateur informatique et jeu de rÃ´le. Ce travail s'inscrit dans une dÃ©marche originale de modÃ©lisation dite ComMod <https://www.commod.org/en> (pour ModÃ©lisation d'Accompagnement). Ce travail nÃ©cessitera de mettre au point des mÃ©thodes de dÃ©tection fiables dâobjets physiques qui pourront alors Ãªtre intÃ©grÃ©s dans le simulateur. Â Â Â *** EspaÃ±ol *** Tenemos una beca para trabajar con Pharo en el Cirad <https://www.cirad.fr/nous-connaitre/unites-de-recherche/savoirs-environneme…> en la unidad de investigaciÃ³n SENS (https://umr-sens.fr) AsÃ que estamos buscando un estudiante de Master para trabajar durante 6 u 8 meses en Cormas <https://github.com/cormas/cormas>, una plataforma de simulaciÃ³n (ver aquÃ nuestra presentaciÃ³n <https://hackmd.iscpif.fr/GGwvzBFqRASE5zCzlRwArQ?view> a ESUG). El tÃtulo de esta pasantÃa es "*SimulaciÃ³n participativa de la gestiÃ³n de recursos renovables en entornos hÃbridos*". Queremos investigar las posibilidades que ofrecen las nuevas aplicaciones relacionadas con la detecciÃ³n de objetos fÃsicos. Esta detecciÃ³n se utilizarÃ¡ despuÃ©s para realizar simulaciones hÃbridas que permitan a los participantes interactuar con un modelo colocando diferentes objetos en un tablero de juego. Se trata, pues, de una nueva forma hÃbrida de juegos, entre simulador informÃ¡tico y juego de rol. Este trabajo forma parte de un enfoque original de modelizaciÃ³n llamado ComMod (para ModelaciÃ³n de AcompaÃ±amento). Este trabajo requerirÃ¡ el desarrollo de mÃ©todos fiables de detecciÃ³n de objetos fÃsicos que puedan integrarse en un simulador. Â Â Â Pierre BOMMEL Â Â Â CIRAD - UMR SENS http://umr-sens.fr/

Feb. 10, 2022

What am I doing wrong with Spec2 in Pharo 9?

by Robert Briggs

I haveÂ a subclass of SpTablePresenter which correctly displays a list of items.Â It is set up to activateOnDoubleClick as I want to open another SpPresenter I have created on the selected table row using the value in the first column to complete the presenter.Â My SpTablePresenter headed Element Attributes is shown bottom left in the attached screenshot. The class method top right reports that valueAtColumn:row: is sent but not implemented and yet it clearly is implemented by the superclass of my presenter (and I have used the method elsewhere in my project (NB: this method is just an instrument at the moment so that I can check what is happening. Double clicking a table row executes the method openAttributeEditorOn:Â but the debugger reports instance of my presenter class did not understand valueAtColumn:row: So what am I doing wrong here? Advice please. Regards Bob Briggs

Feb. 10, 2022

Re: Error when running OSUnixSubprocess - posix_spawn() error

by bajger＠gmail.com

Hi Guille, Thanks for your reply! The problem is not permanent, so I cannot reproduce now :( It usually happens (not always) with fresh image of launcher (after loading Launcher project). Is seems that some file keeps hanging that causes that error. I will confirm if evaluating command directly produce same error, if I will experience this again.

Feb. 9, 2022

Re: Error when running OSUnixSubprocess - posix_spawn() error

by Guillermo Polito

Hi David, What is the function that is actually failing? I would assume itâs something called in #internalRun. I assume you have tried executing the process from the command line (quick check I always do when finding these kind of problems :P). $ echo -n $(pgrep -a -f Pharo | grep ''.image'' | grep -v ''.bash''| grep -v XXX) G > El 4 feb 2022, a las 17:48, bajger(a)gmail.com escribiÃ³: > > Greetings Pharoers! > > I have following problem when using OSSubprocess library. If I run a method that uses code below, it fails: Error: Error: posix_spawn(), code: 9, description: Bad file descriptor > > Any thoughts, hints are welcome! > > My code redirects stdout, stdin in order to catch system outputs from inside of Pharo. > > Subprocess code does following: > OSUnixSubprocess>>runAndWaitWithStdOutput > self > redirectStdout; > redirectStderr; > runAndWaitOnExitDo: [ :termProcess :outString :errString | > termProcess isSuccess > ifTrue: [ ^ outString ] > ifFalse: [ "commands to handle ex message here" ] ] > > Now if I run, it fails: > > Error: Error: posix_spawn(), code: 9, description: Bad file descriptor > OSSUnixSystemAccessor(Object)>>error: > OSSUnixSystemAccessor>>strerror:message: > OSSUnixSubprocess>>internalRun > [ self internalRun ] in OSSUnixSubprocess>>run in Block: [ self internalRun ] > BlockClosure>>ensure: > OSSUnixSubprocess>>run > OSSUnixSubprocess>>runAndWaitOnExitDo: > OSSUnixSubprocess>>runAndWaitWithStdOutput > ... > .. > . > PhLImageProcessListCliCommand(PhLCliCommand)>>executeOSShellCommand > > So it seems that OSUnixSubprocess uses some file that remains opened probably in OS? > Command that is passed to OSSubprocess is generated by args: > ^ Array with: 'echo' with: '-n' with: ('$(pgrep -a -f Pharo | grep ''.image'' | grep -v ''.bash''| grep -v {1})' format: {self currentVMPid asString})

Feb. 9, 2022

Sharing and publishing Pharo powered data stories

by Offray Vladimir Luna CÃ¡rdenas

Hi, We are combining Markdeep and STON in a light format to share and publish Pharo powered data stories and visualizations written/crafted in Glamorous Toolkit's Lepiter. In this link you can find a demo of the published output, that, of course can be imported back to Lepiter: https://mutabit.com/repos.fossil/malleable-systems/doc/trunk/wiki/en/mallea… And below you can find a preview of this data story. Our light format have some differential values over other popular data stories publishing formats, like Jupyter Notebook: a) Its human and browser readable, in contrast IPynb JSON and Python exports are readable by one, but not the other. b) it only requires (3mb) Fossil + (350K) Markdeep to be stored, versioned, shared and published. Other DVCS, web folders can be used and is a big contrast with complicated and/or oligopolistic support to make a format (Ipynb) web renderable. c) The same published document can be imported back to Lepiter. When a Jupyter document is published as HTML, it can not be imported back from there to Jupyter (I imagine something similar happens with RStudio or OrgMode, but I have not experienced data workflows on the last tools by myself). And here is the respective Nitter/Twitter thread with details and alternative narrative: https://nitter.net/offrayLC/status/1490130769603444742#m <https://nitter.net/offrayLC/status/1490130769603444742#m> Cheers, Offray https://i.imgur.com/GhbaSZc.png

Feb. 8, 2022

Pharo GSoC 2022 call for projects

by Sebastian Jordan Montano

Hello to all, We, as Pharo organization, are appliying to the Google Summer of Code (GSoC) 2022 version. More info in: https://summerofcode.withgoogle.com/ >From GSoC Page: "Google Summer of Code is a global, online program focused on bringing new contributors into open source software development. GSoC Contributors work with an open source organization on a 12+ week programming project under the guidance of mentors." Now we are preparing to postulate. We would like to have the most projects as possible. Like that, we will contribute to Pharo and to Open Source in general. If you have any project and you are willing to be a mentor please send us your proposal! We would be happy to work with you. Yours sincerely, Sebastian Jordan GSoC Program Organizer from Pharo Consortium

Feb. 8, 2022

[ANN] Announcing the Winner of the 2022 JRMPC Competition

by horrido.hobbies＠gmail.com

I am pleased to announce the winner of this year's JRMPC competition. The judges reviewed all the submissions and came to the extraordinary decision that onlyÂ **Ana DuCristea**Â of John G. Diefenbaker High School in Calgary, AB was worthy of an award. Her work was outstanding and constituted enormous dedication and enthusiasm for Smalltalk. Unfortunately, none of the other contestants rose to the occasion and there will be no Second or Third Prizes. Therefore, it is my decision that Ana DuCristea will receive the full prize fund of $2,500. My most heart-felt congratulations to Ana. Well done!

Feb. 7, 2022

First Call for Papers: 15th ACM SIGPLAN International Conference on Software Language Engineering (SLE 2022)

by Andrei Chis

------------------------------------------------------------------------ 15th ACM SIGPLAN International Conference on Software Language Engineering (SLE 2022) December 5-10, 2022 Auckland, New Zealand https://conf.researchr.org/home/sle-2022 http://www.sleconf.org/2022 Follow us on twitter: https://twitter.com/sleconf ------------------------------------------------------------------------ We are pleased to invite you to submit papers to the 15th ACM SIGPLAN International Conference on Software Language Engineering (SLE 2022), held in conjunction with SPLASH, GPCE and SAS 2022. Based on the future developments the conference will be hosted in Auckland, New Zealand on December 5-10, 2022. --------------------------- Topics of Interest --------------------------- SLE covers software language engineering rather than engineering a specific software language. Topics of interest include, but are not limited to: - Software Language Design and Implementation - Approaches to and methods for language design - Static semantics (e.g. design rules, well-formedness constraints) - Techniques for specifying behavioral / executable semantics - Generative approaches (incl. code synthesis, compilation) - Meta-languages, meta-tools, language workbenches - Software Language Validation - Verification and formal methods for languages - Testing techniques for languages - Simulation techniques for languages - Software Language Integration and Composition - Coordination of heterogeneous languages and tools - Mappings between languages (incl. transformation languages) - Traceability between languages - Deployment of languages to different platforms - Software Language Maintenance - Software language reuse - Language evolution - Language families and variability, language and software product lines - Domain-specific approaches for any aspects of SLE (design, implementation, validation, maintenance) - Empirical evaluation and experience reports of language engineering tools - User studies evaluating usability - Performance benchmarks - Industrial applications - "Synergies between Language Engineering and emerging/promising research areas" - AI and ML language engineering (e.g., ML compiler testing, code classification) Quantum language engineering (e.g., language design for quantum machines) - Language engineering for physical systems (e.g., CPS, IoT, digital twins) - Socio-technical systems and language engineering (e.g., language evolution to adapt to social requirements) - Etc. --------------------------- Types of Submissions --------------------------- SLE accepts the following types of papers: - **Research papers**: These are "traditional" papers detailing research contributions to SLE. Papers may range from 6 to 12 pages in length, and may optionally include 2 further pages of bibliography/appendices. Papers will be reviewed with an understanding that some results do not need 12 full pages and may be fully described in fewer pages. - **New ideas / vision papers**: These are papers that may describe new, unconventional software language engineering research positions or approaches that depart from standard practice. They can describe well-defined research ideas that are at an early stage of investigation. They could also provide new evidence to challenge common wisdom, present new unifying theories about existing SLE research that provides novel insight or that can lead to the development of new technologies or approaches, or apply SLE technology to radically new application areas. New ideas / vision papers must not exceed 5 pages, and may optionally include 1 further page of bibliography / appendices. - **SLE Body of Knowledge**: The SLE Body of Knowledge (SLEBoK) is a community-wide effort to provide a unique and comprehensive description of the concepts, best practices, tools and methods developed by the SLE community. To this respect, the SLE conference will accept surveys, essays, open challenges, empirical observations and case study papers on the SLE topics. These can focus on but they are not limited to methods, techniques, best practices and teaching approaches. Papers in this category can have up to 20 pages, including bibliography/appendices. - **Tool papers**: These are papers which focus on the tooling aspects which are often forgotten or neglected in research papers. A good tool paper focuses on practical insights that are likely to be useful to other implementers or users in the future. Any of the SLE topics of interest are appropriate areas for tool demonstrations. Submissions must not exceed 5 pages and may optionally include 1 further page of bibliography / appendices. They may optionally come with an appendix with a demo outline / screenshots and/or a short video/screencast illustrating the tool. **Workshops**: Workshops will be organized by SPLASH. Please inform us and contact the SPLASH organizers if you would like to organize a workshop of interest to the SLE audience. Information on how to submit workshops can be found at the SPLASH 2022 Website. --------------------------- Two submission rounds --------------------------- For the first time, SLE is introducing a two-phase submission and review process. This will give authors submitting to the first round an extra opportunity to improve their work (if needed) based on the comments and feedback by the reviewers. Furthermore, this will increase the quality of SLE accepted papers. Manuscripts can be submitted to any of the two submission rounds. Decisions on the papers submitted to the **first round** will be: accept, reject or re-submit revised version. While rejected papers must not, revised versions may be submitted to the second round, with an accompanying response letter to the reviewers stating the changes made and how the authors addressed the reviewersâ criticisms. Re-submissions will be reviewed by the same reviewers. Decisions on fresh papers submitted to the **second round** will be: accept or reject. The authors of those papers that are likely to be rejected but have at least one reviewer who is championing it will have the chance to respond to the reviewers before the final decision is made. --------------------------- Important Dates --------------------------- All dates are Anywhere on Earth. * 1st round submissions * Abstract submissions: April 6, 2022 * Paper submissions: April 13, 2022 * Notification: May 13, 2022 * 2nd round submissions * Abstract submissions: July 8, 2022 (tentative) * Paper submissions: July 15, 2022 (tentative) * Review notification: September 7, 2022 (tentative) * Author response period: September 12, 2022 (tentative) * Notification: September 19, 2022 (tentative) * Artifact submissions: September 26, 2022 (tentative) * Artifact kick-the-tires Author response: October 10, 2022 (tentative) * Artifact notification: October 24, 2022 (tentative) * Camera-ready (for both rounds): November 4, 2022 (tentative) * Conference: December 5-10, 2022 (TENTATIVE) **COVID-19 Disclaimer** Due to the uncertainties related to the current COVID-19 pandemic, the second round submission deadlines, the artifact evaluation deadlines, the camera-ready deadline and the conference dates are still *preliminary* and will be closed in the next few weeks. --------------------------- Format --------------------------- Submissions have to use the ACM SIGPLAN Conference Format "acmart"(http://sigplan.org/Resources/Author/#acmart-format) please make sure that you always use the latest ACM SIGPLAN acmart LaTeX template(https://www.acm.org/binaries/content/assets/publications/consolida…, and that the document class definition is `\documentclass[sigplan,anonymous,review]{acmart}`. Do not make any changes to this format! Ensure that your submission is legible when printed on a black and white printer. In particular, please check that colors remain distinct and font sizes in figures and tables are legible. To increase fairness in reviewing, a double-blind review process has become standard across SIGPLAN conferences. In this line, SLE will follow the double-blind process. Author names and institutions should be omitted from submitted papers, and references to the authorsâ own related work should be in the third person. No other changes are necessary, and authors will not be penalized if reviewers are able to infer their identities in implicit ways. All submissions must be in PDF format. The submission website is: https://sle22.hotcrp.com --------------------------- Concurrent Submissions --------------------------- Papers must describe unpublished work that is not currently submitted for publication elsewhere as described by SIGPLANâs Republication Policy (http://www.sigplan.org/Resources/Policies/Republication) Submitters should also be aware of ACMâs Policy and Procedures on Plagiarism (http://www.acm.org/publications/policies/plagiarism_policy) Submissions that violate these policies will be desk-rejected. --------------------------- Policy on Human Participant and Subject Research --------------------------- Authors conducting research involving human participants and subjects must ensure that their research comply with their local governing laws and regulations and the ACMâs general principles as stated in the ACMâs Publications Policy on Research Involving Human Participants and Subjects (https://www.acm.org/publications/policies/research-involving-human-particip…) Submissions that violate this policy will be rejected. --------------------------- Reviewing Process --------------------------- All submitted papers will be reviewed by at least three members of the program committee. Research papers and tool papers will be evaluated concerning novelty, correctness, significance, readability, and alignment with the conference call. New ideas/vision papers will be evaluated primarily concerning novelty, significance, readability, and alignment with the conference call. SLEBoK papers will be reviewed on their significance, readability, topicality and capacity of presenting/evaluating/demonstrating a piece of BoK about SLE. For fairness reasons, all submitted papers must conform to the above instructions. Submissions that violate these instructions may be rejected without review, at the discretion of the PC chairs. After each review round, authors will get a chance to respond before a final decision is made. --------------------------- Artifact Evaluation --------------------------- For the seventh year, SLE will use an evaluation process for assessing the quality of the artifacts on which papers are based to foster the culture of experimental reproducibility. Authors of accepted research papers are invited to submit artifacts. For more information, please have a look at the Artifact Evaluation (http://www.sleconf.org/2022/ArtifactEvaluation.html) page. --------------------------- Special Issue --------------------------- A special issue on the conference topic in a high-impact journal is under negotiation. --------------------------- Awards --------------------------- - **Distinguished paper**: Award for most notable paper, as determined by the PC chairs based on the recommendations of the programme committee. - **Distinguished artifact**: Award for the artifact most significantly exceeding expectations, as determined by the AEC chairs based on the recommendations of the artifact evaluation committee. --------------------------- Publication --------------------------- All accepted papers will be published in the ACM Digital Library. **AUTHORS TAKE NOTE**: The official publication date is the date the proceedings are made available in the ACM Digital Library. This date may be up to two weeks prior to the first day of the conference. The official publication date affects the deadline for any patent filings related to published work. --------------------------- SLE and Doctoral Students --------------------------- SLE encourages students to submit to the SPLASH doctoral symposium. Authors of accepted papers will have the chance to present their work to the SLE audience, too. --------------------------- Organisation --------------------------- Chairs: * General chair: Bernd Fischer, Stellenbosch University, South Africa * PC co-chair: Lola BurgueÃ±o, Open University of Catalonia, Spain * PC co-chair: Walter Cazzola, UniversitÃ degli Studi di Milano, Italy * Artefact Evaluation co-chair: Thomas KÃ¼hn, Karlsruhe Institute of Technology, Germany * Artefact Evaluation co-chair: Juliana A. Pereira, Pontifical Catholic University of Rio de Janeiro, Brazil Program committee: Shaukat Ali, Simula Research Laboratory, Norway Arvid Butting, Aachen University, Germany Marsha Chechik, University of Toronto, Canada Shigeru Chiba, University of Tokyo, Japan BenoÃ®t Combemale, University of Rennes, France Zhenjiang Hu, Peking University, China JÃ¶rg Kienzle, McGill University, Canada Dimitris Kolovos, University of York, UK Thomas KÃ¼hn, Karlsruhe Institute of Technology, Germany Juan de Lara, Universidad AutÃ³noma de Madrid, Spain Stefan Marr, University of Kent, UK Marjan Mernik, University of Maribor, Slovenia Natsuko Noda, Shibaura Institute of Technology, Japan Juliana A. Pereira, Pontifical Catholic University of Rio de Janeiro, Brazil Elizabeth Scott, University of London, UK Marco Servetto, Victoria University of Wellington, New Zealand Emma SÃ¶derberg, Lund University, Sweden Walid Taha, Halmstad University , Sweden Marco Tullio Valente, Universidade Federal de Minas Gerais, Brazil Erik Van Wyk, University of Minnesota , USA Alfonso de la Vega, University of Cantabria, Spain Ran Wei, Dalian University of Technology, China Andreas Wortmann, Stuttgart University, Germany Vadim Zaytsev, University of Twente, Netherlands Steffen Zschaler, Kingâs College London, UK --------------------------- Contact --------------------------- For additional information, clarification, or answers to questions, please contact the Programme Chairs (Lola BurgueÃ±o and Walter Cazzola) at sle22-chairs _at_ di.unimi.it.

Feb. 7, 2022

[Issue tracker] Please check your older issues

by Marcus Denker

Hi, We are seeing lots of issue that are still open, but already fixed or just not valid anymore. e.g. - the fix that was merged but the issue was not closed (sometimes GitHub has problems doing that) - Bug was fixed independent of the issue - The issue is just not relevant anymore It is often quite time consuming to even find out that an issue is already fixedâ¦ It would be nice if everyone could check the issues that - you submitted yourself - that are assigned to you - [Bonus] where you were part of some discussion https://github.com/pharo-project/pharo/issues Marcus

Feb. 7, 2022

Re: aio event forwarding not supported

by Davide Varvello

Workaround!!! Here I am again. I found a workaround for theÂ PipeableOSProcess and the Big Sur update. It is the usage of LibC, I was not aware of that class, it's useful. I was able to reproduce my logic with LibC, this article (https://fuhrmanator.github.io/2019/03/16/LibC-Pharo-experiments.html) is recommended. Cheers Davide

Feb. 7, 2022

Re: [Pharo-users] Re: What is "Fluid"?

by contactme＠kathe.in

On Monday, February 07, 2022 09:31 CET, Marcus Denker <marcus.denker(a)inria.fr> wrote: Â Â Â On 7 Feb 2022, at 09:10, contactme(a)kathe.in wrote:Â On Monday, February 07, 2022 08:57 CET, Marcus Denker <marcus.denker(a)inria.fr> wrote: Â > On 7 Feb 2022, at 08:41, contactme(a)kathe.in wrote: > > Hello Marcus, > > Thanks for responding with thorough details, but I'm not such a good OO programmer, so what I need to know is; > Will we be able to continue developing with Pharo using the same old Smalltalk-like syntax? Or, will there be major changes some time in the future? Like how (I think) "_" from Squeak was replaced with ":=" in Pharo! > := is I think even ANSI Standard, or not? There are no plans for syntactical changesâ¦ But of course: The *goal* of Pharo is not to be Smalltalk80. I have to admit I kind of misunderstood Squeak back thenâ¦ I really thought the idea if was to take ST80 as a startingoint âto invent the futureââ¦ I still like that idea, I have to sayâ¦ to me what fascinates me is how to take something that is as of a great idea as ST80 and improve itâ¦ for example just consider the resources (in terms of memory or processing power or networking) we have today vs. 1978. The âletâs through it all away and start from scratchâ approach is not great, eitherâ¦ as you need something to buld upon. And: as soon as you finish that âbetterâ system, you would have the same problem: you would be stuck with a âfinishedâ system, while the world continues to evolve. It is a real interesting research question: How an you build Systems that can evolve over a long time ? Systems which evolve over time need to have a very tiny core which is supremely malleable. For one, I would start with a "Forth" and add an object-system to it using the "Metaobject Protocol" along with a Common Lisp like "Condition System". Â Â Forth in the context of the core of an object system is interestingâ¦ someone did in 1979 a Smalltalk and Forth inspired system called âRosetta Smalltalk"Â https://dl.acm.org/doi/10.1145/1113572.1113555Â But: the nice thing of evolving a system is that you *always* can show a real, working result. You can have users, including yourselfâ¦ you can find ways of financingÂ your work that is not just promising something for the future. (which you can only do so often before people get sceptical).Â I think being part of the early Squeak community kind of burned for me the âletâs not improve that (relatively) simple thing A, instead wait for <genius X> to finish <amazing Project Z>.Â Imagine instead you would build a feedback-loop *inside* of your system...Â Â Marcus Agree about what you felt within the Squeak community, I was there too around 1999~2000. There were a bunch of geniuses there, but the way I understand it, geniuses produce the initial spark, but you need strong-willed, perseverent people to kindle the project there-after. The reason I was drawn to Pharo is because of what Ducasse and you and others like you have done with the core spark of Smalltalk-80 based Squeak running Morphic. Though, I've always liked the MVC environment more and fell in love with the "Third-Way" project to deliver a full-blown widget-set for MVC developed by a guy called Gartner (I think) from Germany. Can you elaborate on your feedback-loop *inside* the system idea? Especially in the context of Pharo? Â

Feb. 7, 2022

Re: What is "Fluid"?

by Marcus Denker

> On 7 Feb 2022, at 09:10, contactme(a)kathe.in wrote: > > > On Monday, February 07, 2022 08:57 CET, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> >> >> >> > On 7 Feb 2022, at 08:41, contactme(a)kathe.in wrote: >> > >> > Hello Marcus, >> > >> > Thanks for responding with thorough details, but I'm not such a good OO programmer, so what I need to know is; >> > Will we be able to continue developing with Pharo using the same old Smalltalk-like syntax? Or, will there be major changes some time in the future? Like how (I think) "_" from Squeak was replaced with ":=" in Pharo! >> > >> := is I think even ANSI Standard, or not? >> >> There are no plans for syntactical changesâ¦ >> >> But of course: The *goal* of Pharo is not to be Smalltalk80. >> >> I have to admit I kind of misunderstood Squeak back thenâ¦ >> >> I really thought the idea if was to take ST80 as a startingoint âto invent the futureââ¦ >> I still like that idea, I have to sayâ¦ to me what fascinates me is how to take something >> that is as of a great idea as ST80 and improve itâ¦ for example just consider the resources (in terms >> of memory or processing power or networking) we have today vs. 1978. >> >> The âletâs through it all away and start from scratchâ approach is not great, eitherâ¦ as you need something to buld >> upon. And: as soon as you finish that âbetterâ system, you would have the same problem: you would be stuck with >> a âfinishedâ system, while the world continues to evolve. >> >> It is a real interesting research question: How an you build Systems that can evolve over a long time ? > > Systems which evolve over time need to have a very tiny core which is supremely malleable. > For one, I would start with a "Forth" and add an object-system to it using the "Metaobject Protocol" along with a Common Lisp like "Condition System". > Forth in the context of the core of an object system is interestingâ¦ someone did in 1979 a Smalltalk and Forth inspired system called âRosetta Smalltalk" https://dl.acm.org/doi/10.1145/1113572.1113555 <https://dl.acm.org/doi/10.1145/1113572.1113555> But: the nice thing of evolving a system is that you *always* can show a real, working result. You can have users, including yourselfâ¦ you can find ways of financing your work that is not just promising something for the future. (which you can only do so often before people get sceptical). I think being part of the early Squeak community kind of burned for me the âletâs not improve that (relatively) simple thing A, instead wait for <genius X> to finish <amazing Project Z>. Imagine instead you would build a feedback-loop *inside* of your system... Marcus

Feb. 7, 2022

Re: [Pharo-users] Re: What is "Fluid"?

by contactme＠kathe.in

On Monday, February 07, 2022 08:57 CET, Marcus Denker <marcus.denker(a)inria.fr> wrote: Â > On 7 Feb 2022, at 08:41, contactme(a)kathe.in wrote: > > Hello Marcus, > > Thanks for responding with thorough details, but I'm not such a good OO programmer, so what I need to know is; > Will we be able to continue developing with Pharo using the same old Smalltalk-like syntax? Or, will there be major changes some time in the future? Like how (I think) "_" from Squeak was replaced with ":=" in Pharo! > := is I think even ANSI Standard, or not? There are no plans for syntactical changesâ¦ But of course: The *goal* of Pharo is not to be Smalltalk80. I have to admit I kind of misunderstood Squeak back thenâ¦ I really thought the idea if was to take ST80 as a startingoint âto invent the futureââ¦ I still like that idea, I have to sayâ¦ to me what fascinates me is how to take something that is as of a great idea as ST80 and improve itâ¦ for example just consider the resources (in terms of memory or processing power or networking) we have today vs. 1978. The âletâs through it all away and start from scratchâ approach is not great, eitherâ¦ as you need something to buld upon. And: as soon as you finish that âbetterâ system, you would have the same problem: you would be stuck with a âfinishedâ system, while the world continues to evolve. It is a real interesting research question: How an you build Systems that can evolve over a long time ? Systems which evolve over time need to have a very tiny core which is supremely malleable. For one, I would start with a "Forth" and add an object-system to it using the "Metaobject Protocol" along with a Common Lisp like "Condition System". Â

Feb. 7, 2022

Re: What is "Fluid"?

by Marcus Denker

> On 7 Feb 2022, at 08:41, contactme(a)kathe.in wrote: > > Hello Marcus, > > Thanks for responding with thorough details, but I'm not such a good OO programmer, so what I need to know is; > Will we be able to continue developing with Pharo using the same old Smalltalk-like syntax? Or, will there be major changes some time in the future? Like how (I think) "_" from Squeak was replaced with ":=" in Pharo! > := is I think even ANSI Standard, or not? There are no plans for syntactical changesâ¦ But of course: The *goal* of Pharo is not to be Smalltalk80. I have to admit I kind of misunderstood Squeak back thenâ¦ I really thought the idea if was to take ST80 as a startingoint âto invent the futureââ¦ I still like that idea, I have to sayâ¦ to me what fascinates me is how to take something that is as of a great idea as ST80 and improve itâ¦ for example just consider the resources (in terms of memory or processing power or networking) we have today vs. 1978. The âletâs through it all away and start from scratchâ approach is not great, eitherâ¦ as you need something to buld upon. And: as soon as you finish that âbetterâ system, you would have the same problem: you would be stuck with a âfinishedâ system, while the world continues to evolve. It is a real interesting research question: How an you build Systems that can evolve over a long time ? Marcus

Feb. 7, 2022

Re: [Pharo-users] Re: What is "Fluid"?

by contactme＠kathe.in

Hello Marcus, Thanks for responding with thorough details, but I'm not such a good OO programmer, so what I need to know is; Will we be able to continue developing with Pharo using the same old Smalltalk-like syntax? Or, will there be major changes some time in the future? Like how (I think) "_" from Squeak was replaced with ":=" in Pharo! Thank you. On Wednesday, February 02, 2022 10:50 CET, Marcus Denker <marcus.denker(a)inria.fr> wrote: Â > On 2 Feb 2022, at 09:04, contactme(a)kathe.in wrote: > > I have attached 2 cropped screen-captures of the same class displayed in the class browser; > class-smalltalk.png is the regular class syntax, > class-fluid.png is the same class but with the "Fluid" checkbox selected, and shows a different syntax. > This is no different syntax, as there is no Syntax (in the sense of Grammar) to define classes. These are all message sends, just like before. > May I know what that is all about? > > There's a different terminology too, something called "slot", which I have faint memories of being quite like that in "Self" environments. > The Fluid class definition has two goals: 1) be extensible. With the ST80 way, any new parameter would mean adding *a lot* of methods. And every new parameter needs all the other variations, itâs a serious combinatorial explosion. Just an example: CompiledMethods and CompiledBlock use CompiledMethodLayout. But they are created with: CompiledCode variableByteSubclass: #CompiledMethod instanceVariableNames: '' classVariableNames: '' package: 'Kernel-Methods' So the system checks for the name and uses the CompiledMethodLayout instead of ByteLayout. This is hacked in to the system really with âif the name is CompiledMethod, do not use ByteLayout but CompiledMethodLayout.â But now CompiledCode classLayout ==> "a CompiledMethodLayoutâ Which means yes, we have a class that we can not define! With the new class definition, this is explicit: CompiledCode << #CompiledBlock layout: CompiledMethodLayout; slots: {}; tag: 'Methods'; package: âKernel' Now of course we could have added ~20 methods (not sure if that is enoughâ¦) of a compiledMethodSubclass:, and added a version with the layout as a parameter (another 20+1 variants). But what if we want to add yet another parameter? What is *you* want to do that? With Fluid, class defintions are extensible, and we can easily extend them. 2) Why are variables not a list of names in a String anymore? Because we have âFirst Class Variablesâ: every variable in the system has a meta-object, which is implemented by a class. Point instanceVariables first "#x => InstanceVariableSlotâ So yes, there is an Object that represents âthe variable #x in Pointâ. With an api. The compiler delegates code generation to it fore read and write. You can think of it as a Meta Object Protocol for Variables... (I sometimes wonder if the name Slot was good, we could just think of it as âInstanceVariableâ in the sense of the Variable being modelled as an object, instead of a String). This is a big topic, but the idea is: letâs use Objects, not Strings! We can define our own kind of Variable (see the hierarchy of Variable), and the use of the array {} now allows us to actually define a class that uses this special kind of Variable. There is a presentation I did about it last year: https://vimeo.com/603398445 Marcus Â Â

Feb. 7, 2022

Re: aio event forwarding not supported

by Davide Varvello

Hi Stephane > On Saturday, February 5, 2022, 10:58:37 AM GMT+1, stephane.ducasse(a)free.fr <stephane.ducasse(a)free.fr> wrote: >Hi david > >Can you tell us on which version of os-x you are? I'm on Big Sur, see my original message:Â https://www.mail-archive.com/pharo-users@lists.pharo.org/msg40530.html And the bug I openedÂ https://pharo.fogbugz.com/f/cases/22925/aio-event-forwarding-not-supportedÂ > We faced many glitches with monterrey. For example sometimes at startup my images do not get events :( > Pablo is going on vacation for two weeks and esteban and me too :) > So we will be slower to react.Â > Now you face what we face, the world keeps changing under our feets and > this brings us many things that we did not want/plan to work on. > This is why VMs are nice for the users they abstract the shit underneath but nevertheless it exists. > S I know it's a tough job, I'm trying to implement a workaround, thanks for your work. Davide

Feb. 5, 2022

Re: aio event forwarding not supported

by David T. Lewis

Hi David, I do not think I can help, maybe someone with Big Sur can take a look? I am on Linux. I did a fresh download of Pharo 8 and loaded OSProcess, and I cannot reproduce the problem on my system. Dave On Fri, Feb 04, 2022 at 03:54:57PM +0000, Davide Varvello via Pharo-users wrote: > Hi David,I don't think is an issue of warning, even if I apply your patch I have the same error, see: https://imgur.com/a/pYcLLWx > > > > To reproduce the bug:??Be on ??Big Sur 11.6.3 (20G415) https://support.apple.com/en-us/HT213055Download Pharo 8: curl https://get.pharo.org/64/80+vm|bash > Open the image and evaluate ina playground:Metacello new???? ?? configuration: 'OSProcess';???? ?? repository: 'http://www.squeaksource.com/MetacelloRepository';?? ?? load . > > and then > (PipeableOSProcess command: 'ps') ??output. > > The bug will show itself > CheersDavide > On Friday, February 4, 2022, 04:39:28 PM GMT+1, David T. Lewis <lewis(a)mail.msen.com> wrote: > > Hi Davide, > > Actually the warning has been removed in newer versions of OSProcess. > I do not have time to do an update for Pharo now, but in the mean time > you can apply this change in your image to remove the notifier: > > AioEventHandler>>initializeForExceptions: exceptionEventFlag readEvents: readEventFlag writeEvents: writeEventFlag > ?????? semaphore := Semaphore new. > ?????? semaIndex := Smalltalk registerExternalObject: semaphore. > ?????? (AioPluginPresent = true) ifTrue: [ > ?????? ?????? ([self aioEnable: self descriptor forSemaphore: self semaIndex externalObject: true] > ?????? ?????? ?????? on: Warning > ?????? ?????? ?????? do: [:e | > ?????? ?????? ?????? ?????? self close. "unregister the semaphore" > ?????? ?????? ?????? ?????? OSProcess trace: e messageText asString. nil]) > ?????? ?????? ?????? ifNotNil: > ?????? ?????? ?????? ?????? [handlerProc := self > ?????? ?????? ?????? ?????? ?????? handleExceptions: exceptionEventFlag > ?????? ?????? ?????? ?????? ?????? readEvents: readEventFlag > ?????? ?????? ?????? ?????? ?????? writeEvents: writeEventFlag]] > > > HTH, > Dave > > > > On Fri, Feb 04, 2022 at 03:05:57PM +0000, Davide Varvello wrote: > >?? Hi David,That's weird because if the AioPlugin is not present in my VM,??PipeableOSProcess shouldn't have worked till this morning... when I upgraded my mac :-) > > The warning is not skippable, it stops me at:??MessageNotUnderstood: IRJump>> #nextBytecodeOffsetAfterJumpCheersDavide > > > >?? ?? On Friday, February 4, 2022, 03:54:59 PM GMT+1, David T. Lewis <lewis(a)mail.msen.com> wrote:?? > >?? > >?? On Fri, Feb 04, 2022 at 01:46:46PM +0000, Davide Varvello via Pharo-users wrote: > > > Hi guys, > > > Suddenly evaluating a simple: (PipeableOSProcess command: 'ps') output, or any other PipeableOSProcess command, Pharo gives me: "aio event forwarding not supported". > > > I guess it is something related to the latest update of the OS, specifically Big Sur 11.6.3 (20G415) https://support.apple.com/en-us/HT213055I'm on a Mac, of course, Pharo 8.0.0, Build information: Pharo-8.0.0+build.1128.sha.9f6475d88dda7d83acdeeda794df35d304cf620d (64 Bit) > > > Can you help me, please?CheersDavide > > > > Hi Davide, > > > > The warning message indicates that the AioPlugin is not present > > in your VM. I do not know the reason for that, although your > > PipeableOSProcess should still work if you proceed through the > > warning. > > > > Dave > > > >?? >

Feb. 4, 2022

Error when running OSUnixSubprocess - posix_spawn() error

by bajger＠gmail.com

Greetings Pharoers! I have following problem when using OSSubprocess library. If I run a method that uses code below, it fails: Error: Error: posix_spawn(), code: 9, description: Bad file descriptor Any thoughts, hints are welcome! My code redirects stdout, stdin in order to catch system outputs from inside of Pharo. ``` Subprocess code does following: OSUnixSubprocess>>runAndWaitWithStdOutput ``` ``` self ``` ``` redirectStdout; ``` ``` redirectStderr; ``` ``` runAndWaitOnExitDo: [ :termProcess :outString :errString | ``` ``` termProcess isSuccess ``` ``` ifTrue: [ ^ outString ] ``` ``` ifFalse: [ "commands to handle ex message here" ] ] ``` ``` Now if I run, it fails: Error: Error: posix_spawn(), code: 9, description: Bad file descriptor OSSUnixSystemAccessor(Object)>>error: OSSUnixSystemAccessor>>strerror:message: OSSUnixSubprocess>>internalRun [ self internalRun ] in OSSUnixSubprocess>>run in Block: [ self internalRun ] BlockClosure>>ensure: OSSUnixSubprocess>>run OSSUnixSubprocess>>runAndWaitOnExitDo: OSSUnixSubprocess>>runAndWaitWithStdOutput ... .. . PhLImageProcessListCliCommand(PhLCliCommand)>>executeOSShellCommand So it seems that OSUnixSubprocess uses some file that remains opened probably in OS? Command that is passed to OSSubprocess is generated by args: ^ Array with: 'echo' with: '-n' with: ('$(pgrep -a -f Pharo | grep ''.image'' | grep -v ''.bash''| grep -v {1})' format: {self currentVMPid asString}) ```

Feb. 4, 2022

Re: aio event forwarding not supported

by Davide Varvello

Hi David,I don't think is an issue of warning, even if I apply your patch I have the same error, see: https://imgur.com/a/pYcLLWx To reproduce the bug:Â Be on Â Big Sur 11.6.3 (20G415) https://support.apple.com/en-us/HT213055Download Pharo 8: curl https://get.pharo.org/64/80+vm|bash Open the image and evaluate ina playground:Metacello newÂ Â Â configuration: 'OSProcess';Â Â Â repository: 'http://www.squeaksource.com/MetacelloRepository';Â Â load . and then (PipeableOSProcess command: 'ps') Â output. The bug will show itself CheersDavide On Friday, February 4, 2022, 04:39:28 PM GMT+1, David T. Lewis <lewis(a)mail.msen.com> wrote: Hi Davide, Actually the warning has been removed in newer versions of OSProcess. I do not have time to do an update for Pharo now, but in the mean time you can apply this change in your image to remove the notifier: AioEventHandler>>initializeForExceptions: exceptionEventFlag readEvents: readEventFlag writeEvents: writeEventFlag Â Â Â semaphore := Semaphore new. Â Â Â semaIndex := Smalltalk registerExternalObject: semaphore. Â Â Â (AioPluginPresent = true) ifTrue: [ Â Â Â Â Â Â ([self aioEnable: self descriptor forSemaphore: self semaIndex externalObject: true] Â Â Â Â Â Â Â Â Â on: Warning Â Â Â Â Â Â Â Â Â do: [:e | Â Â Â Â Â Â Â Â Â Â Â Â self close. "unregister the semaphore" Â Â Â Â Â Â Â Â Â Â Â Â OSProcess trace: e messageText asString. nil]) Â Â Â Â Â Â Â Â Â ifNotNil: Â Â Â Â Â Â Â Â Â Â Â Â [handlerProc := self Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â handleExceptions: exceptionEventFlag Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â readEvents: readEventFlag Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â writeEvents: writeEventFlag]] HTH, Dave On Fri, Feb 04, 2022 at 03:05:57PM +0000, Davide Varvello wrote: >Â Hi David,That's weird because if the AioPlugin is not present in my VM,??PipeableOSProcess shouldn't have worked till this morning... when I upgraded my mac :-) > The warning is not skippable, it stops me at:??MessageNotUnderstood: IRJump>> #nextBytecodeOffsetAfterJumpCheersDavide > >Â Â On Friday, February 4, 2022, 03:54:59 PM GMT+1, David T. Lewis <lewis(a)mail.msen.com> wrote:Â >Â >Â On Fri, Feb 04, 2022 at 01:46:46PM +0000, Davide Varvello via Pharo-users wrote: > > Hi guys, > > Suddenly evaluating a simple: (PipeableOSProcess command: 'ps') output, or any other PipeableOSProcess command, Pharo gives me: "aio event forwarding not supported". > > I guess it is something related to the latest update of the OS, specifically Big Sur 11.6.3 (20G415) https://support.apple.com/en-us/HT213055I'm on a Mac, of course, Pharo 8.0.0, Build information: Pharo-8.0.0+build.1128.sha.9f6475d88dda7d83acdeeda794df35d304cf620d (64 Bit) > > Can you help me, please?CheersDavide > > Hi Davide, > > The warning message indicates that the AioPlugin is not present > in your VM. I do not know the reason for that, although your > PipeableOSProcess should still work if you proceed through the > warning. > > Dave > >Â

Feb. 4, 2022

Re: aio event forwarding not supported

by David T. Lewis

Hi Davide, Actually the warning has been removed in newer versions of OSProcess. I do not have time to do an update for Pharo now, but in the mean time you can apply this change in your image to remove the notifier: AioEventHandler>>initializeForExceptions: exceptionEventFlag readEvents: readEventFlag writeEvents: writeEventFlag semaphore := Semaphore new. semaIndex := Smalltalk registerExternalObject: semaphore. (AioPluginPresent = true) ifTrue: [ ([self aioEnable: self descriptor forSemaphore: self semaIndex externalObject: true] on: Warning do: [:e | self close. "unregister the semaphore" OSProcess trace: e messageText asString. nil]) ifNotNil: [handlerProc := self handleExceptions: exceptionEventFlag readEvents: readEventFlag writeEvents: writeEventFlag]] HTH, Dave On Fri, Feb 04, 2022 at 03:05:57PM +0000, Davide Varvello wrote: > Hi David,That's weird because if the AioPlugin is not present in my VM,??PipeableOSProcess shouldn't have worked till this morning... when I upgraded my mac :-) > The warning is not skippable, it stops me at:??MessageNotUnderstood: IRJump>> #nextBytecodeOffsetAfterJumpCheersDavide > > On Friday, February 4, 2022, 03:54:59 PM GMT+1, David T. Lewis <lewis(a)mail.msen.com> wrote: > > On Fri, Feb 04, 2022 at 01:46:46PM +0000, Davide Varvello via Pharo-users wrote: > > Hi guys, > > Suddenly evaluating a simple: (PipeableOSProcess command: 'ps') output, or any other PipeableOSProcess command, Pharo gives me: "aio event forwarding not supported". > > I guess it is something related to the latest update of the OS, specifically Big Sur 11.6.3 (20G415) https://support.apple.com/en-us/HT213055I'm on a Mac, of course, Pharo 8.0.0, Build information: Pharo-8.0.0+build.1128.sha.9f6475d88dda7d83acdeeda794df35d304cf620d (64 Bit) > > Can you help me, please?CheersDavide > > Hi Davide, > > The warning message indicates that the AioPlugin is not present > in your VM. I do not know the reason for that, although your > PipeableOSProcess should still work if you proceed through the > warning. > > Dave > >

Feb. 4, 2022

Re: aio event forwarding not supported

by Davide Varvello

Hi David,That's weird because if the AioPlugin is not present in my VM,Â PipeableOSProcess shouldn't have worked till this morning... when I upgraded my mac :-) The warning is not skippable, it stops me at:Â MessageNotUnderstood: IRJump>> #nextBytecodeOffsetAfterJumpCheersDavide On Friday, February 4, 2022, 03:54:59 PM GMT+1, David T. Lewis <lewis(a)mail.msen.com> wrote: On Fri, Feb 04, 2022 at 01:46:46PM +0000, Davide Varvello via Pharo-users wrote: > Hi guys, > Suddenly evaluating a simple: (PipeableOSProcess command: 'ps') output, or any other PipeableOSProcess command, Pharo gives me: "aio event forwarding not supported". > I guess it is something related to the latest update of the OS, specifically Big Sur 11.6.3 (20G415) https://support.apple.com/en-us/HT213055I'm on a Mac, of course, Pharo 8.0.0, Build information: Pharo-8.0.0+build.1128.sha.9f6475d88dda7d83acdeeda794df35d304cf620d (64 Bit) > Can you help me, please?CheersDavide Hi Davide, The warning message indicates that the AioPlugin is not present in your VM. I do not know the reason for that, although your PipeableOSProcess should still work if you proceed through the warning. Dave

Feb. 4, 2022

Re: aio event forwarding not supported

by David T. Lewis

On Fri, Feb 04, 2022 at 01:46:46PM +0000, Davide Varvello via Pharo-users wrote: > Hi guys, > Suddenly evaluating a simple: (PipeableOSProcess command: 'ps') output, or any other PipeableOSProcess command, Pharo gives me: "aio event forwarding not supported". > I guess it is something related to the latest update of the OS, specifically Big Sur 11.6.3 (20G415) https://support.apple.com/en-us/HT213055I'm on a Mac, of course, Pharo 8.0.0, Build information: Pharo-8.0.0+build.1128.sha.9f6475d88dda7d83acdeeda794df35d304cf620d (64 Bit) > Can you help me, please?CheersDavide Hi Davide, The warning message indicates that the AioPlugin is not present in your VM. I do not know the reason for that, although your PipeableOSProcess should still work if you proceed through the warning. Dave

Feb. 4, 2022