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

Re: [Pharo-dev] Release test for unused temps and other

by Gabriel Cotelli

Hi Torsten, We experienced some similar problems with our builds at Mercap, because all the tests involving code analysis are orders of magnitude slower than the unit tests. What we do is: - When the programmer closes a unit of work (in that case it will be equivalent to create a PR) we run the tests involving this kind of code analysis only over the changed code - In the global build this tests are run in parallel (this wouldn't solve the pressure over the infrastructure, but improves the troughput of the whole build) I think this kind of tests totally worth the effort. Gabriel On Thu, Sep 6, 2018 at 12:51 PM Torsten Bergmann <astares(a)gmx.de> wrote: > Hi, > > the very nice contribution on GIFReadWriter/animated images (see > https://pharo.manuscript.com/f/cases/22137) > unfortunately introduced some methods that had no sender, were > uncategorized and had unused temporary variables, etc. > > Something that is meanwhile shown by our tools and easy to fix. I guess it > was some overseen leftover. Unfortunately this > also slipped through the integration process as it was merged without an > approval from a community reviewer. > > I dont want to lament too much on this specifc case (especially as I now > fixed it in https://pharo.fogbugz.com/f/cases/22426) > > But after I cleaned the P7 image this spring to not have unused > temporaries anymore I was suprised to find such > glitches again now. So to me it shows that we need to write more tests to > detect violations and keep our achieved quality standards > up and also should not solely rely on the review process. > > Otherwise we need to invest our time in cleaning up our own stuff > afterwards again and again. > > To be specific one can evaluate: > > CompiledMethod allInstances select: [:m | m ast temporaries > anySatisfy: [:x | x binding isUnused ]]. > > to find unused temps - which would be easy to package up into one of the > release test to ensure no unused temp vars are left > (the tearDown would require an "ASTCache reset"). > > The problem is that this simple test would take around 20-30 seconds > depending on machine and I do not know if it would be a > good idea/good solution to integrate. Especially I'm not sure if it is > worth the issue or will kill the CI again and again. > > What do you think about it? Comments appreciated? > > Thanks > T. > > > > >

Sept. 6, 2018

Re: [Pharo-dev] Streams and FileDialog in Pharo 6 and 7

by Peter Uhnak

> It should return a FileReference, not an open stream. I believe there are methods that do that. There are different APIs for that. fileOpen*, as the name implies, _opens the file_ and returns the stream. (I think this should be the case for fileSave*) If you want file reference, then you can use e.g. UIManager default chooseFileMatching: #() label: nil or `chooseFileMatching:label:`, `chooseFileName:extensions:path:preview:`, `chooseFullFileName:extensions:path:preview:`, `chooseFullFileNameMatching:label:`. Also some methods for selecting directories (`chooseDirectory:path:`, chooseDirectory:from:`, ...) iirc some of them actually return String (file path) instead of FileReference. ( https://gist.github.com/peteruhnak/8ac6667b8eb11daee71517d0172b7355#file-ui… ) So it can be confusing, but the API is already available. Also iirc UIManager should be preferred over UITheme builder. Peter On Thu, Sep 6, 2018 at 9:57 PM Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > > On 6 Sep 2018, at 21:37, Torsten Bergmann <astares(a)gmx.de> wrote: > > > > Hi, > > > > A question to those who worked on the new streams for Pharo 7: > > > > > > In PHARO 6 I used the following expression to open a file dialog and let > the user choose > > a binary file: > > > > s := UITheme builder fileOpen: 'Choose a file' extensions: #('exe'). > > > > This returned > > - either nil (when file dialog was canceled) > > - a "MultiByteFileStream" instance when a file was selected > > > > The MultiByteFileStream instance already had the name of the file (= > full path) and I was > > able to query it for further use: > > > > s := UITheme builder fileOpen: 'Choose a file' extensions: #('exe'). > > s name inspect > > > > (for instance to display which file is processed in a window by showing > the full path) > > > > > > > > Now in PHARO 7 same expression returns an instance of > ZnCharacterReadStream (as MultiByteFileStream > > is deprecated): > > > > s := UITheme builder fileOpen: 'Choose a file' extensions: #('exe'). > > > > and ZnCharacterReadStream does not understand #name - and in fact the > info about the name is > > totally lost/not available. To me this looks missing/broken. > > > > So what is the recommended way in Pharo 7 to open a file dialog, let the > use choose a file > > and get a file stream but also the name? IMHO this is either broken or > missing... > > > > Thanks > > T. > > It should return a FileReference, not an open stream. I believe there are > methods that do that. > > But that is an incompatible API change (same selector, different return > type). So hard to decide. > > >

Sept. 6, 2018

Re: [Pharo-dev] Status fo Stream changes in Pharo 7

by Sven Van Caekenberghe

> On 6 Sep 2018, at 21:42, Torsten Bergmann <astares(a)gmx.de> wrote: > > Hi, > > In Pharo 7 there were changes applied to rework the streams. I understand that we might have > reasons to change it - but to me this looks incomplete and not finished. > > For instance "FileStream" is a deprecated class - but still a lot of code in the > image is referencing it instead, > > Is there a guide or plan for all these methods being reworked to use a (hopefully > compatible) alternative. > > Can anyone involved in this topic give an update on the status? Yes, the transition is incomplete. There is an umbrella issue somewhere. Not all of it is easy ... > Thanks > T. >

Sept. 6, 2018

Re: [Pharo-dev] Streams and FileDialog in Pharo 6 and 7

by Sven Van Caekenberghe

> On 6 Sep 2018, at 21:37, Torsten Bergmann <astares(a)gmx.de> wrote: > > Hi, > > A question to those who worked on the new streams for Pharo 7: > > > In PHARO 6 I used the following expression to open a file dialog and let the user choose > a binary file: > > s := UITheme builder fileOpen: 'Choose a file' extensions: #('exe'). > > This returned > - either nil (when file dialog was canceled) > - a "MultiByteFileStream" instance when a file was selected > > The MultiByteFileStream instance already had the name of the file (= full path) and I was > able to query it for further use: > > s := UITheme builder fileOpen: 'Choose a file' extensions: #('exe'). > s name inspect > > (for instance to display which file is processed in a window by showing the full path) > > > > Now in PHARO 7 same expression returns an instance of ZnCharacterReadStream (as MultiByteFileStream > is deprecated): > > s := UITheme builder fileOpen: 'Choose a file' extensions: #('exe'). > > and ZnCharacterReadStream does not understand #name - and in fact the info about the name is > totally lost/not available. To me this looks missing/broken. > > So what is the recommended way in Pharo 7 to open a file dialog, let the use choose a file > and get a file stream but also the name? IMHO this is either broken or missing... > > Thanks > T. It should return a FileReference, not an open stream. I believe there are methods that do that. But that is an incompatible API change (same selector, different return type). So hard to decide.

Sept. 6, 2018

Re: [Pharo-dev] [Moose-dev] Re: [cormas-dev] Pharo eye-candy: Domain-Specific Modeling and Simulation

by Nick Papoylias

On Thu, Sep 6, 2018 at 9:28 PM Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > Bloc is a new world and the intention is to build a new stack on it. It > can be embedded in Morphic, This will have to do for now ;) Thanx for your great efforts ! > but not the other way around. Higher level frameworks, like Spec would > have to build a renderer for Bloc. > Cheers, > Doru > > > > > On Sep 6, 2018, at 8:45 PM, Nick Papoylias <npapoylias(a)gmail.com> wrote: > > > > Thanx Doru ! > > > > Any pointers on embeding Morphs/Specs/RTViews to the > > new GT tools (and vice versa), if possible ? > > > > I am looking to achive smth similar to what Johan and Stef did > > on Sec 9.1 of the Spec Book: "Integrating the different UI frameworks", > > but with the Bloc version of GT. > > > > > > > > On Thu, Sep 6, 2018 at 8:24 PM Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Nice job! > > > > Doru > > > > > > > > > On Sep 6, 2018, at 8:10 PM, Nick Papoylias <npapoylias(a)gmail.com> > wrote: > > > > > > Some of this tech, will soon make it to Cormas ;) > > > > > > So we can work together to make it even better ! > > > > > > Best, > > > > > > Nick > > > > > > On Thu, Sep 6, 2018 at 7:59 PM HernÃ¡n Morales Durand < > hernan.morales(a)gmail.com> wrote: > > > Impressive work! > > > > > > Congratulations Nick. > > > > > > Cheers, > > > > > > HernÃ¡n > > > > > > 2018-09-06 14:17 GMT-03:00 Nick Papoylias <npapoylias(a)gmail.com>: > > > > A nice example of how Pharo can be used for > > > > domain-specific modeling and simulation. Short > > > > session from one of our projects at Rochelle: > > > > > > > > https://www.youtube.com/watch?v=Z7wJNhAIaVQ > > > > > > > > Some additional info here: https://goo.gl/jS4NjB > > > > > > > > Currently investigating how to incorporate the new Bloc based > > > > widgets of @feenkcom into the workflow. > > > > > > > > Cheers, > > > > > > > > Nick > > > > > > > > -- > > > > You received this message because you are subscribed to the Google > Groups > > > > "cormas-dev" group. > > > > To unsubscribe from this group and stop receiving emails from it, > send an > > > > email to cormas-dev+unsubscribe(a)googlegroups.com. > > > > To post to this group, send email to cormas-dev(a)googlegroups.com. > > > > To view this discussion on the web visit > > > > > https://groups.google.com/d/msgid/cormas-dev/CACEStOjqbQt96qeae_4Nsf%3DEBqr… > . > > > > For more options, visit https://groups.google.com/d/optout. > > > > > > -- > > > You received this message because you are subscribed to the Google > Groups "cormas-dev" group. > > > To unsubscribe from this group and stop receiving emails from it, send > an email to cormas-dev+unsubscribe(a)googlegroups.com. > > > To post to this group, send email to cormas-dev(a)googlegroups.com. > > > To view this discussion on the web visit > https://groups.google.com/d/msgid/cormas-dev/CAKHmnHuSE38ureMsiAO5gHj5AJVzk… > . > > > For more options, visit https://groups.google.com/d/optout. > > > _______________________________________________ > > > Moose-dev mailing list > > > Moose-dev(a)list.inf.unibe.ch > > > https://www.list.inf.unibe.ch/listinfo/moose-dev > > > > -- > > www.feenk.com > > > > "No matter how many recipes we know, we still value a chef." > > > > > > > > > > > > > > > > > > _______________________________________________ > > Moose-dev mailing list > > Moose-dev(a)list.inf.unibe.ch > > https://www.list.inf.unibe.ch/listinfo/moose-dev > > _______________________________________________ > > Moose-dev mailing list > > Moose-dev(a)list.inf.unibe.ch > > https://www.list.inf.unibe.ch/listinfo/moose-dev > > -- > www.feenk.com > > âThe smaller and more pervasive the hardware becomes, the more physical > the software gets." > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev >

