July 2019 - Pharo-dev - lists.pharo.org

[Pharo 8.0] Build #426: 3739-Rules-override-wrong-method
by ci-pharo-ci-jenkins2＠inria.fr July 4, 2019

July 4, 2019

There is a new Pharo build available! The status of the build #426 was: SUCCESS. The Pull Request #3751 was integrated: "3739-Rules-override-wrong-method" Pull request url: https://github.com/pharo-project/pharo/pull/3751 Issue Url: https://github.com/pharo-project/pharo/issues/3739 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #425: [comment] attempt to remove an ambiguity in #pinnedInMemory's comment.
by ci-pharo-ci-jenkins2＠inria.fr July 3, 2019

July 3, 2019

There is a new Pharo build available! The status of the build #425 was: FAILURE. The Pull Request #3756 was integrated: "[comment] attempt to remove an ambiguity in #pinnedInMemory's comment." Pull request url: https://github.com/pharo-project/pharo/pull/3756 Issue Url: https://github.com/pharo-project/pharo/issues/Pharo8.0 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #424: 3753-improve-code-completion-for-temps
by ci-pharo-ci-jenkins2＠inria.fr July 3, 2019

July 3, 2019

There is a new Pharo build available! The status of the build #424 was: SUCCESS. The Pull Request #3754 was integrated: "3753-improve-code-completion-for-temps" Pull request url: https://github.com/pharo-project/pharo/pull/3754 Issue Url: https://github.com/pharo-project/pharo/issues/3753 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #423: 3745-Simplify-CompiledMethod-overriddenMethods
by ci-pharo-ci-jenkins2＠inria.fr July 3, 2019

July 3, 2019

There is a new Pharo build available! The status of the build #423 was: FAILURE. The Pull Request #3746 was integrated: "3745-Simplify-CompiledMethod-overriddenMethods" Pull request url: https://github.com/pharo-project/pharo/pull/3746 Issue Url: https://github.com/pharo-project/pharo/issues/3726 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Re: [Pharo-dev] Test Completion has been added to Pharo 8 - please test!
by Myroslava Romaniuk July 3, 2019

July 3, 2019

Also if anyone has an idea why when i send an email to the mailing lists, duplicate emails are sent out, and how to fix it, i would be super grateful. Thanks, Myroslava On Wed, 3 Jul 2019 at 16:58, Myroslava Romaniuk via Pharo-dev < pharo-dev(a)lists.pharo.org> wrote: > Hi Stef > > So the more detailed instruction with the screenshot is in the blog post : > https://medium.com/@myroslavarm/test-code-completion-has-been-added-to-phar…, > but simply put: > if you go to settings, type in 'completion' in the search bar, and where > it says 'controller' change it to 'TestCompletionController', you will have > it. > > It will be inside the environment instead of the regular completion, so > any time you type something in playground or editor, it will be the test > completion that is triggered. Basically to test it you only need to be > coding something in Pharo :) So if you use it and it breaks somewhere, let > us know. > > Best regards, > Myroslava > > On Wed, 3 Jul 2019 at 15:27, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > wrote: > >> Hi miroslava >> >> how can we test it? >> >> Stef >> >> On 3 Jul 2019, at 01:11, Myroslava Romaniuk <romaniuk(a)ucu.edu.ua> wrote: >> >> >> *From: *Myroslava Romaniuk <romaniuk(a)ucu.edu.ua> >> *Subject: **Test Completion has been added to Pharo 8 - please test!* >> *Date: *3 July 2019 at 01:11:51 GMT+9 >> *To: *Pharo Development List <pharo-dev(a)lists.pharo.org>, Any question >> about pharo is welcome <pharo-users(a)lists.pharo.org> >> >> >> Hi all, >> >> we added an intermediate version of the upcoming test completion to Pharo >> 8, it would be cool if you tested it and let us know the results. Here's a >> blog post about it - link >> <https://medium.com/@myroslavarm/test-code-completion-has-been-added-to-phar…>, >> and here's a tweet I'd be grateful if you shared - link >> <https://twitter.com/myroslavarm/status/1146013653067587584> so perhaps >> people who don't read the mailing list would also see it. In the blog post >> you can find more info how to enable the completion in the settings and >> details about the whole thing in general. If something doesn't work, or if >> something works differently than it used to in the old completion (both if >> you don't like it or perhaps if you prefer it) let me know either replying >> here, on twitter, or submitting an issue request directly for the github >> repository here - link >> <https://github.com/myroslavarm/Experimental-Completion/issues>. >> >> Thanks very much, >> Myroslava >> >> >> >> -------------------------------------------- >> 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 >> >> > > -- > Ð Ð¿Ð¾Ð²Ð°Ð³Ð¾Ñ, > ÐÐ¸ÑÐ¾ÑÐ»Ð°Ð²Ð° Ð Ð¾Ð¼Ð°Ð½ÑÐº. > -- Ð Ð¿Ð¾Ð²Ð°Ð³Ð¾Ñ, ÐÐ¸ÑÐ¾ÑÐ»Ð°Ð²Ð° Ð Ð¾Ð¼Ð°Ð½ÑÐº.

