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

[Pharo 7.0-dev] Build #968: 21990-isProbablyPrime-and-friends-should-not-refer-to-Transcript

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

There is a new Pharo build available! The status of the build #968 was: FAILURE. The Pull Request #1435 was integrated: "21990-isProbablyPrime-and-friends-should-not-refer-to-Transcript" Pull request url: https://github.com/pharo-project/pharo/pull/1435 Issue Url: https://pharo.fogbugz.com/f/cases/21990 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 28, 2018

[Pharo 7.0-dev] Build #967: 22001 Cleanup System-Object Events package

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

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

May 28, 2018

Re: [Pharo-dev] [Compiler] #bindings: improvement: Global shadowing

by Marcus Denker

> > Shortcomings: > -> extensions are not treated, only the main package > -> Not used much, for sure needs testing to see if this really works. â> there might be other places in addition global #compilerClass: where we need to point to the overlay version For the complete âcompile a methodâ it works, but I think there are other cases where it is not enough. > -> Can we get rid of the #CompilerOverlay global? > I think it can be a class variable of OpalCompiler, this way we can turn the whole thing into a Setting (if it turns out to be usable) Marcus

May 28, 2018

[Pharo 7.0-dev] Build #966: 22002 Cleanup System-Platforms

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

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

May 28, 2018

Re: [Pharo-dev] [Compiler] #bindings: improvement: Global shadowing

by Marcus Denker

> On 18 May 2018, at 10:39, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > the #binding: API until now did not allow to shadow globals. But there is actually no reason to forbid that > (and it can actually be interesting, e.g. to compile code where one class ref is switched to another). > > The Pull Request does: > > - add comment to OCExtraBindingScope > - categorize tests > - change #lookupVar: to allow shadowing of Globals. > - change test to reflect the new behaviour > > This means you can do: > > result := Smalltalk compiler > bindings: {(#Object -> Point)} asDictionary; > evaluate: 'Object newâ. So what can we do with this? If you develop a compiler, it is always very annoying that any change that you do actually breaks the compiler if you do it wrong. Larger changes over multiple methods get quite hard to do. One thing that we will soon have is the âaccept for testâ feature that I posted recently. Another idea is to use the #bindings: feature of the compiler. I did small experiment, I added this method to the OpalCompiler class on the class side: prepareForDevelopment "this method sets up an overlay in the global var CompilerOverlay" <script> | overlayEnvironment | overlayEnvironment := Dictionary new. Smalltalk globals at: #CompilerOverlay put: overlayEnvironment. "now we put a copy of all the classes of the compiler package into the environment" self package definedClasses do: [ :class | overlayEnvironment at: class name put: class copy]. âthen we recompile the classes in the environment with itself as an overlay" overlayEnvironment valuesDo: [ :class | class methods do: [ :method | |newMethod| newMethod := class compiler bindings: overlayEnvironment; compile: method sourceCode. class addSelectorSilently: method selector withMethod: newMethod. ]]. After that is done, we have CompilerOverlay global that contains a copy of all the classes of the compiler recompiled so that they use all the classes inside this copy. So we now can set this copy as the main compiler for the image: SmalltalkImage compilerClass: (CompilerOverlay at: #OpalCompiler) And after that, you can put a #halt deep in the compiler (or do some change that needs multiple steps), yet compilation will not be affected. Most tests (not all) are writing in a way that they use classes from the package directly (they do not go via the global #compilerClass setting). So this means that one can now change the compiler as much as one wants, test it by running tests and then be quite sure that it will not break anything. Shortcomings: -> extensions are not treated, only the main package -> Not used much, for sure needs testing to see if this really works. -> Can we get rid of the #CompilerOverlay global? Marcus

May 28, 2018

[Pharo 7.0-dev] Build #965: 22003-OSWindowDriver-shutdown-throws-DNU

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

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

May 28, 2018

[Pharo 7.0-dev] Build #964: 21996-SDL2-clipboard-primitives-are-wrong

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

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

May 28, 2018

Esteban's ChangeLog week of 21 May 2018

by estebanlm＠gmail.com

Hello! This is my weekly ChangeLog, from 21 May 2018 to 27 May 2018. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=21/5/2018&to=27/5/2018 ChangeLog ========= 23 May 2018: ------------ * I fixed an annoying issue when using +OSWindowWorldMorph+, [case: 21957](https://pharo.fogbugz.com/f/cases/21957). The problem was this: when using an altearnative world (like the one provided by OSWindow), +DisplayScreen class>>actualScreenSize+ is answering a random value. Even worst when you use it with Ronie's headless VM. Right now, this is invisible for 99.99% of users, but in the future it will be a good thing to have it working. cheers! Esteban

May 28, 2018

Re: [Pharo-dev] IMPORTANT: ML Etiquette

by Ben Coman

On 28 May 2018 at 11:48, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Dear all, > > There were several posts in the "Beacon for Pharo 7" thread which > top-posted > on top of massive unsnipped quotes that were several-previous-posts deep. > IMHO this made the conversation impossible to follow. This issue has > cropped > up from time to time in other threads. > > Please adhere to basic ML etiquette [1] to maximize our effectiveness. Two > essential guidelines are: > 1) snip quoted material to just what's necessary to understand what's > being replied to > 2) Post reply /after/ the quote from the OP, not before. > > 1. > https://www.freebsd.org/doc/en_US.ISO8859-1/articles/ > mailing-list-faq/etiquette.html#idp55179976 e.g... Because it messes up the order in which people normally read text. >Why is top-posting such a bad thing? >>The lost context. >>>What makes top-posted replies harder to read than bottom-posted? >>>>Yes. >>>>>Should I trim down the quoted part of an email to which I'm replying? http://www.idallen.com/topposting.html Part of the problem is the way gmail and other clients *hide* the original text behind three ellipses dots, so its not immediately obvious how much a thread has grown. Its good to make a habit of clicking those dots immediately after clicking <Reply>. cheers -ben

May 28, 2018

IMPORTANT: ML Etiquette

by Sean P. DeNigris

Dear all, There were several posts in the "Beacon for Pharo 7" thread which top-posted on top of massive unsnipped quotes that were several-previous-posts deep. IMHO this made the conversation impossible to follow. This issue has cropped up from time to time in other threads. Please adhere to basic ML etiquette [1] to maximize our effectiveness. Two essential guidelines are: 1) snip quoted material to just what's necessary to understand what's being replied to 2) Post reply /after/ the quote from the OP, not before. 1. https://www.freebsd.org/doc/en_US.ISO8859-1/articles/mailing-list-faq/etiqu… ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

May 28, 2018