Sept. 6, 2018

Status fo Stream changes in Pharo 7

by Torsten Bergmann

Hi, In Pharo 7 there were changes applied to rework the streams. I understand that we might have reasons to change it - but to me this looks incomplete and not finished. For instance "FileStream" is a deprecated class - but still a lot of code in the image is referencing it instead, Is there a guide or plan for all these methods being reworked to use a (hopefully compatible) alternative. Can anyone involved in this topic give an update on the status? Thanks T.

Sept. 6, 2018

Streams and FileDialog in Pharo 6 and 7

by Torsten Bergmann

Hi, A question to those who worked on the new streams for Pharo 7: In PHARO 6 I used the following expression to open a file dialog and let the user choose a binary file: s := UITheme builder fileOpen: 'Choose a file' extensions: #('exe'). This returned - either nil (when file dialog was canceled) - a "MultiByteFileStream" instance when a file was selected The MultiByteFileStream instance already had the name of the file (= full path) and I was able to query it for further use: s := UITheme builder fileOpen: 'Choose a file' extensions: #('exe'). s name inspect (for instance to display which file is processed in a window by showing the full path) Now in PHARO 7 same expression returns an instance of ZnCharacterReadStream (as MultiByteFileStream is deprecated): s := UITheme builder fileOpen: 'Choose a file' extensions: #('exe'). and ZnCharacterReadStream does not understand #name - and in fact the info about the name is totally lost/not available. To me this looks missing/broken. So what is the recommended way in Pharo 7 to open a file dialog, let the use choose a file and get a file stream but also the name? IMHO this is either broken or missing... Thanks T.

