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

> On 4 Apr 2018, at 09:58, Peter Uhnák 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

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

> On 5 Apr 2018, at 07:26, Alistair Grant wrote: > > On 4 April 2018 at 22:20, Peter Uhnák wrote: >> If we remove self halt, then I won't be able to use `1halt.`. :-D which is >> actually what I always do, because writing `self halt` is 4 characters

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

> On 5 Apr 2018, at 09:09, Marcus Denker wrote: > > > >> On 4 Apr 2018, at 21:50, Sven Van Caekenberghe wrote: >> >> Very cool. Impressive combination of unique Pharo features. >> > > It shows, too, that “doing an experiment on top” and then writing

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

you should use that as an example in the reflectivity paper. On Wed, Apr 4, 2018 at 6:02 PM, Marcus Denker 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

[Pharo-dev] call for help: answer on HN :)

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

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

> On 3 Apr 2018, at 21:56, Christophe Demarey > wrote: > > Nice addition! > I should say that names are not really intention revealing. > What about haltIfTestExecutionEnvironment and > haltIfDefaultExecutionEnvironment ? > To long and too implementation

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

> On 5 Apr 2018, at 09:12, Marcus Denker wrote: > > > >> On 4 Apr 2018, at 09:58, Peter Uhnák wrote: >> >> Would it be possible to instead have a #haltIf object to which you can send >> additional conditions? >> >> E.g. >> >> self haltIf

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

> On 4 Apr 2018, at 22:41, Nicolas Cellier > wrote: > > Yes this is cool. > I was wondering what if you try and modify the Meta-Link architecture itself, > but my brain did not reach this second meta level... > for now all Links are ignored that are put

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

> On 4 Apr 2018, at 21:50, Sven Van Caekenberghe 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

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

> On 5. Apr 2018, at 08:31, Marcus Denker 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

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

2018-04-05 9:10 GMT+02:00 Marcus Denker : > > > On 3 Apr 2018, at 21:56, Christophe Demarey > wrote: > > Nice addition! > I should say that names are not really intention revealing. > What about haltIfTestExecutionEnvironment and >

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

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

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

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:

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

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

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

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

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

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

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

On 05/04/2018 17:14, Alexandre Bergel wrote: > When there is a new version of Pharo 6.1, how can I make the launcher > know about it? > Hi, In "official distributions", just download a new Pharo 61 version from the launcher and it will be this version by default. It should be build 60540 I

[Pharo-dev] Grafoscopio Questions

I just loaded 1.3.9 into Pharo 6.1 latest (IIRC 540). Two questions: - I got an error on load about updating the docs. Is this known? If not, I'll go back and get more details - How does one contribute to the docs? I found a typo, but if I edit the STON file the PDF will not be in sync and also