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

Re: [Pharo-dev] [ANN] New Pharo 6.1 version

by Alexandre Bergel

When there is a new version of Pharo 6.1, how can I make the launcher know about it? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Apr 5, 2018, at 10:00 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > https://pharo.fogbugz.com/f/cases/20944/Integrate-Epicea-8-2-8-in-Ph6-1 <https://pharo.fogbugz.com/f/cases/20944/Integrate-Epicea-8-2-8-in-Ph6-1> > >

April 5, 2018

Re: [Pharo-dev] [ANN] New Pharo 6.1 version

by philippe.back＠highoctane.be

sounds very interesting! Phil On Thu, Apr 5, 2018, 15:01 Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > https://pharo.fogbugz.com/f/cases/20944/Integrate-Epicea-8-2-8-in-Ph6-1 > > >

April 5, 2018

[ANN] New Pharo 6.1 version

by Esteban Lorenzano

https://pharo.fogbugz.com/f/cases/20944/Integrate-Epicea-8-2-8-in-Ph6-1 <https://pharo.fogbugz.com/f/cases/20944/Integrate-Epicea-8-2-8-in-Ph6-1>

April 5, 2018

Re: [Pharo-dev] [Pharo7] halt inside and outside tests

by Sean P. DeNigris

Denis Kudriashov wrote >> I would even shorten it to haltIfTest and haltIfNotTest. Sounds good. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

April 5, 2018

[Pharo 7.0-dev] Build #756: 21678-Improve-the-Diff-Morph-with-a-title-bar-showing-each-of-the-version-compared

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

There is a new Pharo build available! The status of the build #756 was: SUCCESS. The Pull Request #1183 was integrated: "21678-Improve-the-Diff-Morph-with-a-title-bar-showing-each-of-the-version-compared" Pull request url: https://github.com/pharo-project/pharo/pull/1183 Issue Url: https://pharo.fogbugz.com/f/cases/21678 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

April 5, 2018

call for help: answer on HN :)

by Esteban Lorenzano

Hi, yesterday someone posted an article on HN about the Pharo MOOC and there has been some negative posts there. I would like to call people who can have the time to answer there and help to explain better and also contribute to contest that FUD someones (we know who they areâ¦ sames as always) are spreading. here the link : https://news.ycombinator.com/item?id=16754872 <https://news.ycombinator.com/item?id=16754872> (this is not loosing time, people searching for Pharo will likely see this kind of messagesâ¦ at least we need to offer our point of view) cheers! Esteban

April 5, 2018

Re: [Pharo-dev] Idea and proof of concept: Accept for Test

by Stephane Ducasse

you should use that as an example in the reflectivity paper. On Wed, Apr 4, 2018 at 6:02 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Hi, > > Some code is very âactiveâ, executed all the time, e.g. collections, graphicsâ¦ or imagine if you work on the compiler or debugger. > > It would really be nice if we could test a change before accepting it. Something like âAccept for Testâ where magically the original method > does not change, yet, when running tests, the version of the code we accepted for testing is executed. > > So how do we implement that? > > 1) menu in the browser. I did a quick hack, a Suggestions AST menu shows for all nodes (to be replaced with the âcorrectâ way later). > > SugsSuggestion subclass: #SugsAcceptForTest > instanceVariableNames: '' > classVariableNames: '' > package: 'SmartSuggestions-Suggestionâ > > label > ^'Accept for testâ > > So, now we can do everything in the #execute method. > > What do we need? > > 1) How we know that we are in a test? â> CurrentExecutionEnvironment value isTest > 2) can we compile the buffer even if there are syntax errors (kind of what I expect to happen in non-accepted code)? > â> yes, remember, we use the same Parser for syntax highlighting and we extended code-generation for SyntaxError Nodes > in the past (it raises a syntax error at runtime, isnât that kind off odd in a fun way?). > > newMethod := context selectedClass compiler > source: context code; > options: #(+ optionParseErrors); > compile. > > 3) Now how to we âhook intoâ the execution of the original unchanged method? We use a MetaLink. We install it as a before link on > the RBMethodNode, the meta-object is a block. This block gets as arguments the thisContext and the arguments of the original method > and then just does what you want it do do: if we are in test, return the result of the execution of the method we just compiled. > (Closures are fun, we can just reference the outer temp newMethod, no need to store it anywhere else explicitly): > > [ :aContext :args | > CurrentExecutionEnvironment value isTest > ifTrue: [ aContext return: (newMethod valueWithReceiver: aContext receiver arguments: args) ] ]; > > Thus, all the code is this: > > execute > | newMethod metaLink | > âwe compile a new method from the not-accepted text editor. Allow syntax errors" > newMethod := context selectedClass compiler > source: context code; > options: #(+ optionParseErrors); > compile. > "the link executes the method we just created and returns" > metaLink := MetaLink new > metaObject: [ :aContext :args | > CurrentExecutionEnvironment value isTest > ifTrue: [ aContext return: (newMethod valueWithReceiver: aContext receiver arguments: args) ] ]; > selector: #value:value:; > arguments: #(context arguments). > context selectedMethod ast link: metaLink > > Cleanup we do not care as everything will be GCed as soon as we accept the method for real. > > And it works! I did not test it too much, but it seems to do what it is supposed to do. (but more tests and testing are for sure needed) > https://github.com/pharo-project/pharo/pull/1182 > > Next step: move it to a better place in the menu. > > Marcus > >

April 5, 2018

Re: [Pharo-dev] Idea and proof of concept: Accept for Test

by Holger Freyther

> On 5. Apr 2018, at 08:31, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > And it leads immediately (at least for me) that I start to get lots of ideasâ¦ > > so now we accept a single method for test. > > Why notâ¦ (random ideas) nice! Do we have this for collecting testcases and expected output as well? The tricky part might be to put the Class Under Test into the right state (and condense all duplicate test cases). holger

April 5, 2018

Re: [Pharo-dev] Idea and proof of concept: Accept for Test

by Marcus Denker

> On 5 Apr 2018, at 09:09, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > >> On 4 Apr 2018, at 21:50, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> Very cool. Impressive combination of unique Pharo features. >> > > It shows, too, that âdoing an experiment on topâ and then writing a paper is one thing, but that true progress happens if you can actually integrate the results back into the system. > And it leads immediately (at least for me) that I start to get lots of ideasâ¦ so now we accept a single method for test. Why notâ¦ (random ideas) -> For un-accepted code: Why not do something like this automatically at every keystroke? That is, after syntax highlight, we can just compile a method and store it as a method property on the original method (cost almost nothing). Then all those for an âimplicit layer" that e.g we can very easily activate for the dynamic extended of the exection of an expression in the playground. You could even open a playground that default to that. There can be a button in the browser ârun not acceptedâ. -> extend it so that you actually âaccept for layer Xâ, that is, you give a name to groups of these. -> and of course implement it that the whole group an be accepted as an atomic operation Marcus

April 5, 2018

Re: [Pharo-dev] [Pharo7] halt inside and outside tests

by Marcus Denker

> On 5 Apr 2018, at 09:12, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > >> On 4 Apr 2018, at 09:58, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >> >> Would it be possible to instead have a #haltIf object to which you can send additional conditions? >> >> E.g. >> >> self haltIf insideTest >> self haltIf outsideTest >> >> Makes it (imho) a bit more readable, adds just a single method to Object, and allows for more potential extensions... >> >> self haltIf nil. >> self haltIf count: 3. >> > > Interesting. I will make a not. > noteâ¦ I will make a note. Not a not. Marcus

April 5, 2018