February 2016 - Pharo-dev - lists.pharo.org

pharo-minimal-vm
by Ben Coman Feb. 6, 2016

Feb. 6, 2016

Is there a minimal-VM that can be used to run the minimal-IMAGE [1] ? It would be nice for [1] to include an a step.... PharoVMBuilder buildUnix32minimal. since the VM is also part of "how small can we go". My reason for asking is that also less generated VM code might shorten the edit-compile-run loop when I try porting the VM to a Xen Rump kernel Also nice would be an example of how to invoke the tests in a minimal image from the commandline. cheers -ben [1] https://github.com/pharo-project/pharo-minimal-scripts

3 2

Re: [Pharo-dev] [Vm-dev] Where to get Monitor implementation based on primitives?
by Ben Coman Feb. 6, 2016

Feb. 6, 2016

On Fri, Jan 8, 2016 at 9:39 PM, Ben Coman <btc(a)openinworld.com> wrote: > > btw, Looking at the following... > CriticalSection>>critical: aBlock > ^self primitiveEnterCriticalSection > ifTrue: [aBlock value] > ifFalse: [aBlock ensure: [self primitiveExitCriticalSection]] > > without intimate VM knowledge but seeing Eliot recently say > "invocations of methods with primitives [...] are not suspension > points, unless their primitives fail" -- I'm paranoid that since > #ensure: primitive 198 always fail, there might be some some small > window for a race where a process might be terminated before > #primitiveExitCriticalSection can be executed. I'll take a refutation > of this to improve the method comment. > > The following instils more confidence... > > CriticalSection2>>critical: aBlock > | reEntered | > reEntered := false. > [ reEntered := self primitiveEnterCriticalSection. > aBlock value ] ensure: > [ reEntered ifFalse: [ self primitiveExitCriticalSection] ] Having spent more time considering this, I found I was off track here. If a process waiting at #primitiveEnterCriticalSection is terminated, then #primitiveExitCriticalSection is erroneously executed. And it will be the same problem with the proposal for Case17373 based on OwnedLock>>acquire Mutex>>critical: aBlock | lockAcquiredNotHere | <lockAt: #lock tracksStateAt: 1> lockAcquiredNotHere := true. ^[ lockAcquiredNotHere := false. lockAcquiredNotHere := lock acquire. aBlock value ] ensure: [lockAcquiredNotHere ifFalse: [lock release]]. So now I believe the original #critical: proposed by Eliot is optimal. * If #primitiveEnterCriticalSection is terminated while waiting, then the #ifFalse: is never executed. * When #primitiveEnterCriticalSection returns, the inlined #ifTrue:ifFalse cant be interrupted. * #ensure is a primitive which can't be interrupted. By the time it has done its usual "fail", which I raised concern over, actually it has already done its job to make sure #primitiveExitCriticalSection is executed.

1 0

Ubuntu with Spur
by Torsten Bergmann Feb. 5, 2016

Feb. 5, 2016

Is Spur already in the PPA for last stable Ubuntu or how do I install latest spur quickly using commandline? Should I use zeroconf from get.pharo.org. Does it run on latest dev version of Ubuntu? Thanks T.

2 1

Easy way to change "move between words" to alt key in OSX?
by Mariano Martinez Peck Feb. 5, 2016

Feb. 5, 2016

Hi guys, It happens to me that I got so used to work in Pharo and "move between words" with ctrl key, that then, whenever I use any other program of OSX, I get crazy because in many programs ctrl+arrow is for going start/end of file. Same for command. It seems to me that using alt + arrow for moving between words is the most common in OSX. So....is there a way to set this via preferences or something? Thanks in advance, -- Mariano http://marianopeck.wordpress.com

1 0

Contributing to Pharo
by David Allouche Feb. 5, 2016

Feb. 5, 2016

Hello, I believe the Contributing to Pharo page http://pharo.org/contribute-propose-fix <http://pharo.org/contribute-propose-fix> is out of date. I found a bug https://pharo.fogbugz.com/f/cases/17396/MonticelloRepositoryBrowser-example… <https://pharo.fogbugz.com/f/cases/17396/MonticelloRepositoryBrowser-example…> and a made a fix in in a clean image (50525), created by the newly fixed PharoLauncher. Then I followed the instruction on the page. > Create a slice (group of packages): > Open the Monticello Browser. > Open the Slice Maker by clicking the "Slice" button. > In Slice Maker enter the Fogbugz issue number and "grab" the issue summary. > Select all dirty packages affected by your bug fix. I have no idea how the "list of dirty packages" is generated, but it shows a bunch of packages I have not touched it does not show the package that contains my fix (Spec-Tools) I looked in the world menu, and I found this menu item called "Komitter". That sounded like a good candidate. Now, I guess I should select Pharo50Inbox as the Remote, write a commit message, click Ok and hope for the best. Is that right? I guess contributors are expected to use a recent image. So I think it would be good that someone updates the documentation. Or fix the slice maker. Or both.