1 0

Re: [Pharo-dev] Test Completion has been added to Pharo 8 - please test!
by StÃ©phane Ducasse July 3, 2019

July 3, 2019

Hi miroslava how can we test it? Stef > On 3 Jul 2019, at 01:11, Myroslava Romaniuk <romaniuk(a)ucu.edu.ua> wrote: > > > From: Myroslava Romaniuk <romaniuk(a)ucu.edu.ua> > Subject: Test Completion has been added to Pharo 8 - please test! > Date: 3 July 2019 at 01:11:51 GMT+9 > To: Pharo Development List <pharo-dev(a)lists.pharo.org>, Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > > > Hi all, > > we added an intermediate version of the upcoming test completion to Pharo 8, it would be cool if you tested it and let us know the results. Here's a blog post about it - link <https://medium.com/@myroslavarm/test-code-completion-has-been-added-to-phar…>, and here's a tweet I'd be grateful if you shared - link <https://twitter.com/myroslavarm/status/1146013653067587584> so perhaps people who don't read the mailing list would also see it. In the blog post you can find more info how to enable the completion in the settings and details about the whole thing in general. If something doesn't work, or if something works differently than it used to in the old completion (both if you don't like it or perhaps if you prefer it) let me know either replying here, on twitter, or submitting an issue request directly for the github repository here - link <https://github.com/myroslavarm/Experimental-Completion/issues>. > > Thanks very much, > Myroslava > > -------------------------------------------- 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

2 1

Compiler: add the concept of a Production Environment
by Marcus Denker July 3, 2019

July 3, 2019

Hi, We added support for setting a âproduction environmentâ for the compiler: When compiling, there might be the case that the result of the compiler (the compiledMethod) should not be an instance of the class CompiledMethod from the environment in which we compile, but from some other environment. (e.g. imagine you have multiple environments and want to cross cross compile) This PR adds the concept of a productionEnvironment and enables it for CompiledMethod. (other use cases might make sense, too, for example all the literals in the CompiledMethod, this is future work but can be done similarly by handing the context into the Scanner) This is our test for CompiledMethod: testCompileWithProductionEnvironment | environment method return | environment := {#CompiledMethod -> MyCompiledMethodForTesting} asDictionary. method := Smalltalk compiler productionEnvironment: environment; compile: 'tt ^1+2'. self assert: method class equals: MyCompiledMethodForTesting. return := method valueWithReceiver: nil arguments: #(). self assert: return equals: 3. As one can see, the produces compiled method of the Compiler is an instance of our class. PR needs a Review: https://github.com/pharo-project/pharo/pull/3749/files

1 0

[Pharo 8.0] Build #422: 3724-Anonther-small-cleanup-SystemNavigation
by ci-pharo-ci-jenkins2＠inria.fr July 2, 2019

July 2, 2019

There is a new Pharo build available! The status of the build #422 was: SUCCESS. The Pull Request #3725 was integrated: "3724-Anonther-small-cleanup-SystemNavigation" Pull request url: https://github.com/pharo-project/pharo/pull/3725 Issue Url: https://github.com/pharo-project/pharo/issues/3724 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #421: 3741-New-completion-test-DNU-completionToken-for-Parse-Error-node
by ci-pharo-ci-jenkins2＠inria.fr July 2, 2019

July 2, 2019

There is a new Pharo build available! The status of the build #421 was: SUCCESS. The Pull Request #3743 was integrated: "3741-New-completion-test-DNU-completionToken-for-Parse-Error-node" Pull request url: https://github.com/pharo-project/pharo/pull/3743 Issue Url: https://github.com/pharo-project/pharo/issues/3741 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Test Completion has been added to Pharo 8 - please test!
by Myroslava Romaniuk July 2, 2019

July 2, 2019

Hi all, we added an intermediate version of the upcoming test completion to Pharo 8, it would be cool if you tested it and let us know the results. Here's a blog post about it - link <https://medium.com/@myroslavarm/test-code-completion-has-been-added-to-phar…>, and here's a tweet I'd be grateful if you shared - link <https://twitter.com/myroslavarm/status/1146013653067587584> so perhaps people who don't read the mailing list would also see it. In the blog post you can find more info how to enable the completion in the settings and details about the whole thing in general. If something doesn't work, or if something works differently than it used to in the old completion (both if you don't like it or perhaps if you prefer it) let me know either replying here, on twitter, or submitting an issue request directly for the github repository here - link <https://github.com/myroslavarm/Experimental-Completion/issues>. Thanks very much, Myroslava

1 0