Sept. 6, 2018

Re: [Pharo-dev] [Moose-dev] [cormas-dev] Pharo eye-candy: Domain-Specific Modeling and Simulation

by Tudor Girba

Hi, Bloc is a new world and the intention is to build a new stack on it. It can be embedded in Morphic, but not the other way around. Higher level frameworks, like Spec would have to build a renderer for Bloc. Cheers, Doru > On Sep 6, 2018, at 8:45 PM, Nick Papoylias <npapoylias(a)gmail.com> wrote: > > Thanx Doru ! > > Any pointers on embeding Morphs/Specs/RTViews to the > new GT tools (and vice versa), if possible ? > > I am looking to achive smth similar to what Johan and Stef did > on Sec 9.1 of the Spec Book: "Integrating the different UI frameworks", > but with the Bloc version of GT. > > > > On Thu, Sep 6, 2018 at 8:24 PM Tudor Girba <tudor(a)tudorgirba.com> wrote: > Nice job! > > Doru > > > > > On Sep 6, 2018, at 8:10 PM, Nick Papoylias <npapoylias(a)gmail.com> wrote: > > > > Some of this tech, will soon make it to Cormas ;) > > > > So we can work together to make it even better ! > > > > Best, > > > > Nick > > > > On Thu, Sep 6, 2018 at 7:59 PM HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > > Impressive work! > > > > Congratulations Nick. > > > > Cheers, > > > > HernÃ¡n > > > > 2018-09-06 14:17 GMT-03:00 Nick Papoylias <npapoylias(a)gmail.com>: > > > A nice example of how Pharo can be used for > > > domain-specific modeling and simulation. Short > > > session from one of our projects at Rochelle: > > > > > > https://www.youtube.com/watch?v=Z7wJNhAIaVQ > > > > > > Some additional info here: https://goo.gl/jS4NjB > > > > > > Currently investigating how to incorporate the new Bloc based > > > widgets of @feenkcom into the workflow. > > > > > > Cheers, > > > > > > Nick > > > > > > -- > > > You received this message because you are subscribed to the Google Groups > > > "cormas-dev" group. > > > To unsubscribe from this group and stop receiving emails from it, send an > > > email to cormas-dev+unsubscribe(a)googlegroups.com. > > > To post to this group, send email to cormas-dev(a)googlegroups.com. > > > To view this discussion on the web visit > > > https://groups.google.com/d/msgid/cormas-dev/CACEStOjqbQt96qeae_4Nsf%3DEBqr…. > > > For more options, visit https://groups.google.com/d/optout. > > > > -- > > You received this message because you are subscribed to the Google Groups "cormas-dev" group. > > To unsubscribe from this group and stop receiving emails from it, send an email to cormas-dev+unsubscribe(a)googlegroups.com. > > To post to this group, send email to cormas-dev(a)googlegroups.com. > > To view this discussion on the web visit https://groups.google.com/d/msgid/cormas-dev/CAKHmnHuSE38ureMsiAO5gHj5AJVzk…. > > For more options, visit https://groups.google.com/d/optout. > > _______________________________________________ > > Moose-dev mailing list > > Moose-dev(a)list.inf.unibe.ch > > https://www.list.inf.unibe.ch/listinfo/moose-dev > > -- > www.feenk.com > > "No matter how many recipes we know, we still value a chef." > > > > > > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev -- www.feenk.com âThe smaller and more pervasive the hardware becomes, the more physical the software gets."

Sept. 6, 2018

Re: [Pharo-dev] [Moose-dev] Re: [cormas-dev] Pharo eye-candy: Domain-Specific Modeling and Simulation

by Nick Papoylias