18 103

[pharo-project/pharo-core]
by GitHub Feb. 5, 2016

Feb. 5, 2016

Branch: refs/tags/50567 Home: https://github.com/pharo-project/pharo-core

1 0

[pharo-project/pharo-core] 219d90: 50567
by GitHub Feb. 5, 2016

Feb. 5, 2016

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 219d902c7d979074a155881cc28de2d71d1e39a3 https://github.com/pharo-project/pharo-core/commit/219d902c7d979074a155881c… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-02-05 (Fri, 05 Feb 2016) Changed paths: M Collections-Strings.package/String.class/class/initialization/initialize.st A Collections-Tests.package/StringTest.class/instance/test-comparing/testComparingCaseInsensitiveLatin1.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50566.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50567.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50566.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50567.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Slot-Tests.package/SlotErrorsTest.class/instance/tests/testDangerousClassesConditions.st R System-Support.package/SystemDictionary.class/instance/memory space/growMemoryByAtLeast_.st Log Message: ----------- 50567 17526 growMemoryByAtLeast: duplicated https://pharo.fogbugz.com/f/cases/17526 17530 fix testDangerousClassesConditions https://pharo.fogbugz.com/f/cases/17530 17242 String>>compare:caseSensitive seems to be failing for extended charset comparisons https://pharo.fogbugz.com/f/cases/17242 http://files.pharo.org/image/50/50567.zip

1 0

Epicea tests failure under Windows (WAS: RE: [ANN] We are in "code freeze" for Pharo 5)
by Blondeau Vincent Feb. 5, 2016

Feb. 5, 2016

I just tried to integrate and the tests are failing when reopening the image. Just added the opening of the session file at the right place and the closing of the file at the end of the critical section. Now, it works fine for me (under W7 of course ;): Name: Ombu-VincentBlondeau.191 Author: VincentBlondeau Time: 4 February 2016, 4:22:48.687273 pm UUID: ebaf974e-9285-e147-bcaa-0049ff093ffe Ancestors: Ombu-MartinDias.190 Vincent > -----Message d'origine----- > De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de > Marcus Denker > EnvoyÃ© : jeudi 4 fÃ©vrier 2016 15:19 > Ã : Pharo Development List > Objet : Re: [Pharo-dev] [ANN] We are in "code freeze" for Pharo 5 > > > > On 04 Feb 2016, at 15:16, Damien Cassou <damien.cassou(a)inria.fr> wrote: > > > > Esteban Lorenzano <estebanlm(a)gmail.com> writes: > > > >> We are on âjust bugfixesâ since some time nowâ¦ I delayed the > announcement because Epicea still needs to enter and we didnât manage to > include it yet. > >> But wellâ¦ with the exception of Epicea, no new features will be included > un Pharo 5â¦ just bugfixes (and we have a lot of bugfixes incomingâ¦ this > release will be hard :( ) > > > > what is Epicea's integration status? > > > We have some strange problem on Windowsâ¦ the test on the build server > fails after integrating it. > > Martin already fixed one problem, but my try yesterday failed again. > > Marcus > Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

4 7

[Pharo-project] [ANN] Pomodoro for Pharo 2.0
by Torsten Bergmann Feb. 5, 2016

Feb. 5, 2016

Hi, I followed the recent discussion and initial code about "Pomodoro" and since (until now) I used a timer written in Java I thought it would be a good idea to replace it with a Smalltalk one ;) I grabbed the HOPomodoro code from Phil and since it was marked as "experiment" I thought it would be good to write a new clean implementation with tests for Pharo 2.0. Thanks Phil - hope you are not angry that I hijacked the idea ... Attached is a screenshot of the tool. Install ======= Go to the Config browser in Pharo 2.0 ("Tools" -> "Config Browser") and load "Pomodoro" from the "Verified" tab. A new timer should appear and you can just click on "Start" to run the timer. When it finished it turns red, beeps and informs the user. How to use ========== You can open a new pomodoro (defaults 25 minutes) from the world menu ("Tools" -> "Pomodoro"). Customize ========= You can customize the pomodoro using Smalltalk. Here are a few examples: "open a new 25 minute one" Pomodoro new open "Opens a new timer with one minute total time" Pomodoro timerFor: 1 minute "Provide an action when pomodoro is finished" Pomodoro timerFor: 5 seconds whenFinishedDo: [ self inform: 'Pomodoro finished'] Code ==== The project comes with 15 tests. Code lives on project "Pomodoro" on SmalltalkHub. So far I added Phil and Sean as contributors since they discussed this topic already and may provide new ideas. If one wants to contribute feel free to do so. Thanks T.

5 6

Pharo mooc registration is available
by stepharo Feb. 4, 2016

Feb. 4, 2016

https://www.france-universite-numerique-mooc.fr/courses/inria/41010/session…

1 0