- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core] 9a770f: 50568
by GitHub Feb. 8, 2016

Feb. 8, 2016

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 9a770ffe7387272747c7bf65fc8c0b758371423f https://github.com/pharo-project/pharo-core/commit/9a770ffe7387272747c7bf65… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-02-08 (Mon, 08 Feb 2016) Changed paths: M Monticello.package/MethodAddition.class/instance/notifying/notifyObservers.st M Morphic-Base.package/HaloMorph.class/instance/private/addNameBeneath_string_.st R Morphic-Base.package/NameStringInHalo.class/README.md R Morphic-Base.package/NameStringInHalo.class/definition.st R Morphic-Base.package/NameStringInHalo.class/instance/drawing/drawOn_.st M Morphic-Base.package/StringMorph.class/definition.st A Morphic-Base.package/StringMorph.class/instance/accessing/backgroundColor.st A Morphic-Base.package/StringMorph.class/instance/accessing/backgroundColor_.st M Morphic-Base.package/StringMorph.class/instance/drawing/drawOn_.st M Morphic-Base.package/StringMorph.class/instance/initialization/initialize.st M ScriptLoader50.package/ScriptLoader.class/instance/load primitives/loadConfiguration_version_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50567.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50568.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50567.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50568.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Traits.package/TClassDescription.class/instance/compiling/compile_classified_withStamp_notifying_logSource_.st A Traits.package/TClassDescription.class/instance/compiling/noteCompilationOfMethod_meta_.st Log Message: ----------- 50568 17531 add #noteCompilationOfMethod:meta: https://pharo.fogbugz.com/f/cases/17531 13209 StringMorph background https://pharo.fogbugz.com/f/cases/13209 http://files.pharo.org/image/50/50568.zip

1 0

Best way to access icons?
by Aliaksei Syrel Feb. 8, 2016

Feb. 8, 2016

Hi For ages to access an icon we used: > Smalltalk ui icons protocolPrivateIcon Smalltalk ui icons returns an instance of ThemeIcons. After refactoring (case https://pharo.fogbugz.com/f/cases/16651 <https://pharo.fogbugz.com/f/cases/16651>) all methods to access icon (for example protocolPrivateIcon) were removed. ThemeIcons>>#doesNotUnderstand: aMessage converts message sent to iconNamed: aMessage selector which works. BUT we have this all over the image: [image: Inline image 1] So, what is the best practice to access icons to use in application? Cheers, Alex

6 12

[ANN] We are in "code freeze" for Pharo 5
by Esteban Lorenzano Feb. 8, 2016

Feb. 8, 2016

Hi, 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 :( ) cheers, Esteban

7 8

[bloc] a little demo
by stepharo Feb. 6, 2016

Feb. 6, 2016

Hi guys aleksei, glenn, alain shaked deeply bloc and slowly bloc is getting backing shape. We are moving now the discussions to the pharo-dev mailing-list https://drive.google.com/file/d/0B-bMBVDOi3oTTDBxNmdfS0o3S3c/view?pref=2&pl…

2 1

Simple versus Recursive Mutexes
by Ben Coman Feb. 6, 2016

Feb. 6, 2016

While we are in the process of revising the Mutex infrastructure [1] to use dedicated primitives rather than rely on counting via a semaphore, I want to raise the question of simple versus recursive mutexes. This isn't something I know much about, except that some people strongly believe recursive mutexes are evil, including David Butenhof who apparently was the guy who added recursive mutexes to POSIX "on a dare [...] but nobody was supposed to use recursive mutexes." [1]. There are two interesting discussion on stockoverflow [2][3]. But btw I disagree with Tall Jeff [3] says "The difference between a recursive and non-recursive mutex has to do with ownership. " I think he confuses a simple-mutex and binary-semaphore, as do a some commenters. "Prefer Simple Mutex Over Recursive Mutex" [4] demonstrates some performance considerations and advises "a recursive mutex is dangerous because you lose sense of locking scope. It costs more than a simple mutex." "Recursive Locks Will Kill You!" [5] provides some thread safety guidelines. Finally, there is a paper "Ad Hoc Synchronization Considered harmful" [6], which I haven't read yet since I wanted to get this post out before heading to bed, but I hope to tomorrow. [1] http://www.zaval.org/resources/library/butenhof1.html [2] http://stackoverflow.com/questions/2415082/when-to-use-recursive-mutex [3] http://stackoverflow.com/questions/187761/recursive-lock-mutex-vs-non-recur… [4] http://askldjd.com/2009/10/26/prefer-simple-mutex-over-recursive-mutex/ [5] http://www.fieryrobot.com/blog/2008/10/14/recursive-locks-will-kill-you/ [6] https://www.usenix.org/legacy/event/osdi10/tech/full_papers/Xiong.pdf So our existing Mutex implementation happens to be recursive, and I'm not suggesting we change that. However if we should consider *not* baking the *assumption* of recursion into the primitives, so the same primitives could *also* be used for a SimpleMutex class. The logic to provide recursion for Mutex is only [ owner = activeProcess ] which is easily done in-image. So I propose introducing aquire/release primitives based off the existing critical section primitives with the recursion removed. cheers -ben

3 5

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