Thanx Doru ! Any pointers on embeding Morphs/Specs/RTViews to the new GT tools (and vice versa), if possible ? I am looking to achive smth similar to what Johan and Stef did on Sec 9.1 of the Spec Book <http://files.pharo.org/books-pdfs/spec/2017-01-23-SpecBooklet.pdf>: "Integrating the different UI frameworks", but with the Bloc version of GT. On Thu, Sep 6, 2018 at 8:24 PM Tudor Girba <tudor(a)tudorgirba.com> wrote: > Nice job! > > Doru > > > > > On Sep 6, 2018, at 8:10 PM, Nick Papoylias <npapoylias(a)gmail.com> wrote: > > > > Some of this tech, will soon make it to Cormas ;) > > > > So we can work together to make it even better ! > > > > Best, > > > > Nick > > > > On Thu, Sep 6, 2018 at 7:59 PM HernÃ¡n Morales Durand < > hernan.morales(a)gmail.com> wrote: > > Impressive work! > > > > Congratulations Nick. > > > > Cheers, > > > > HernÃ¡n > > > > 2018-09-06 14:17 GMT-03:00 Nick Papoylias <npapoylias(a)gmail.com>: > > > A nice example of how Pharo can be used for > > > domain-specific modeling and simulation. Short > > > session from one of our projects at Rochelle: > > > > > > https://www.youtube.com/watch?v=Z7wJNhAIaVQ > > > > > > Some additional info here: https://goo.gl/jS4NjB > > > > > > Currently investigating how to incorporate the new Bloc based > > > widgets of @feenkcom into the workflow. > > > > > > Cheers, > > > > > > Nick > > > > > > -- > > > You received this message because you are subscribed to the Google > Groups > > > "cormas-dev" group. > > > To unsubscribe from this group and stop receiving emails from it, send > an > > > email to cormas-dev+unsubscribe(a)googlegroups.com. > > > To post to this group, send email to cormas-dev(a)googlegroups.com. > > > To view this discussion on the web visit > > > > https://groups.google.com/d/msgid/cormas-dev/CACEStOjqbQt96qeae_4Nsf%3DEBqr… > . > > > For more options, visit https://groups.google.com/d/optout. > > > > -- > > You received this message because you are subscribed to the Google > Groups "cormas-dev" group. > > To unsubscribe from this group and stop receiving emails from it, send > an email to cormas-dev+unsubscribe(a)googlegroups.com. > > To post to this group, send email to cormas-dev(a)googlegroups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/cormas-dev/CAKHmnHuSE38ureMsiAO5gHj5AJVzk… > . > > For more options, visit https://groups.google.com/d/optout. > > _______________________________________________ > > Moose-dev mailing list > > Moose-dev(a)list.inf.unibe.ch > > https://www.list.inf.unibe.ch/listinfo/moose-dev > > -- > www.feenk.com > > "No matter how many recipes we know, we still value a chef." > > > > > > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev >

Sept. 6, 2018

Re: [Pharo-dev] [cormas-dev] Pharo eye-candy: Domain-Specific Modeling and Simulation

by serge.stinckwich＠gmail.com

Great ! A presentation of CORMAS simulation platform will be done at next ESUG. See you there. EnvoyÃ© de mon iPhone > Le 6 sept. 2018 Ã 19:17, Nick Papoylias <npapoylias(a)gmail.com> a Ã©crit : > > A nice example of how Pharo can be used for > domain-specific modeling and simulation. Short > session from one of our projects at Rochelle: > > https://www.youtube.com/watch?v=Z7wJNhAIaVQ > > Some additional info here: https://goo.gl/jS4NjB > > Currently investigating how to incorporate the new Bloc based > widgets of @feenkcom into the workflow. > > Cheers, > > Nick > -- > You received this message because you are subscribed to the Google Groups "cormas-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an email to cormas-dev+unsubscribe(a)googlegroups.com. > To post to this group, send email to cormas-dev(a)googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/msgid/cormas-dev/CACEStOjqbQt96qeae_4Nsf%3DEBqr…. > For more options, visit https://groups.google.com/d/optout.

Sept. 6, 2018

Re: [Pharo-dev] [Moose-dev] [cormas-dev] Pharo eye-candy: Domain-Specific Modeling and Simulation

by Tudor Girba

Nice job! Doru > On Sep 6, 2018, at 8:10 PM, Nick Papoylias <npapoylias(a)gmail.com> wrote: > > Some of this tech, will soon make it to Cormas ;) > > So we can work together to make it even better ! > > Best, > > Nick > > On Thu, Sep 6, 2018 at 7:59 PM HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > Impressive work! > > Congratulations Nick. > > Cheers, > > HernÃ¡n > > 2018-09-06 14:17 GMT-03:00 Nick Papoylias <npapoylias(a)gmail.com>: > > A nice example of how Pharo can be used for > > domain-specific modeling and simulation. Short > > session from one of our projects at Rochelle: > > > > https://www.youtube.com/watch?v=Z7wJNhAIaVQ > > > > Some additional info here: https://goo.gl/jS4NjB > > > > Currently investigating how to incorporate the new Bloc based > > widgets of @feenkcom into the workflow. > > > > Cheers, > > > > Nick > > > > -- > > You received this message because you are subscribed to the Google Groups > > "cormas-dev" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to cormas-dev+unsubscribe(a)googlegroups.com. > > To post to this group, send email to cormas-dev(a)googlegroups.com. > > To view this discussion on the web visit > > https://groups.google.com/d/msgid/cormas-dev/CACEStOjqbQt96qeae_4Nsf%3DEBqr…. > > For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups "cormas-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an email to cormas-dev+unsubscribe(a)googlegroups.com. > To post to this group, send email to cormas-dev(a)googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/msgid/cormas-dev/CAKHmnHuSE38ureMsiAO5gHj5AJVzk…. > For more options, visit https://groups.google.com/d/optout. > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev -- www.feenk.com "No matter how many recipes we know, we still value a chef."

