- Pharo-users - lists.pharo.org

FFI and when to convert the stack pointer (an Alien) into an ExternalAddress

by Holger Freyther

I am toying with Ben's bindings to clang-c (C interface to the Clang C-indexer API). One of the main features of the C API is a way to visit the translation unit. This is implemented as a callback into Smalltalk with with "cursors" providing indirect access and simplified access to the node of the AST. The return result indicates how to continue the traversal (continue, stop, recurse). FFICallback signature: #( CXChildVisitResult ( CXCursor cursor, CXCursor parent, CXString client_data)) block: [ :cursor :parent :clientData | cursor spelling. <- booom but no crash aCXChildVisitResult value "@1" ]. "cursor" will be an Instance of CXCursor and is passed by value and the C struct size is >16 bytes (on Unix this is passed on the stack). The resulting CXCursor has a handle that is invalid to perform any call-out with. CXCursor getHandle FFIExternalStructureReferenceHandle handle: an Alien (isPointer = true, the stack ptr offset: 0 ExternalStructure defines valid types as ByteArray (the data) or ExternalAddress (the pointer). FFIExternalStructureReferenceHandle is missing there and I will create a separate thread/ticket about it. So somewhere from: FFICallback>>#valueWithContext:sp: ... FFICallbackArg>>#extractStructType: FFIExternalType>>#handle:at: FFIExternalStructureType>>#basicHandle:at: ee will need to convert the handle + offset (one based) to an ExternalAddress. Now the protocol of >>#handle:at: and >>#integerAt:, >>#pointerAt: indicate that we want to carry address+offset into late of the conversion. And I can't point my finger into where it should be done. I have created: Alien>>#referenceStructAt: byteOffset length: length ^self isPointer ifFalse: [super referenceStructAt: byteOffset length: length ] ifTrue: [ (ExternalAddress fromAddress: self addressField) + (byteOffset - 1)] This "fixes" it. But that is at the last point in the conversion. It shadows another problem as well. So in fact maybe changing: FFICallbackArgumentReader>>#extractPointerOfType: and >>#extractStructType: to read: ... pair := self nextBaseAddressForStructure: type. baseAddressToRead := ExternalAddress fromAddress: pair first address. <- modified offsetOfBaseAddress := pair second. ... is this the right way forward? We convert the stack to an ExternalAddress early on and use it. With the above change to FFICallbackArgumentReader the CXCursor from the stack will read as: CXCursor getHandle FFIExternalStructureReferenceHandle handle: ExternalAddress offset: 0 I am still not able to push this cursor to the stack. But that is for another mail. WDUT? holger

April 4, 2019

Difficulties setting up default image in XMonad

by Vanessa McHale

Hi all, When I try to launch the latest Pharo image in XMonad, I run into the following: Pharo launch failure screenshot I couldn't copy the error text unfortunately so I have attached a screenshot instead. Any hints on what might be causing it? Is it due to my using a tiling window manager? Cheers, Vanessa McHale

April 4, 2019

Re: [Pharo-users] Slots and Metalink

by Steven Costiou

Also, I do not think metalinks could work on #write:to: method from slots, because that method is not used at runtime (I do not remember exactly but maybe somebody knows the details...). Le 2019-04-03 16:20, Steven Costiou a Ã©crit : > Hi, > > if you are using Pharo7, you could do either on a class (affects all instances) or on an object (affects only the target instance): > >> classOrObject link: yourMetaLink toSlotNamed: #slotName option: #write > > It will install the metalink on all write accesses to the slot. > > Note that if you target a single object, it will be migrated to an anonymous subclass for the metalink to be object-specific. > > In both cases, if you add or remove inst-var accesses, the metalink should update automatically. > > Steven. > > Le 2019-04-03 15:57, Vitor Medina Cruz a Ã©crit : > >> Hello, >> >> Is it possible to intercept a slot store? I tried with a before metalink into #write:to selector, but it don't seems to work. Should I use another selector? >> >> I would like to experiment with ivar change notification, but I don't know what is the better approach. I know I could install a MetaLink in an attribution node, but that seems ankward and I would have to edit the linkage every time my object is changed, isn't true? >> >> Regards, >> Vitor

April 3, 2019

Re: [Pharo-users] Slots and Metalink

