- Pharo-users - lists.pharo.org

Re: [Pharo-users] ring deprecation in pharo 7

by Peter Uhnak

Hi Doru, I imagine the replacement is Pavel's Ring2 https://github.com/pavel-krivanek/ring2 Peter On Fri, Oct 19, 2018 at 10:56 PM Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > Ring seems to be deprecated in Pharo 7. Is there something else it will be > replaced with? > > In particular, I am looking for the correct class that should correspond > to RGMethodDefinition. > > Cheers, > Doru > > > -- > www.feenk.com > > "Value is always contextual." > > > > > > >

Oct. 23, 2018

Re: [Pharo-users] About the IoT Hackathon last Friday

by Norbert Hartl

Thank you for the kind words! It was our pleasure to have you with us. Everything went well and we had a beautiful day together. So good we have to repeat this!! Norbert > Am 22.10.2018 um 16:23 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > > Last Friday we went to the IoT Hackathon in KÃ¶ln and it was a great experience. > > Thank you Norbert, Christian, Markus and the whole ZweiDenker team for their generous hospitality: the accommodations where great (beautiful office), the food and drinks super tasty, everybody friendly and welcoming. > > Thank you Allex (Oliviera, Inria/RMOD) for running the workshop and for being so patient, friendly and tireless in helping everyone with all aspects of getting experiments up and running. > > I knew about PharoThings [1] and TelePharo [2] before, but actually using it in practice to experience connecting software and hardware felt a bit like magic. Thank you Denis (Kudriashov) and Inria/RMOD for developing these packages. > > > > > > Sven > > [1] https://github.com/pharo-iot/PharoThings > [2] https://github.com/pharo-ide/TelePharo > >

Oct. 22, 2018

Re: [Pharo-users] [vwnc] Parsing in Smalltalk

by Steffen MÃ¤rcker