Sept. 6, 2018

Re: [Pharo-dev] [cormas-dev] Pharo eye-candy: Domain-Specific Modeling and Simulation

by Nick Papoylias

Some of this tech, will soon make it to Cormas ;) So we can work together to make it even better ! Best, Nick On Thu, Sep 6, 2018 at 7:59 PM HernÃ¡n Morales Durand < hernan.morales(a)gmail.com> wrote: > Impressive work! > > Congratulations Nick. > > Cheers, > > HernÃ¡n > > 2018-09-06 14:17 GMT-03:00 Nick Papoylias <npapoylias(a)gmail.com>: > > A nice example of how Pharo can be used for > > domain-specific modeling and simulation. Short > > session from one of our projects at Rochelle: > > > > https://www.youtube.com/watch?v=Z7wJNhAIaVQ > > > > Some additional info here: https://goo.gl/jS4NjB > > > > Currently investigating how to incorporate the new Bloc based > > widgets of @feenkcom into the workflow. > > > > Cheers, > > > > Nick > > > > -- > > You received this message because you are subscribed to the Google Groups > > "cormas-dev" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to cormas-dev+unsubscribe(a)googlegroups.com. > > To post to this group, send email to cormas-dev(a)googlegroups.com. > > To view this discussion on the web visit > > > https://groups.google.com/d/msgid/cormas-dev/CACEStOjqbQt96qeae_4Nsf%3DEBqr… > . > > For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "cormas-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to cormas-dev+unsubscribe(a)googlegroups.com. > To post to this group, send email to cormas-dev(a)googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/cormas-dev/CAKHmnHuSE38ureMsiAO5gHj5AJVzk… > . > For more options, visit https://groups.google.com/d/optout. >

Sept. 6, 2018

Re: [Pharo-dev] [cormas-dev] Pharo eye-candy: Domain-Specific Modeling and Simulation

by HernÃ¡n Morales Durand

Impressive work! Congratulations Nick. Cheers, HernÃ¡n 2018-09-06 14:17 GMT-03:00 Nick Papoylias <npapoylias(a)gmail.com>: > A nice example of how Pharo can be used for > domain-specific modeling and simulation. Short > session from one of our projects at Rochelle: > > https://www.youtube.com/watch?v=Z7wJNhAIaVQ > > Some additional info here: https://goo.gl/jS4NjB > > Currently investigating how to incorporate the new Bloc based > widgets of @feenkcom into the workflow. > > Cheers, > > Nick > > -- > You received this message because you are subscribed to the Google Groups > "cormas-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to cormas-dev+unsubscribe(a)googlegroups.com. > To post to this group, send email to cormas-dev(a)googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/cormas-dev/CACEStOjqbQt96qeae_4Nsf%3DEBqr…. > For more options, visit https://groups.google.com/d/optout.

Sept. 6, 2018

Pharo eye-candy: Domain-Specific Modeling and Simulation

by Nick Papoylias

A nice example of how Pharo can be used for domain-specific modeling and simulation. Short session from one of our projects at Rochelle: https://www.youtube.com/watch?v=Z7wJNhAIaVQ Some additional info here: https://goo.gl/jS4NjB Currently investigating how to incorporate the new Bloc based widgets of @feenkcom into the workflow. Cheers, Nick

Sept. 6, 2018

[Pharo 7.0-dev] Build #1231: 22423 Correctly deprecate MatrixTest

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1231 was: SUCCESS. The Pull Request #1774 was integrated: "22423 Correctly deprecate MatrixTest" Pull request url: https://github.com/pharo-project/pharo/pull/1774 Issue Url: https://pharo.fogbugz.com/f/cases/22423 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 6, 2018

Release test for unused temps and other

by Torsten Bergmann