by Steven Costiou

Hi, if you are using Pharo7, you could do either on a class (affects all instances) or on an object (affects only the target instance): > classOrObject link: yourMetaLink toSlotNamed: #slotName option: #write It will install the metalink on all write accesses to the slot. Note that if you target a single object, it will be migrated to an anonymous subclass for the metalink to be object-specific. In both cases, if you add or remove inst-var accesses, the metalink should update automatically. Steven. Le 2019-04-03 15:57, Vitor Medina Cruz a Ã©crit : > Hello, > > Is it possible to intercept a slot store? I tried with a before metalink into #write:to selector, but it don't seems to work. Should I use another selector? > > I would like to experiment with ivar change notification, but I don't know what is the better approach. I know I could install a MetaLink in an attribution node, but that seems ankward and I would have to edit the linkage every time my object is changed, isn't true? > > Regards, > Vitor

April 3, 2019

Slots and Metalink

by Vitor Medina Cruz

Hello, Is it possible to intercept a slot store? I tried with a before metalink into #write:to selector, but it don't seems to work. Should I use another selector? I would like to experiment with ivar change notification, but I don't know what is the better approach. I know I could install a MetaLink in an attribution node, but that seems ankward and I would have to edit the linkage every time my object is changed, isn't true? Regards, Vitor

April 3, 2019

Re: [Pharo-users] What's wrong with latest Pharo?

by Ben Coman