Hi, my current shot is to subclass IdentityDictionary with NildentityDictionary. The class checks on indexed access whether the key is nil. If so, storing/retrival uses a singleton Object as key (stored in instance variable NIL := Object new). I needed to override at least: >>at:ifAbsent: >>associationsAt:ifAbsent: >>at:put: >>findElementLike:ifAbsent: >>initialize class>>new class>>new: It works for PP2 (without serious performance impact so far), although the class is yet incomplete wrt. Collection/Dictionary protocol. Currently, all but the Morphic-related tests are green. \o/ After some cleanup of the bundles, I'll publish an inital version to the Public Store. @James: If you like, I we could discuss our ports later to double-check an making the future process easier. How about that? @Jan: I'd be happy to hear your thoughts on the porting matter. Best, Steffen Am .10.2018, 16:06 Uhr, schrieb James Foster <Smalltalk(a)jgfoster.net>: > We will have the same issue porting PP2 to GemStone and look forward to > suggestions. > >> On Oct 22, 2018, at 4:40 AM, Steffen MÃ¤rcker <merkste(a)web.de> wrote: >> >> Hi Jan, >> >> I am trying to port PP2 to VW and managed to get most of the tests >> green. =) Some of the remaining test failures occur in >> >> PP2DebuggingStrategy>>cacheIfNeeded:debugResult: >> >> where a result of nil is to be stored in an IdentityDictionary. But in >> VW Dictionaries do not accept nil as a key. If this is indeed intended, >> I wonder how to circumvent the limitation best. Would it be feasible to >> use a placeholder object instead of nil (which code would be effected)? >> Or would it be better to not cache nil at all? >> >> I'd be happy to hear your thoughts. >> >> Best, Steffen >> >> >> >> >> >> Am .10.2018, 20:58 Uhr, schrieb Jan KurÅ¡ <kurs.jan(a)gmail.com>: >> >>> I run PP2 on travis [1], seems Pharo 6.1 loads all configurations, >>> both on >>> linux and mac. Pharo 5, Pharo 6.0 got broken, why is build >>> configuration so >>> hard :'( I don't know, how can I support you. I myself had to gave up >>> on >>> some tools, because I failed to load them. >>> >>> There is no specific reason to use SmallInteger maxVal... and nobody >>> ever >>> thought it might be too little. 'PP2 min: X' fails if there are less >>> repetitions that X. 'PP2 max: X' parses at most X repetitions. >>> >>> ($a asPParser min: 2 max: 3) parse: 'a'. -> Failure >>> ($a asPParser min: 2 max: 3) parse: 'aa'. #($a $a) >>> ($a asPParser min: 2 max: 3) parse: 'aaa'. #($a $a $a) >>> ($a asPParser min: 2 max: 3) parse: 'aaaa'. #($a $a $a) >>> >>> >>> Use $- asPParser for characters, e.g: >>> $- asPParser parse: '-' >>> >>> [1]: https://travis-ci.org/kursjan/petitparser2/builds/438358467 >>> >>> On Thu, Oct 11, 2018 at 8:13 PM Steffen MÃ¤rcker <merkste(a)web.de> wrote: >>> >>>> Reading the code of PetitParser, I wonder why PPRepeatingParser >>>> initializes 'max' with SmallInteger maxVal instead of some notion of >>>> infinity, like Float infinity (and PP2RepeatingNode as well). If I >>>> understand the code correctly, PParser>>min: fails if the number of >>>> repetitions exceeds SmallInteger maxVal, doesn't it? >>>> >>>> Best, Steffen >>>> >>>> >>>> Am .10.2018, 17:10 Uhr, schrieb Steffen MÃ¤rcker <merkste(a)web.de>: >>>> >>>> > I am using MacOS 10.13.6 and the 32bit VM: >>>> > >>>> > Pharo 6.0 >>>> > Latest update: #60546 >>>> > >>>> > ... the String in about is wrong, it should be 6.1. I installed it >>>> via >>>> > the launcher as "Official Distribution: Pharo 6.1 - 32Bit (stable)" >>>> I >>>> > just noticed, that the sources file is missing from >>>> vms/private/6521/, >>>> > too. >>>> > >>>> > Am .10.2018, 17:02 Uhr, schrieb Sean P. DeNigris >>>> <sean(a)clipperadams.com >>>> >: >>>> > >>>> >> Steffen MÃ¤rcker wrote >>>> >>> I did the following: >>>> >>> 1) Download and start Pharo 6.1 stable via the launcher. >>>> >>> 2b) Attempt to install PP2 via the scripts from GitHub: >>>> >>> Metacello new >>>> >>> baseline: 'PetitParser2'; >>>> >>> repository: 'github://kursjan/petitparser2'; >>>> >>> load. >>>> >>> Metacello new >>>> >>> baseline: 'PetitParser2Gui'; >>>> >>> repository: 'github://kursjan/petitparser2'; >>>> >>> load. >>>> >> >>>> >> This way worked for me in Pharo #60546 (check in >>>> World->System->About). >>>> >> What >>>> >> exact Pharo version/OS are you on? 32 or 64-bit >>>> >> >>>> >> >>>> >> >>>> >> ----- >>>> >> Cheers, >>>> >> Sean >>>> >> -- >>>> >> Sent from: >>>> http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >>>> >> >>>> > >>>> > >>>> >> >> >

Oct. 22, 2018

About the IoT Hackathon last Friday

by Sven Van Caekenberghe

Last Friday we went to the IoT Hackathon in KÃ¶ln and it was a great experience. Thank you Norbert, Christian, Markus and the whole ZweiDenker team for their generous hospitality: the accommodations where great (beautiful office), the food and drinks super tasty, everybody friendly and welcoming. Thank you Allex (Oliviera, Inria/RMOD) for running the workshop and for being so patient, friendly and tireless in helping everyone with all aspects of getting experiments up and running. I knew about PharoThings [1] and TelePharo [2] before, but actually using it in practice to experience connecting software and hardware felt a bit like magic. Thank you Denis (Kudriashov) and Inria/RMOD for developing these packages. Sven [1] https://github.com/pharo-iot/PharoThings [2] https://github.com/pharo-ide/TelePharo

Oct. 22, 2018

Re: [Pharo-users] [vwnc] Parsing in Smalltalk

by James Foster

We will have the same issue porting PP2 to GemStone and look forward to suggestions. > On Oct 22, 2018, at 4:40 AM, Steffen MÃ¤rcker <merkste(a)web.de> wrote: > > Hi Jan, > > I am trying to port PP2 to VW and managed to get most of the tests green. =) Some of the remaining test failures occur in > > PP2DebuggingStrategy>>cacheIfNeeded:debugResult: > > where a result of nil is to be stored in an IdentityDictionary. But in VW Dictionaries do not accept nil as a key. If this is indeed intended, I wonder how to circumvent the limitation best. Would it be feasible to use a placeholder object instead of nil (which code would be effected)? Or would it be better to not cache nil at all? > > I'd be happy to hear your thoughts. > > Best, Steffen > > > > > > Am .10.2018, 20:58 Uhr, schrieb Jan KurÅ¡ <kurs.jan(a)gmail.com>: > >> I run PP2 on travis [1], seems Pharo 6.1 loads all configurations, both on >> linux and mac. Pharo 5, Pharo 6.0 got broken, why is build configuration so >> hard :'( I don't know, how can I support you. I myself had to gave up on >> some tools, because I failed to load them. >> >> There is no specific reason to use SmallInteger maxVal... and nobody ever >> thought it might be too little. 'PP2 min: X' fails if there are less >> repetitions that X. 'PP2 max: X' parses at most X repetitions. >> >> ($a asPParser min: 2 max: 3) parse: 'a'. -> Failure >> ($a asPParser min: 2 max: 3) parse: 'aa'. #($a $a) >> ($a asPParser min: 2 max: 3) parse: 'aaa'. #($a $a $a) >> ($a asPParser min: 2 max: 3) parse: 'aaaa'. #($a $a $a) >> >> >> Use $- asPParser for characters, e.g: >> $- asPParser parse: '-' >> >> [1]: https://travis-ci.org/kursjan/petitparser2/builds/438358467 >> >> On Thu, Oct 11, 2018 at 8:13 PM Steffen MÃ¤rcker <merkste(a)web.de> wrote: >> >>> Reading the code of PetitParser, I wonder why PPRepeatingParser >>> initializes 'max' with SmallInteger maxVal instead of some notion of >>> infinity, like Float infinity (and PP2RepeatingNode as well). If I >>> understand the code correctly, PParser>>min: fails if the number of >>> repetitions exceeds SmallInteger maxVal, doesn't it? >>> >>> Best, Steffen >>> >>> >>> Am .10.2018, 17:10 Uhr, schrieb Steffen MÃ¤rcker <merkste(a)web.de>: >>> >>> > I am using MacOS 10.13.6 and the 32bit VM: >>> > >>> > Pharo 6.0 >>> > Latest update: #60546 >>> > >>> > ... the String in about is wrong, it should be 6.1. I installed it via >>> > the launcher as "Official Distribution: Pharo 6.1 - 32Bit (stable)" I >>> > just noticed, that the sources file is missing from vms/private/6521/, >>> > too. >>> > >>> > Am .10.2018, 17:02 Uhr, schrieb Sean P. DeNigris <sean(a)clipperadams.com >>> >: >>> > >>> >> Steffen MÃ¤rcker wrote >>> >>> I did the following: >>> >>> 1) Download and start Pharo 6.1 stable via the launcher. >>> >>> 2b) Attempt to install PP2 via the scripts from GitHub: >>> >>> Metacello new >>> >>> baseline: 'PetitParser2'; >>> >>> repository: 'github://kursjan/petitparser2'; >>> >>> load. >>> >>> Metacello new >>> >>> baseline: 'PetitParser2Gui'; >>> >>> repository: 'github://kursjan/petitparser2'; >>> >>> load. >>> >> >>> >> This way worked for me in Pharo #60546 (check in >>> World->System->About). >>> >> What >>> >> exact Pharo version/OS are you on? 32 or 64-bit >>> >> >>> >> >>> >> >>> >> ----- >>> >> Cheers, >>> >> Sean >>> >> -- >>> >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >>> >> >>> > >>> > >>> > >

Oct. 22, 2018

Re: [Pharo-users] [vwnc] Parsing in Smalltalk

by Steffen MÃ¤rcker

Hi Jan, I am trying to port PP2 to VW and managed to get most of the tests green. =) Some of the remaining test failures occur in PP2DebuggingStrategy>>cacheIfNeeded:debugResult: where a result of nil is to be stored in an IdentityDictionary. But in VW Dictionaries do not accept nil as a key. If this is indeed intended, I wonder how to circumvent the limitation best. Would it be feasible to use a placeholder object instead of nil (which code would be effected)? Or would it be better to not cache nil at all? I'd be happy to hear your thoughts. Best, Steffen Am .10.2018, 20:58 Uhr, schrieb Jan KurÅ¡ <kurs.jan(a)gmail.com>: > I run PP2 on travis [1], seems Pharo 6.1 loads all configurations, both > on > linux and mac. Pharo 5, Pharo 6.0 got broken, why is build configuration > so > hard :'( I don't know, how can I support you. I myself had to gave up on > some tools, because I failed to load them. > > There is no specific reason to use SmallInteger maxVal... and nobody > ever > thought it might be too little. 'PP2 min: X' fails if there are less > repetitions that X. 'PP2 max: X' parses at most X repetitions. > > ($a asPParser min: 2 max: 3) parse: 'a'. -> Failure > ($a asPParser min: 2 max: 3) parse: 'aa'. #($a $a) > ($a asPParser min: 2 max: 3) parse: 'aaa'. #($a $a $a) > ($a asPParser min: 2 max: 3) parse: 'aaaa'. #($a $a $a) > > > Use $- asPParser for characters, e.g: > $- asPParser parse: '-' > > [1]: https://travis-ci.org/kursjan/petitparser2/builds/438358467 > > On Thu, Oct 11, 2018 at 8:13 PM Steffen MÃ¤rcker <merkste(a)web.de> wrote: > >> Reading the code of PetitParser, I wonder why PPRepeatingParser >> initializes 'max' with SmallInteger maxVal instead of some notion of >> infinity, like Float infinity (and PP2RepeatingNode as well). If I >> understand the code correctly, PParser>>min: fails if the number of >> repetitions exceeds SmallInteger maxVal, doesn't it? >> >> Best, Steffen >> >> >> Am .10.2018, 17:10 Uhr, schrieb Steffen MÃ¤rcker <merkste(a)web.de>: >> >> > I am using MacOS 10.13.6 and the 32bit VM: >> > >> > Pharo 6.0 >> > Latest update: #60546 >> > >> > ... the String in about is wrong, it should be 6.1. I installed it via >> > the launcher as "Official Distribution: Pharo 6.1 - 32Bit (stable)" I >> > just noticed, that the sources file is missing from vms/private/6521/, >> > too. >> > >> > Am .10.2018, 17:02 Uhr, schrieb Sean P. DeNigris >> <sean(a)clipperadams.com >> >: >> > >> >> Steffen MÃ¤rcker wrote >> >>> I did the following: >> >>> 1) Download and start Pharo 6.1 stable via the launcher. >> >>> 2b) Attempt to install PP2 via the scripts from GitHub: >> >>> Metacello new >> >>> baseline: 'PetitParser2'; >> >>> repository: 'github://kursjan/petitparser2'; >> >>> load. >> >>> Metacello new >> >>> baseline: 'PetitParser2Gui'; >> >>> repository: 'github://kursjan/petitparser2'; >> >>> load. >> >> >> >> This way worked for me in Pharo #60546 (check in >> World->System->About). >> >> What >> >> exact Pharo version/OS are you on? 32 or 64-bit >> >> >> >> >> >> >> >> ----- >> >> Cheers, >> >> Sean >> >> -- >> >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> >> >> > >> > >>

Oct. 22, 2018

[ANN] Next Pharo Sprint: Oct 26

by Marcus Denker

We will organize a Pharo sprint / Moose dojo Oct 26, starting at 10:00am. (Local Time Paris). Goals of this sprint: â¢ Pharo 7 issues Remote Sprint: Remotely, you can join us on Discord. During the sprint, we synchronize local and remote Pharo sprinters: http://pharo.org/contribute-events Known Local Sprint meetings Lille/France: It will be at the Inria Lille, Building B, third floor (RMoD offices). As the building is not open to the public, please contact us before if you plan to come https://association.pharo.org/event-2973622

Oct. 22, 2018

Re: [Pharo-users] Pharo2VW (Was:[vwnc] Parsing in Smalltalk)

by Alexandre Bergel

Thanks Steffen for your contribution to Pharo2VW. We reviewed and accepted your PullRequests. Alexandre > On Oct 19, 2018, at 6:29 AM, Steffen MÃ¤rcker <merkste(a)web.de> wrote: > > Nevermind, I figured it out easily. Must been blind before. > > Many thanks to the Iceberg team, the tool works like a charm in 6.1! > > > Am .10.2018, 10:58 Uhr, schrieb Steffen MÃ¤rcker <merkste(a)web.de>: > >> Hi, >> >> I tried the tool yesterday and found some hickups. After opening issues on GitHub, I wonder how I can easily contribute a PR there. I imagine there is a straight-forward way with Iceberg now, isn't it? I a sorry if I miss the obvious but I am still not familiar with Pharos comprehensive tool set. >> >> Best, Steffen >> >> >> Am .10.2018, 18:06 Uhr, schrieb milton mamani <akevalion(a)gmail.com>: >> >>> Hi you can use >>> >>> https://github.com/ObjectProfile/Pharo2VW >>> >>> Cheers, Milton >>> >>> El sÃ¡b., 13 oct. 2018 a las 12:38, Steffen MÃ¤rcker (<merkste(a)web.de>) >>> escribiÃ³: >>> >>>> Hi, >>>> >>>> I gave PetitParser 2 a try and I am pretty impressed by the results, >>>> please see the updated table below. =) Again, that's pure parsing and >>>> Array-based AST-building. Moving to PP2 was indeed as easy as sending >>>> #asPParser and working around character ranges ($a - $z). Is there a >>>> preferred way to do the latter? >>>> >>>> Jan mentioned that there might be an automated tool to port stuff to >>>> VisualWorks. Do you have a name? And again the old question: what is the >>>> preferred workflow to exchange code between the two dialects? Till now I >>>> stick to FileOut30. >>>> >>>> input Prism Storm Xtreams.PEG PP PP2 >>>> size parse check check parse cache parse parse optim >>>> 230kB 0.1s 10s 6s 9s 3s 2s 4s 0.2s >>>> 544kB 0.2s 90s 20s 20s 7s 5s 9s 0.5s >>>> 1.1MB 0.4s 392s 46s 34s 13s 8s 15s 1.0s >>>> 1.4MB 0.8s 1091s 85s 47s 20s 12s 20s 1.3s >>>> 2.2MB 63s 30s 16s 27s 1.9s >>>> 2.9MB 81s 44s 20s 34s 2.5s >>>> 3.8MB 107s 61s 25s 45s 3.1s >>>> 4.4MB 123s 76s 30s 56s 3.7s >>>> >>>> Best, Steffen >>>> >>>> >>>> Am .10.2018, 05:22 Uhr, schrieb Tudor Girba <tudor(a)tudorgirba.com>: >>>> >>>> > Hi, >>>> > >>>> > Interesting experiment. Thanks for sharing! >>>> > >>>> > I assume that you tried the original PetitParser. PetitParser2 offers >>>> > the possibility to optimize the parser (kind of a compilation), and >>>> this >>>> > provides a significant speedup: >>>> > https://github.com/kursjan/petitparser2 >>>> > >>>> > Would you be interested in trying this out? >>>> > >>>> > Cheers, >>>> > Doru >>>> > >>>> > >>>> > >>>> >> On Oct 4, 2018, at 10:46 PM, Steffen MÃ¤rcker <MerkSte(a)web.de> wrote: >>>> >> >>>> >> I gave Xtreams-Parsing and PetitParser a shot and like to share my >>>> >> findings.[*] >>>> >> >>>> >> The task was to parse the modelling language of the probabilistic >>>> model >>>> >> checker PRISM. I've written a grammer of about 130 definitions in the >>>> >> Xtreams DSL, which is close to Bryan Fords syntax. To avoid doing it >>>> >> all again with PetitParser, I wrote a PetitParserGenerator that takes >>>> >> the DSL and builds a PetitParser. >>>> >> >>>> >> The numbers below are just parsing times, no further actions involved. >>>> >> For reference I show the times from PRISM (which uses JavaCC), too -- >>>> >> although they involve additional verification and normalization steps >>>> >> on the AST. >>>> >> >>>> >> input Prism XP PP >>>> >> 230kB 14s 9s 2s >>>> >> 544kB 121s 20s 5s >>>> >> 1.1MB 421s 34s 8s >>>> >> 1.4MB 1091s 47s 12s >>>> >> 2.2MB 63s 16s >>>> >> 2.9MB 81s 20s >>>> >> 3.8MB 107s 25s >>>> >> 4.4MB 123s 30s >>>> >> >>>> >> Please note that these times are not representative at all. It's just >>>> a >>>> >> single example and I put zero effort in optimization. However, I am >>>> >> quite satisfied with the results. >>>> >> >>>> >> [*] I was already familiar with the DSL of Xtreams-Parsing, which I >>>> >> like very much. I did not consider SmaCC, as I find PEGs easier to use. >>>> >> >>>> >> Best, Steffen >>>> >> >>>> >> >>>> >> >>>> >> Am .10.2018, 20:14 Uhr, schrieb Steffen MÃ¤rcker <merkste(a)web.de>: >>>> >> >>>> >>> Dear all, >>>> >>> >>>> >>> I have two questions regarding parsing frameworks. >>>> >>> >>>> >>> 1) Do you have any insights on the performance of SmaCC VS Xtreams >>>> >>> Parsing VS PetitParser? >>>> >>> 2) Has anybody started to port PetitParser 2 from Pharo to VW? Is it >>>> >>> worth the effort? >>>> >>> >>>> >>> Sorry for cross-posting, I thought this might interest both >>>> >>> communities. >>>> >>> >>>> >>> Cheers, Steffen >>>> > >>>> > -- >>>> > www.feenk.com >>>> > >>>> > "No matter how many recipes we know, we still value a chef." >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >

Oct. 21, 2018

ring deprecation in pharo 7

by Tudor Girba

Hi, Ring seems to be deprecated in Pharo 7. Is there something else it will be replaced with? In particular, I am looking for the correct class that should correspond to RGMethodDefinition. Cheers, Doru -- www.feenk.com "Value is always contextual."

Oct. 19, 2018

Re: [Pharo-users] library to chain select:/collect:/ ... via cascade

by Steffen MÃ¤rcker

Another important difference is that no intermediate collections are built. In contrast, chaining x enumeration statements #select:, #collect:, etc. iterates x times over the collection elements and builds x-1 intermediate collections. Am .10.2018, 11:59 Uhr, schrieb Steffen MÃ¤rcker <merkste(a)web.de>: > Hi, > > indeed, transducers provided a way to achieve this, e.g. > > #(12 7 'a' nil #(0)) pipe > filter: #notNil; > filter: #isNumber; > map: #squared; > filter: #even; > into: OrderedCollection. > > But this feature is deprecated, as it was not that useful. The preferred > way to do this is either: > > #(12 7 'a' nil #(0)) > transduce: #notNil filter * #isNumber filter * squared map * #even > filter > reduce: Set accumulate. > > or: > > Set <~ #even filter > <~ #squared map > <~ #isNumber filter > <~ #notNil filter > <~ #(12 7 'a' nil #(0)). > > The advantage of the transducer approach is that it decouples > filtering/mapping/etc. from iteration and aggregation. This facilitates > reuse and makes it trivial to provide all operations to new custom data > types. > > However, I didn't have time to finish the Pharo port of Transducers, > yet. Hence, the a current version is available in Cincom's Public Store > or (most current) directly from me only. But if you are interested and > have a nice use case, I'd be happy to help out. > > Best, Steffen > > > Am .10.2018, 08:45 Uhr, schrieb Julien <julien.delplanque(a)inria.fr>: > >> I think this was the idea of Transducers as well. >> >> Julien >> >> --- >> Julien Delplanque >> Doctorant Ã lâUniversitÃ© de Lille >> http://juliendelplanque.be/phd.html >> Equipe Rmod, Inria >> BÃ¢timent B 40, Avenue Halley 59650 Villeneuve d'Ascq >> NumÃ©ro de tÃ©lÃ©phone: +333 59 35 86 40 >> <---Schnitt---> >

Oct. 19, 2018