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

Re: [Pharo-dev] About CommentPane

by stepharo

> Hi, Stef, > Thank you. > I come from shanghai china and study Pharo for several years. Super! Do you know that we are launching a cool mooc on Pharo http://mooc.pharo.org https://www.fun-mooc.fr/courses/inria/41010/session01/about?platform=hootsu… > I want to write some my own language comment , so i wrote a tool for me. Excellent! > the comment text pane and my comment pane need to switch. Did you see that you can have a plugin in nautilus. Click on the menu > so I ask this silly question. There is no silly question :) > Pharo 5.0 I used. > > Best Regards! > > Bing Liang > >

April 20, 2016

Re: [Pharo-dev] Class allSubInstances size takes 23 seconds to run on Pharo 5 on OS X

by Pavel Krivanek

That is not real amount of objects in the object memory: count := 0. object := 0 someObject. [object == 0] whileFalse: [ count := count + 1. object := object nextObject ]. count. "->724653" 2016-04-20 15:18 GMT+02:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > And here other interesting results: > > Class allSubInstances size. > "5636" > Object allSubclasses size > "11267" > > What they are not almost equal? > > 2016-04-20 14:54 GMT+02:00 Pavel Krivanek <pavel.krivanek(a)gmail.com>: > >> Interesting. It takes very high amount of time on Pharo 2.0 too. >> >> -- Pavel >> >> 2016-04-20 14:26 GMT+02:00 Bernhard Pieber <bernhard(a)pieber.com>: >> >>> Dear Pharoers, >>> >>> I found something strange: >>> Time millisecondsToRun: [ Class allSubInstances size ]. â23617" >>> >>> I did this on a new Pharo 5 image >>> curl get.pharo.org/alpha+vmLatest | bash >>> >>> Can somebody confirm this on their machine? What might be the reason? >>> >>> Cheers, >>> Bernhard >>> >> >> >

April 20, 2016

Re: [Pharo-dev] Class allSubInstances size takes 23 seconds to run on Pharo 5 on OS X

by Denis Kudriashov

And here other interesting results: Class allSubInstances size. "5636" Object allSubclasses size "11267" What they are not almost equal? 2016-04-20 14:54 GMT+02:00 Pavel Krivanek <pavel.krivanek(a)gmail.com>: > Interesting. It takes very high amount of time on Pharo 2.0 too. > > -- Pavel > > 2016-04-20 14:26 GMT+02:00 Bernhard Pieber <bernhard(a)pieber.com>: > >> Dear Pharoers, >> >> I found something strange: >> Time millisecondsToRun: [ Class allSubInstances size ]. â23617" >> >> I did this on a new Pharo 5 image >> curl get.pharo.org/alpha+vmLatest | bash >> >> Can somebody confirm this on their machine? What might be the reason? >> >> Cheers, >> Bernhard >> > >

April 20, 2016

Re: [Pharo-dev] Class allSubInstances size takes 23 seconds to run on Pharo 5 on OS X

by Pavel Krivanek

Interesting. It takes very high amount of time on Pharo 2.0 too. -- Pavel 2016-04-20 14:26 GMT+02:00 Bernhard Pieber <bernhard(a)pieber.com>: > Dear Pharoers, > > I found something strange: > Time millisecondsToRun: [ Class allSubInstances size ]. â23617" > > I did this on a new Pharo 5 image > curl get.pharo.org/alpha+vmLatest | bash > > Can somebody confirm this on their machine? What might be the reason? > > Cheers, > Bernhard >

April 20, 2016

Re: [Pharo-dev] Mocketry names again

by Denis Kudriashov

2016-04-20 13:59 GMT+02:00 Dennis Schetinin <chaetal(a)gmail.com>: > Why do we need those sophisticated past-something form after should at > all? Why not simply > > mock should receive someMessage > > ? > Maybe. What others think?

April 20, 2016

Class allSubInstances size takes 23 seconds to run on Pharo 5 on OS X

by Bernhard Pieber

Dear Pharoers, I found something strange: Time millisecondsToRun: [ Class allSubInstances size ]. â23617" I did this on a new Pharo 5 image curl get.pharo.org/alpha+vmLatest | bash Can somebody confirm this on their machine? What might be the reason? Cheers, Bernhard

April 20, 2016

Re: [Pharo-dev] Mocketry names again

by Dennis Schetinin

Why do we need those sophisticated past-something form after should at all? Why not simply mock should receive someMessage ? -- Best regards, Dennis Schetinin 2016-04-20 11:35 GMT+03:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > Hi. > > People start argue that my choice of names are not good. > > For now Mocketry use "should got" to verify that following message was > occurred: > > mock *should got* someMessage > > > This is broken for native english speakers. Do you agree to replace it > with correct #haveReceived? > Can we use more short version #haveGot? > > mock should haveReceived someMessage > > mock should haveGot someMessage > > > Also there is new expression to verify how object was received during > test: > > result should *beReturnedFrom:* [mock someMessage] > > > Should it be #haveReturnedFrom: ? > > > result should haveReturnedFrom: [mock someMessage] > > > I hope we can make consensus and be happy with Mocketry. > > Best regards, > Denis >

April 20, 2016

Re: [Pharo-dev] Ubuntu PPA administration - volunteers?

by Norbert Hartl

Hi, I'll wait for another couple of days but if nobody will step in I'll try. I have the same fear not finding enough time to do it but it is worth a try. My goal with it would be to move from ubuntu ppa to opensuse build service. If integrated there we could build packages for all big linux distributions at once. It woould be nice if you could describe the steps you do more in-depth so the take-over will be easy. Norbert [1] http://openbuildservice.org/ <http://openbuildservice.org/> > Am 19.04.2016 um 09:34 schrieb Markus Fritsche <mfritsche(a)reauktion.de>: > > Hello list, > > I haven't been able to supply as many ppa updates as needed. Right now, > there's a need for a new spur vm and a new graph of dependencies between > the packages that I havent't yet set up. > > Realistically, I think I won't be able to keep up as with pharo > development it deserves :( > > Is there anyone whos willing to help? It involves > - setting up a build environment > - keeping up with pharo vm, pharo launcher releases > - executing build scripts > - react to errors - not that often > - entering your gpg key passphrase > - testing the successful deployment >

April 20, 2016

[pharo-project/pharo-core]

by GitHub

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

April 20, 2016

[pharo-project/pharo-core] 668022: 50702

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 668022f0e62bc208deb8b7ebbd7a31550ea50346 https://github.com/pharo-project/pharo-core/commit/668022f0e62bc208deb8b7eb… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-04-20 (Wed, 20 Apr 2016) Changed paths: A Kernel-Tests.package/CompiledMethodTest.class/instance/tests - testing/testContainsHalt.st M Kernel.package/CompiledMethod.class/instance/testing/containsHalt.st R OpalCompiler-Core.package/OCCopyingTempVariable.class/instance/debugging/writeFromContext_scope_value_.st M OpalCompiler-Tests.package/MethodMapTests.class/instance/testing - temp access/testExampleTempNamedPutCopying2.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50701.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50702.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50701.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50702.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50702 18017 CompiledMethod>>#containsHalt should exclude the selector when checking literals https://pharo.fogbugz.com/f/cases/18017 17702 failting test: OCClosureCompilerTest>>#testDebuggerTempAccess https://pharo.fogbugz.com/f/cases/17702 http://files.pharo.org/image/50/50702.zip

April 20, 2016