On Wed, 3 Apr 2019 at 05:09, Richard O'Keefe <raoknz(a)gmail.com> wrote: > I just did a complete reinstall of Ubuntu 18.4 on this > laptop yesterday, > > and it did not come with any version of curl. > What do you mean? Under WSL I have installed Ubuntu 18.4 and for... $ apt-cache search libcurl | less I see libcurl3 and libcurl4 cheers -ben > uname -a => > Linux Inspiron 4.18.0-16-generic #17~18.04.1-Ubuntu SMP Tue Feb 12 > 13:35:51 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux > > > > On Wed, 3 Apr 2019 at 01:27, Vitor Medina Cruz <vitormcruz(a)gmail.com> > wrote: > >> Installing curl don't work because there is a conflict between curl >> version name used on Ubuntu and that used by Pharo, you can't install >> libcurl 3 and libcru4 together. Ubuntu 18 comes with libcurl4 and older >> software depending on libcurl3 broke with it. I tested with minidebian and >> it also failed. >> >> Richard, was you able to use Iceberg? It should only work if either >> Ubuntu fix this dependency problem with libcurl or Pharo started to use >> libcrl4. >> >> >> >> On Tue, Apr 2, 2019 at 5:50 AM Richard O'Keefe <raoknz(a)gmail.com> wrote: >> >>> I have Pharo 6.1 and Pharo 7.0 working in Ubuntu 18.04 >>> with no trouble so far. I just downloaded the launcher >>> from pharo.org and pulled the images down that way. >>> >>> One thing I do find annoying in Ubuntu 18.04 is the >>> number of programs (like okular) that spew warning >>> messages out the terminal. Pharo, sadly, is one of >>> them. Whenever a debugger window comes up in Pharo >>> there is spewage on the terminal. But it works. >>> >>> >>> On Tue, 2 Apr 2019 at 13:07, john pfersich <jpfersich(a)gmail.com> wrote: >>> >>>> Ubuntu 18.04 LTS is, IMHO, is royal piece of crap. Ubuntu seems to have >>>> abandoned programmers tools almost completely in 18.04. Iâve had more >>>> problems with support of programming tools in 18.04, more than even >>>> Windows. I have run âsudo apt installâ maybe 80 times to install tools and >>>> libraries. Ubuntu 18.04âs hardware support is also lame compared to 16.04. >>>> Personally , Iâm not surprised that Pharo doesnât run on 18.04. I >>>> stopped installing 18.04 on my new machines, after all 16.04 still has a >>>> few years of support going for it, and at least it works without hours of >>>> upgrading. >>>> >>>> /*âââââââââââââââââ-*/ >>>> Sent from my iPhone >>>> https://boincstats.com/signature/-1/user/51616339056/sig.png >>>> See https://objectnets.net and https://objectnets.org >>>> >>>> > On Apr 1, 2019, at 06:06, horrido <horrido.hobbies(a)gmail.com> wrote: >>>> > >>>> > This issue bit me in the ass before, but I forgot. Yes, I had a senior >>>> > moment. >>>> > >>>> > The issue is this: When I tried to run Pharo under Ubuntu Server >>>> 18.04 at >>>> > OVH last year, it failed. I had to fall back to Ubuntu Server 16.04. >>>> > >>>> > This week, I tried to run Pharo under Ubuntu Server 18.04 at Google >>>> Cloud >>>> > Platform and it failed. Again, I had to fall back to Ubuntu Server >>>> 16.04. >>>> > >>>> > Why does this issue keep biting me in the ass??? Because I'm 65 and >>>> my brain >>>> > is dying. >>>> > >>>> > The bigger issue is this: Hosting services like Digital Ocean, OVH, >>>> and >>>> > Google Cloud Platform are becoming increasingly important in the >>>> enterprise >>>> > space. If Pharo can't run on these server operating systems, it's >>>> going to >>>> > be a black eye for the language. We can get away with not supporting >>>> this >>>> > for now, but it will eventually catch up with us. >>>> > >>>> > At Google Cloud Platform, for example, the user can choose from this >>>> list of >>>> > hosts: Debian GNU/Linux 9 (Stretch), CentOS 6, CentOS 7, various >>>> versions of >>>> > CoreOS, Ubuntu 14.04 LTS Minimal, Ubuntu 16.04 LTS Minimal, Ubuntu >>>> 18.04 LTS >>>> > Minimal, Ubuntu 18.10 Minimal, various versions of Red Hat, various >>>> versions >>>> > of SUSE, various versions of Window, and so on. It's a long list. *I >>>> > strongly suspect that many of these are unusable with Pharo.* >>>> > >>>> > How to address this? I don't know. But if it's not a major problem >>>> now, it >>>> > will be. It's bitten me in the ass twice, and I can't be alone. >>>> > >>>> > I'm giving a fair warning to everyone. Don't lash back at me â I'm >>>> just the >>>> > canary in the coal mine. >>>> > >>>> > >>>> > >>>> > >>>> > Tim Mackinnon wrote >>>> >> Come on, letâs try not to be dismissive , weâve all had that annoying >>>> >> moment where something doesnât work. >>>> >> >>>> >> Richard, was this installed with zero conf or Launcher, and as >>>> mentioned - >>>> >> a Linux distro is going to be helpful. >>>> >> >>>> >> Iâm assuming it worked before at some point for you right? But was >>>> that v6 >>>> >> and now youâre trying v7? >>>> >> >>>> >> Tim >>>> >> >>>> >> >>>> >> Sent from my iPhone >>>> >> >>>> >>> On 31 Mar 2019, at 23:46, john pfersich < >>>> > >>>> >> jpfersich@ >>>> > >>>> >> > wrote: >>>> >>> >>>> >>> What Linux (distro and version) and which version of Pharo. You >>>> couldnât >>>> >>> supply less information if you tried. >>>> >>> >>>> >>> >>>> >>> /*âââââââââââââââââ-*/ >>>> >>> Sent from my iPhone >>>> >>> https://boincstats.com/signature/-1/user/51616339056/sig.png >>>> >>> See https://objectnets.net and https://objectnets.org >>>> >>> >>>> >>>> On Mar 31, 2019, at 14:21, Richard Kenneth Eng < >>>> > >>>> >> horrido.hobbies@ >>>> > >>>> >> > wrote: >>>> >>>> >>>> >>>> I just installed Pharo under Linux and when I start it up, I get: >>>> >>>> >>>> >>>> Error: External module not found >>>> >>>> >>>> >>>> It doesn't matter how I install Pharo. >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > -- >>>> > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >>>> > >>>> >>>>

April 3, 2019

Re: [Pharo-users] Comment on: Pharo performance issues

by Marcus Denker