Hi, the very nice contribution on GIFReadWriter/animated images (see https://pharo.manuscript.com/f/cases/22137) unfortunately introduced some methods that had no sender, were uncategorized and had unused temporary variables, etc. Something that is meanwhile shown by our tools and easy to fix. I guess it was some overseen leftover. Unfortunately this also slipped through the integration process as it was merged without an approval from a community reviewer. I dont want to lament too much on this specifc case (especially as I now fixed it in https://pharo.fogbugz.com/f/cases/22426) But after I cleaned the P7 image this spring to not have unused temporaries anymore I was suprised to find such glitches again now. So to me it shows that we need to write more tests to detect violations and keep our achieved quality standards up and also should not solely rely on the review process. Otherwise we need to invest our time in cleaning up our own stuff afterwards again and again. To be specific one can evaluate: CompiledMethod allInstances select: [:m | m ast temporaries anySatisfy: [:x | x binding isUnused ]]. to find unused temps - which would be easy to package up into one of the release test to ensure no unused temp vars are left (the tearDown would require an "ASTCache reset"). The problem is that this simple test would take around 20-30 seconds depending on machine and I do not know if it would be a good idea/good solution to integrate. Especially I'm not sure if it is worth the issue or will kill the CI again and again. What do you think about it? Comments appreciated? Thanks T.

Sept. 6, 2018

[Pharo 7.0-dev] Build #1230: 22421 fogbugz is now manuscript

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1230 was: FAILURE. The Pull Request #1772 was integrated: "22421 fogbugz is now manuscript" Pull request url: https://github.com/pharo-project/pharo/pull/1772 Issue Url: https://pharo.fogbugz.com/f/cases/22421 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 6, 2018

[Pharo 7.0-dev] Build #1229: 22419 Complete class comments in Kernel-Tests

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1229 was: FAILURE. The Pull Request #1770 was integrated: "22419 Complete class comments in Kernel-Tests" Pull request url: https://github.com/pharo-project/pharo/pull/1770 Issue Url: https://pharo.fogbugz.com/f/cases/22419 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 6, 2018

[Pharo 7.0-dev] Build #1228: 22418 Cleanup DateAndTimeDosEpochTest

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1228 was: FAILURE. The Pull Request #1768 was integrated: "22418 Cleanup DateAndTimeDosEpochTest" Pull request url: https://github.com/pharo-project/pharo/pull/1768 Issue Url: https://pharo.fogbugz.com/f/cases/22418 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 6, 2018

Why being a Pharo Association Member matters?

by StÃ©phane Ducasse

Hi Pharo supporters First I would like thank you. And I would like to show you that your membership in the Pharo association is really helping Pharo. We are creating a precise report but the main message is the same. You concretely help Pharo. First, we would like to really thank you for your support because as you will see it is important. Your contributions are making an impact. Until now, the association did not make visible how was spent the money from your membership. It's time to fix this. In the first place, the support we got from last year enable the creation of monthly activities helping with the development of Pharo. The association is now the support for the following ones: Sprint organisations: Every month sprints to correct Pharo bugs are organised. You can join remotely or organise one at your location TechTalks: Every month a technical talk is been done to give visibility on Pharo process and Pharo projects and interact with the community to get feedback Next, your association contributions are securing vital Pharo infrastructures. It pays: The domains such as pharo.org. The hosting files.pharo.org: This year we moved out of Inria infrastructure because we could not identify the cause of a huge network latency. It got resolved - it was a fiber which was in bad condition but not cut. This was fixed at the level of Renater national back-bone layer, but we decided to stay outside. We plan to migrate to a better service. The wild apricot software which manages the association. It will enable us to do more with the association. (40$/month) The newsletter via Mailchimp. This newsletter is a real success with more than 2300 recipients . You get see the archive at https://us11.campaign-archive.com/home/?u=6f667565c2569234585a7be77&id=0486… <https://us11.campaign-archive.com/home/?u=6f667565c2569234585a7be77&id=0486…> (30$/month) The mailing-lists are managed with Mailname a professional service. On another note, we would like to remember the advantages of being an association member: Reduction for the PharoDays Offer access to PharoCloud (which is currently under redesign) 20% Discount on the printed book Learning Object-Oriented Programming, Design with TDD in Pharo <http://books.pharo.org/learning-oop/> Possibility to be listed as a Pharo consultant (Require gold membership) -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr http://www.synectique.eu / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

Sept. 6, 2018

[Pharo 7.0-dev] Build #1227: 22416 Tag Manifest in Kernel-Tests

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1227 was: SUCCESS. The Pull Request #1767 was integrated: "22416 Tag Manifest in Kernel-Tests" Pull request url: https://github.com/pharo-project/pharo/pull/1767 Issue Url: https://pharo.fogbugz.com/f/cases/22416 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 6, 2018

[Pharo 7.0-dev] Build #1226: 22412-Typo-closeclosed-in-AbstractBinaryFileStream--nextputAll

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1226 was: SUCCESS. The Pull Request #1765 was integrated: "22412-Typo-closeclosed-in-AbstractBinaryFileStream--nextputAll" Pull request url: https://github.com/pharo-project/pharo/pull/1765 Issue Url: https://pharo.fogbugz.com/f/cases/22412 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 6, 2018

[Pharo 7.0-dev] Build #1225: 22026-Date-little-improvement-proposal-DateAndTime

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1225 was: SUCCESS. The Pull Request #1747 was integrated: "22026-Date-little-improvement-proposal-DateAndTime" Pull request url: https://github.com/pharo-project/pharo/pull/1747 Issue Url: https://pharo.fogbugz.com/f/cases/22026 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 5, 2018

Re: [Pharo-dev] Auto-completion of methods names

by Cyril Ferlicot D.

Le 05/09/2018 Ã 10:00, Marcus Denker a Ã©critÂ : > > I will add a simpler version by default back (today). > > The old version tried to be clever and replace whole methodsâ¦ which was extremely confusing (and not really > helping). It complicated the model, too. > (We got even bug report > > Method name completion is nice, it is very easy to add method name completion back, I will do it today. > Great, thank you! I'm glad that it's not just a feature removal without replacement :) > Marcus > > -- Cyril Ferlicot https://ferlicot.fr

Sept. 5, 2018

[Pharo 7.0-dev] Build #1224: 22025-Date-little-improvement-proposal-

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1224 was: FAILURE. The Pull Request #1755 was integrated: "22025-Date-little-improvement-proposal-" Pull request url: https://github.com/pharo-project/pharo/pull/1755 Issue Url: https://pharo.fogbugz.com/f/cases/22025 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 5, 2018

[Pharo 7.0-dev] Build #1223: 22409-ProperMethodCategorizationTesttestTearDownMethodInSUnitTestsNeedsToBeInRunningProtocol

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1223 was: SUCCESS. The Pull Request #1764 was integrated: "22409-ProperMethodCategorizationTesttestTearDownMethodInSUnitTestsNeedsToBeInRunningProtocol" Pull request url: https://github.com/pharo-project/pharo/pull/1764 Issue Url: https://pharo.fogbugz.com/f/cases/22409 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 5, 2018

[Pharo 7.0-dev] Build #1222: 22408-Ecompletion-remove-some-methods-with-no-senders

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1222 was: SUCCESS. The Pull Request #1763 was integrated: "22408-Ecompletion-remove-some-methods-with-no-senders" Pull request url: https://github.com/pharo-project/pharo/pull/1763 Issue Url: https://pharo.fogbugz.com/f/cases/22408 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 5, 2018

Re: [Pharo-dev] Auto-completion of methods names

by Marcus Denker

> On 4 Sep 2018, at 21:49, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: > > Hi, > > Today I tried to launch a Pharo 7 image and I just saw that one of my > setting was failing. > > The setting is from NEC and allow to auto-complete the method name and > could be enable like this: > > NECPreferences overrideModel: true > > In the recent Pharo 7, #overrideModel: and all the code depending on it > was removed. > > Is there an other way to get this feature or will it just be removed > totally from Pharo 7? > I will add a simpler version by default back (today). The old version tried to be clever and replace whole methodsâ¦ which was extremely confusing (and not really helping). It complicated the model, too. (We got even bug report Method name completion is nice, it is very easy to add method name completion back, I will do it today. Marcus

Sept. 5, 2018

Auto-completion of methods names

by Cyril Ferlicot D.

Hi, Today I tried to launch a Pharo 7 image and I just saw that one of my setting was failing. The setting is from NEC and allow to auto-complete the method name and could be enable like this: NECPreferences overrideModel: true In the recent Pharo 7, #overrideModel: and all the code depending on it was removed. Is there an other way to get this feature or will it just be removed totally from Pharo 7? -- Cyril Ferlicot https://ferlicot.fr

Sept. 4, 2018

[Pharo 7.0-dev] Build #1221: 22387 Allow dynamic spec builder to specify a different presenter for each model object.

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1221 was: FAILURE. The Pull Request #1744 was integrated: "22387 Allow dynamic spec builder to specify a different presenter for each model object." Pull request url: https://github.com/pharo-project/pharo/pull/1744 Issue Url: https://pharo.fogbugz.com/f/cases/22387 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 4, 2018

[Pharo7] completion: enabled method preview

by Marcus Denker

Hi, In the last build, we enabled by default the method preview in the code completion dialog. (this is left-arrow). In addition, some cleanups should have made opening the menu the first time faster.

Sept. 4, 2018

[Pharo 7.0-dev] Build #1220: 22401-make-NECContext-pluggable

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1220 was: SUCCESS. The Pull Request #1761 was integrated: "22401-make-NECContext-pluggable" Pull request url: https://github.com/pharo-project/pharo/pull/1761 Issue Url: https://pharo.fogbugz.com/f/cases/22401 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 4, 2018

[Pharo 7.0-dev] Build #1219: 22391-NECompletion-clean-up-switchToUntyped

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1219 was: SUCCESS. The Pull Request #1758 was integrated: "22391-NECompletion-clean-up-switchToUntyped" Pull request url: https://github.com/pharo-project/pharo/pull/1758 Issue Url: https://pharo.fogbugz.com/f/cases/22391 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 4, 2018

[Pharo 7.0-dev] Build #1218: 22398-speed-up-NECSymbolCache-interestingSymbolsDo

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1218 was: FAILURE. The Pull Request #1757 was integrated: "22398-speed-up-NECSymbolCache-interestingSymbolsDo" Pull request url: https://github.com/pharo-project/pharo/pull/1757 Issue Url: https://pharo.fogbugz.com/f/cases/22398 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 4, 2018

[Pharo 7.0-dev] Build #1217: 22022--Date-little-improvement-proposal--YearcurrentYear

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1217 was: SUCCESS. The Pull Request #1754 was integrated: "22022--Date-little-improvement-proposal--YearcurrentYear" Pull request url: https://github.com/pharo-project/pharo/pull/1754 Issue Url: https://pharo.fogbugz.com/f/cases/22022 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 3, 2018

[Pharo 7.0-dev] Build #1216: 22239-DataAndTimeTesttestAsDateAndTime-is-meaningful

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1216 was: SUCCESS. The Pull Request #1737 was integrated: "22239-DataAndTimeTesttestAsDateAndTime-is-meaningful" Pull request url: https://github.com/pharo-project/pharo/pull/1737 Issue Url: https://pharo.fogbugz.com/f/cases/22239 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 3, 2018

[Pharo 7.0-dev] Build #1215: 22364 renraku rule to check that a subclass of test case has its name ending with test

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1215 was: FAILURE. The Pull Request #1717 was integrated: "22364 renraku rule to check that a subclass of test case has its name ending with test" Pull request url: https://github.com/pharo-project/pharo/pull/1717 Issue Url: https://pharo.fogbugz.com/f/cases/22364 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 2, 2018

[Pharo 7.0-dev] Build #1214: 22022--Date-little-improvement-proposal--YearcurrentYear

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1214 was: FAILURE. The Pull Request #1742 was integrated: "22022--Date-little-improvement-proposal--YearcurrentYear" Pull request url: https://github.com/pharo-project/pharo/pull/1742 Issue Url: https://pharo.fogbugz.com/f/cases/22022 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 2, 2018

Re: [Pharo-dev] Promote new Pharo 7 VM (d952580)

by Alistair Grant

Hi Esteban, I've found a UTF8 coding issue on Windows in the plugin. I'll have to resolve that, so no hurry on the release now (I'll also update FileSystemTest>>testFileNames so it is covered). Sorry for the noise. Thanks, Alistair On Sat, 1 Sep 2018 at 11:13, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hi, > > Iâm currently in holidays, I will start the process next monday :) > > Esteban > > > > On 30 Aug 2018, at 10:38, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > > > Hi Esteban and Everyone, > > > > I would like to request we start the process for promoting a new Pharo 7 > > VM. d952580 (vmLatest as I write this) has two changes that I'm > > looking forward to: > > > > - Fix path encoding / decoding on OSX > > Hopefully this will finally allow me to submit the File Attributes > > changes (fogbugz 18279[1] & 21368[2]). > > - Add primitiveChangeMode(), primitiveChangeOwner() and > > primitiveSymlinkChangeOwner() > > This will allow Pharo to set file owner & group IDs and posix > > permissions on Unix platforms (Linux & OSX). > > > > > > Other changes include: > > > > - stdio is flagged correctly on Windows > > - Windows 64 bit work > > - fflush added to sqFileTruncate() > > - Eliot's work on Cog > > - Everything else I've missed :-) (sorry to those authors) > > > > > > Running the automated test suite on Linux 32 bit, Linux 64 bit and > > Windows 32 bit produces basically the same set of failures with the > > current stable VM and the proposed VM. > > > > [1] https://pharo.fogbugz.com/f/cases/18279/isSymlink-seems-to-be-broken-on-Lin… > > [2] https://pharo.fogbugz.com/f/cases/21368/Integrate-FileAttributesPlugin > > > > > > Thanks, > > Alistair > > > >

Sept. 2, 2018

[Pharo 7.0-dev] Build #1213: 22025-Date-little-improvement-proposal-

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1213 was: SUCCESS. The Pull Request #1746 was integrated: "22025-Date-little-improvement-proposal-" Pull request url: https://github.com/pharo-project/pharo/pull/1746 Issue Url: https://pharo.fogbugz.com/f/cases/22025 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 2, 2018

[Pharo 7.0-dev] Build #1212: 22382-atWrap-and-atWrapput-should-be-better-commented-and-have-an-executable-comment

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1212 was: SUCCESS. The Pull Request #1739 was integrated: "22382-atWrap-and-atWrapput-should-be-better-commented-and-have-an-executable-comment" Pull request url: https://github.com/pharo-project/pharo/pull/1739 Issue Url: https://pharo.fogbugz.com/f/cases/22382 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 2, 2018

Re: [Pharo-dev] Promote new Pharo 7 VM (d952580)

by Esteban Lorenzano

Hi, Iâm currently in holidays, I will start the process next monday :) Esteban > On 30 Aug 2018, at 10:38, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > Hi Esteban and Everyone, > > I would like to request we start the process for promoting a new Pharo 7 > VM. d952580 (vmLatest as I write this) has two changes that I'm > looking forward to: > > - Fix path encoding / decoding on OSX > Hopefully this will finally allow me to submit the File Attributes > changes (fogbugz 18279[1] & 21368[2]). > - Add primitiveChangeMode(), primitiveChangeOwner() and > primitiveSymlinkChangeOwner() > This will allow Pharo to set file owner & group IDs and posix > permissions on Unix platforms (Linux & OSX). > > > Other changes include: > > - stdio is flagged correctly on Windows > - Windows 64 bit work > - fflush added to sqFileTruncate() > - Eliot's work on Cog > - Everything else I've missed :-) (sorry to those authors) > > > Running the automated test suite on Linux 32 bit, Linux 64 bit and > Windows 32 bit produces basically the same set of failures with the > current stable VM and the proposed VM. > > [1] https://pharo.fogbugz.com/f/cases/18279/isSymlink-seems-to-be-broken-on-Lin… > [2] https://pharo.fogbugz.com/f/cases/21368/Integrate-FileAttributesPlugin > > > Thanks, > Alistair >

Sept. 1, 2018

[Pharo 7.0-dev] Build #1211: 22389-remove-NECOverrideModel

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1211 was: FAILURE. The Pull Request #1749 was integrated: "22389-remove-NECOverrideModel" Pull request url: https://github.com/pharo-project/pharo/pull/1749 Issue Url: https://pharo.fogbugz.com/f/cases/22389 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 1, 2018

[Pharo 7.0-dev] Build #1210: 21708-Epicea-should-not-offer-to-recover-changes-if-the-ombu-file-does-not-exists

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1210 was: SUCCESS. The Pull Request #1721 was integrated: "21708-Epicea-should-not-offer-to-recover-changes-if-the-ombu-file-does-not-exists" Pull request url: https://github.com/pharo-project/pharo/pull/1721 Issue Url: https://pharo.fogbugz.com/f/cases/21708 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 1, 2018

[Pharo 7.0-dev] Build #1209: 22392-messages-in-String-need-more-executable-comments

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1209 was: SUCCESS. The Pull Request #1752 was integrated: "22392-messages-in-String-need-more-executable-comments" Pull request url: https://github.com/pharo-project/pharo/pull/1752 Issue Url: https://pharo.fogbugz.com/f/cases/22392 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 1, 2018