> > I spent quite some time with Alexandre Bergel's NeuralNetwork implementation and stumbled across many implementations that cause general performance issues. > > While, I "fixed/altered" only those parts affecting my code, I would offer to search trough the image an alter the parts similar to those already altered. > > In such case that somebody would like to move a greater amount of code towards review and integration into current development how would the process of such contribution look like? > > The regular path of reporting bugs, or just forking on Github and pull request? The best is to first report an issue, then do a pull request. There is a pointer to a tutorial here: https://github.com/pharo-project/pharo/blob/Pharo8.0/CONTRIBUTING.md <https://github.com/pharo-project/pharo/blob/Pharo8.0/CONTRIBUTING.md> (If you get stuck somewhere, please tellâ¦ I think it might needs some update for Pharo8, it is on my TODO to check it carefully) > > I am extremely busy right now, but during the nights I could slowly attempt to work some performance issues out. > That would be great! Marcus

April 3, 2019

Re: [Pharo-users] What's wrong with latest Pharo?

by Richard O'Keefe

I just did a complete reinstall of Ubuntu 18.4 on this laptop yesterday, and it did not come with any version of curl. uname -a => Linux Inspiron 4.18.0-16-generic #17~18.04.1-Ubuntu SMP Tue Feb 12 13:35:51 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux On Wed, 3 Apr 2019 at 01:27, Vitor Medina Cruz <vitormcruz(a)gmail.com> wrote: > Installing curl don't work because there is a conflict between curl > version name used on Ubuntu and that used by Pharo, you can't install > libcurl 3 and libcru4 together. Ubuntu 18 comes with libcurl4 and older > software depending on libcurl3 broke with it. I tested with minidebian and > it also failed. > > Richard, was you able to use Iceberg? It should only work if either Ubuntu > fix this dependency problem with libcurl or Pharo started to use libcrl4. > > > > On Tue, Apr 2, 2019 at 5:50 AM Richard O'Keefe <raoknz(a)gmail.com> wrote: > >> I have Pharo 6.1 and Pharo 7.0 working in Ubuntu 18.04 >> with no trouble so far. I just downloaded the launcher >> from pharo.org and pulled the images down that way. >> >> One thing I do find annoying in Ubuntu 18.04 is the >> number of programs (like okular) that spew warning >> messages out the terminal. Pharo, sadly, is one of >> them. Whenever a debugger window comes up in Pharo >> there is spewage on the terminal. But it works. >> >> >> On Tue, 2 Apr 2019 at 13:07, john pfersich <jpfersich(a)gmail.com> wrote: >> >>> Ubuntu 18.04 LTS is, IMHO, is royal piece of crap. Ubuntu seems to have >>> abandoned programmers tools almost completely in 18.04. Iâve had more >>> problems with support of programming tools in 18.04, more than even >>> Windows. I have run âsudo apt installâ maybe 80 times to install tools and >>> libraries. Ubuntu 18.04âs hardware support is also lame compared to 16.04. >>> Personally , Iâm not surprised that Pharo doesnât run on 18.04. I >>> stopped installing 18.04 on my new machines, after all 16.04 still has a >>> few years of support going for it, and at least it works without hours of >>> upgrading. >>> >>> /*âââââââââââââââââ-*/ >>> Sent from my iPhone >>> https://boincstats.com/signature/-1/user/51616339056/sig.png >>> See https://objectnets.net and https://objectnets.org >>> >>> > On Apr 1, 2019, at 06:06, horrido <horrido.hobbies(a)gmail.com> wrote: >>> > >>> > This issue bit me in the ass before, but I forgot. Yes, I had a senior >>> > moment. >>> > >>> > The issue is this: When I tried to run Pharo under Ubuntu Server 18.04 >>> at >>> > OVH last year, it failed. I had to fall back to Ubuntu Server 16.04. >>> > >>> > This week, I tried to run Pharo under Ubuntu Server 18.04 at Google >>> Cloud >>> > Platform and it failed. Again, I had to fall back to Ubuntu Server >>> 16.04. >>> > >>> > Why does this issue keep biting me in the ass??? Because I'm 65 and my >>> brain >>> > is dying. >>> > >>> > The bigger issue is this: Hosting services like Digital Ocean, OVH, and >>> > Google Cloud Platform are becoming increasingly important in the >>> enterprise >>> > space. If Pharo can't run on these server operating systems, it's >>> going to >>> > be a black eye for the language. We can get away with not supporting >>> this >>> > for now, but it will eventually catch up with us. >>> > >>> > At Google Cloud Platform, for example, the user can choose from this >>> list of >>> > hosts: Debian GNU/Linux 9 (Stretch), CentOS 6, CentOS 7, various >>> versions of >>> > CoreOS, Ubuntu 14.04 LTS Minimal, Ubuntu 16.04 LTS Minimal, Ubuntu >>> 18.04 LTS >>> > Minimal, Ubuntu 18.10 Minimal, various versions of Red Hat, various >>> versions >>> > of SUSE, various versions of Window, and so on. It's a long list. *I >>> > strongly suspect that many of these are unusable with Pharo.* >>> > >>> > How to address this? I don't know. But if it's not a major problem >>> now, it >>> > will be. It's bitten me in the ass twice, and I can't be alone. >>> > >>> > I'm giving a fair warning to everyone. Don't lash back at me â I'm >>> just the >>> > canary in the coal mine. >>> > >>> > >>> > >>> > >>> > Tim Mackinnon wrote >>> >> Come on, letâs try not to be dismissive , weâve all had that annoying >>> >> moment where something doesnât work. >>> >> >>> >> Richard, was this installed with zero conf or Launcher, and as >>> mentioned - >>> >> a Linux distro is going to be helpful. >>> >> >>> >> Iâm assuming it worked before at some point for you right? But was >>> that v6 >>> >> and now youâre trying v7? >>> >> >>> >> Tim >>> >> >>> >> >>> >> Sent from my iPhone >>> >> >>> >>> On 31 Mar 2019, at 23:46, john pfersich < >>> > >>> >> jpfersich@ >>> > >>> >> > wrote: >>> >>> >>> >>> What Linux (distro and version) and which version of Pharo. You >>> couldnât >>> >>> supply less information if you tried. >>> >>> >>> >>> >>> >>> /*âââââââââââââââââ-*/ >>> >>> Sent from my iPhone >>> >>> https://boincstats.com/signature/-1/user/51616339056/sig.png >>> >>> See https://objectnets.net and https://objectnets.org >>> >>> >>> >>>> On Mar 31, 2019, at 14:21, Richard Kenneth Eng < >>> > >>> >> horrido.hobbies@ >>> > >>> >> > wrote: >>> >>>> >>> >>>> I just installed Pharo under Linux and when I start it up, I get: >>> >>>> >>> >>>> Error: External module not found >>> >>>> >>> >>>> It doesn't matter how I install Pharo. >>> > >>> > >>> > >>> > >>> > >>> > -- >>> > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >>> > >>> >>>

April 2, 2019

Comment on: Pharo performance issues

by Sebastian Heidbrink

Hi! A friend of mine just just pointed this entry out to me https://pharoweekly.wordpress.com/2019/04/02/about-performance-issues/ I spent quite some time with Alexandre Bergel's NeuralNetwork implementation and stumbled across many implementations that cause general performance issues. While, I "fixed/altered" only those parts affecting my code, I would offer to search trough the image an alter the parts similar to those already altered. In such case that somebody would like to move a greater amount of code towards review and integration into current development how would the process of such contribution look like? The regular path of reporting bugs, or just forking on Github and pull request? I am extremely busy right now, but during the nights I could slowly attempt to work some performance issues out. Kind wishes, Sebastian

April 2, 2019

Re: [Pharo-users] What's wrong with latest Pharo?

by Vitor Medina Cruz

Installing curl don't work because there is a conflict between curl version name used on Ubuntu and that used by Pharo, you can't install libcurl 3 and libcru4 together. Ubuntu 18 comes with libcurl4 and older software depending on libcurl3 broke with it. I tested with minidebian and it also failed. Richard, was you able to use Iceberg? It should only work if either Ubuntu fix this dependency problem with libcurl or Pharo started to use libcrl4. On Tue, Apr 2, 2019 at 5:50 AM Richard O'Keefe <raoknz(a)gmail.com> wrote: > I have Pharo 6.1 and Pharo 7.0 working in Ubuntu 18.04 > with no trouble so far. I just downloaded the launcher > from pharo.org and pulled the images down that way. > > One thing I do find annoying in Ubuntu 18.04 is the > number of programs (like okular) that spew warning > messages out the terminal. Pharo, sadly, is one of > them. Whenever a debugger window comes up in Pharo > there is spewage on the terminal. But it works. > > > On Tue, 2 Apr 2019 at 13:07, john pfersich <jpfersich(a)gmail.com> wrote: > >> Ubuntu 18.04 LTS is, IMHO, is royal piece of crap. Ubuntu seems to have >> abandoned programmers tools almost completely in 18.04. Iâve had more >> problems with support of programming tools in 18.04, more than even >> Windows. I have run âsudo apt installâ maybe 80 times to install tools and >> libraries. Ubuntu 18.04âs hardware support is also lame compared to 16.04. >> Personally , Iâm not surprised that Pharo doesnât run on 18.04. I stopped >> installing 18.04 on my new machines, after all 16.04 still has a few years >> of support going for it, and at least it works without hours of upgrading. >> >> /*âââââââââââââââââ-*/ >> Sent from my iPhone >> https://boincstats.com/signature/-1/user/51616339056/sig.png >> See https://objectnets.net and https://objectnets.org >> >> > On Apr 1, 2019, at 06:06, horrido <horrido.hobbies(a)gmail.com> wrote: >> > >> > This issue bit me in the ass before, but I forgot. Yes, I had a senior >> > moment. >> > >> > The issue is this: When I tried to run Pharo under Ubuntu Server 18.04 >> at >> > OVH last year, it failed. I had to fall back to Ubuntu Server 16.04. >> > >> > This week, I tried to run Pharo under Ubuntu Server 18.04 at Google >> Cloud >> > Platform and it failed. Again, I had to fall back to Ubuntu Server >> 16.04. >> > >> > Why does this issue keep biting me in the ass??? Because I'm 65 and my >> brain >> > is dying. >> > >> > The bigger issue is this: Hosting services like Digital Ocean, OVH, and >> > Google Cloud Platform are becoming increasingly important in the >> enterprise >> > space. If Pharo can't run on these server operating systems, it's going >> to >> > be a black eye for the language. We can get away with not supporting >> this >> > for now, but it will eventually catch up with us. >> > >> > At Google Cloud Platform, for example, the user can choose from this >> list of >> > hosts: Debian GNU/Linux 9 (Stretch), CentOS 6, CentOS 7, various >> versions of >> > CoreOS, Ubuntu 14.04 LTS Minimal, Ubuntu 16.04 LTS Minimal, Ubuntu >> 18.04 LTS >> > Minimal, Ubuntu 18.10 Minimal, various versions of Red Hat, various >> versions >> > of SUSE, various versions of Window, and so on. It's a long list. *I >> > strongly suspect that many of these are unusable with Pharo.* >> > >> > How to address this? I don't know. But if it's not a major problem now, >> it >> > will be. It's bitten me in the ass twice, and I can't be alone. >> > >> > I'm giving a fair warning to everyone. Don't lash back at me â I'm just >> the >> > canary in the coal mine. >> > >> > >> > >> > >> > Tim Mackinnon wrote >> >> Come on, letâs try not to be dismissive , weâve all had that annoying >> >> moment where something doesnât work. >> >> >> >> Richard, was this installed with zero conf or Launcher, and as >> mentioned - >> >> a Linux distro is going to be helpful. >> >> >> >> Iâm assuming it worked before at some point for you right? But was >> that v6 >> >> and now youâre trying v7? >> >> >> >> Tim >> >> >> >> >> >> Sent from my iPhone >> >> >> >>> On 31 Mar 2019, at 23:46, john pfersich < >> > >> >> jpfersich@ >> > >> >> > wrote: >> >>> >> >>> What Linux (distro and version) and which version of Pharo. You >> couldnât >> >>> supply less information if you tried. >> >>> >> >>> >> >>> /*âââââââââââââââââ-*/ >> >>> Sent from my iPhone >> >>> https://boincstats.com/signature/-1/user/51616339056/sig.png >> >>> See https://objectnets.net and https://objectnets.org >> >>> >> >>>> On Mar 31, 2019, at 14:21, Richard Kenneth Eng < >> > >> >> horrido.hobbies@ >> > >> >> > wrote: >> >>>> >> >>>> I just installed Pharo under Linux and when I start it up, I get: >> >>>> >> >>>> Error: External module not found >> >>>> >> >>>> It doesn't matter how I install Pharo. >> > >> > >> > >> > >> > >> > -- >> > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> > >> >>

April 2, 2019