September 2015 - Pharo-dev - lists.pharo.org

Pedantic on Random>>nextValue method name

by Ben Coman

In Random>>nextValue I notice the comment: "This method does NOT update the seed; repeated sends answer the same value." Thus the following produces all the same values... oc := OrderedCollection new. r := Random new. 5 timesRepeat: [ oc add: r nextValue ] . oc inspect. Am I being too pedantic thinking this ancient method should be named #currentValue. Are there historical constraints to be wary of? Its only significant in-Image sender is Random>>next which would then be... ^ (seed := self currentValue) / m cheers -ben

Sept. 16, 2015

Re: [Pharo-dev] SyntaxError: parentheses; cascades and yourself (Opal vs. old compilers parser)

by Christophe Demarey

The PackageAnalyzer is now maintained by me (especially because it is so usefull for the bootstrap). I just fixed that. Indeed, the code was wrong. Christophe Le 16 sept. 2015 Ã 15:05, Nicolai Hess a Ã©crit : > OK, I think Sven is right and a cascade needs at least one message send > > "self ; yourself" > > doesn't work too (both parser don't accept this). > > There are currently two methods in Pharo 5.0 with this > syntax: > > DAPackageAnalyzerWindow class>>#onPackagesNamed: > DAPackageCycleDetectionTreeModel class>>#onPackagesNamed: > > @Yuri, can you change that. > > > And I think we should fix RBParser. > > 2015-09-16 11:30 GMT+02:00 Thierry Goubier <thierry.goubier(a)gmail.com>: > Nicolai, > > can you try with the RBParser directly? I believe Opal uses the RBParser. > > RBParser parseMethod: 'createRedMorph > ^ (self new color:Color red); yourself' > > Oh, RBParser sees it as: > > self new > color: Color red; > yourself > > :) > > Thierry > > > 2015-09-16 10:56 GMT+02:00 Nicolai Hess <nicolaihess(a)web.de>: > The following method compiles with Opal: > > createRedMorph > ^ (self new color:Color red); yourself > > but gives a syntax error with the old compilers parser > > createRedMorph > ^ (self new color:Color red)End of block expected -> ; yourself > > > removing the parenthesis of course works for both. > Who is right ? > > > (for those who understand the ParseTreeSearcher syntax, how would > a search expression look, for finding code like: > > "(some expression);yourself" > > > nicolai > > >

Sept. 16, 2015

Re: [Pharo-dev] SyntaxError: parentheses; cascades and yourself (Opal vs. old compilers parser)

by Thierry Goubier

Argh, sent too early: self new color: Color red; yourself est bien une cascade, non? Thierry 2015-09-16 15:12 GMT+02:00 Thierry Goubier <thierry.goubier(a)gmail.com>: > > > 2015-09-16 15:05 GMT+02:00 Nicolai Hess <nicolaihess(a)web.de>: > >> OK, I think Sven is right and a cascade needs at least one message send >> >> "self ; yourself" >> >> doesn't work too (both parser don't accept this). >> > > But > > > >> >> There are currently two methods in Pharo 5.0 with this >> syntax: >> >> DAPackageAnalyzerWindow class>>#onPackagesNamed: >> DAPackageCycleDetectionTreeModel class>>#onPackagesNamed: >> >> @Yuri, can you change that. >> >> >> And I think we should fix RBParser. >> >> >> 2015-09-16 11:30 GMT+02:00 Thierry Goubier <thierry.goubier(a)gmail.com>: >> >>> Nicolai, >>> >>> can you try with the RBParser directly? I believe Opal uses the RBParser. >>> >>> RBParser parseMethod: 'createRedMorph >>> ^ (self new color:Color red); yourself' >>> >>> Oh, RBParser sees it as: >>> >>> self new >>> color: Color red; >>> yourself >>> >>> :) >>> >>> Thierry >>> >>> >>> 2015-09-16 10:56 GMT+02:00 Nicolai Hess <nicolaihess(a)web.de>: >>> >>>> The following method compiles with Opal: >>>> >>>> createRedMorph >>>> ^ (self new color:Color red); yourself >>>> >>>> but gives a syntax error with the old compilers parser >>>> >>>> createRedMorph >>>> ^ (self new color:Color red)End of block expected -> ; yourself >>>> >>>> >>>> removing the parenthesis of course works for both. >>>> Who is right ? >>>> >>>> >>>> (for those who understand the ParseTreeSearcher syntax, how would >>>> a search expression look, for finding code like: >>>> >>>> "(some expression);yourself" >>>> >>>> >>>> nicolai >>>> >>>> >>> >> >

Sept. 16, 2015

Re: [Pharo-dev] SyntaxError: parentheses; cascades and yourself (Opal vs. old compilers parser)

by Thierry Goubier

2015-09-16 15:05 GMT+02:00 Nicolai Hess <nicolaihess(a)web.de>: > OK, I think Sven is right and a cascade needs at least one message send > > "self ; yourself" > > doesn't work too (both parser don't accept this). > But > > There are currently two methods in Pharo 5.0 with this > syntax: > > DAPackageAnalyzerWindow class>>#onPackagesNamed: > DAPackageCycleDetectionTreeModel class>>#onPackagesNamed: > > @Yuri, can you change that. > > > And I think we should fix RBParser. > > > 2015-09-16 11:30 GMT+02:00 Thierry Goubier <thierry.goubier(a)gmail.com>: > >> Nicolai, >> >> can you try with the RBParser directly? I believe Opal uses the RBParser. >> >> RBParser parseMethod: 'createRedMorph >> ^ (self new color:Color red); yourself' >> >> Oh, RBParser sees it as: >> >> self new >> color: Color red; >> yourself >> >> :) >> >> Thierry >> >> >> 2015-09-16 10:56 GMT+02:00 Nicolai Hess <nicolaihess(a)web.de>: >> >>> The following method compiles with Opal: >>> >>> createRedMorph >>> ^ (self new color:Color red); yourself >>> >>> but gives a syntax error with the old compilers parser >>> >>> createRedMorph >>> ^ (self new color:Color red)End of block expected -> ; yourself >>> >>> >>> removing the parenthesis of course works for both. >>> Who is right ? >>> >>> >>> (for those who understand the ParseTreeSearcher syntax, how would >>> a search expression look, for finding code like: >>> >>> "(some expression);yourself" >>> >>> >>> nicolai >>> >>> >> >

Sept. 16, 2015

Re: [Pharo-dev] SyntaxError: parentheses; cascades and yourself (Opal vs. old compilers parser)

by Nicolai Hess

Arrg, sorry Yuri, this (too) isn't from QualityAssistance, but DependencyAnalyzer 2015-09-16 15:05 GMT+02:00 Nicolai Hess <nicolaihess(a)web.de>: > OK, I think Sven is right and a cascade needs at least one message send > > "self ; yourself" > > doesn't work too (both parser don't accept this). > > There are currently two methods in Pharo 5.0 with this > syntax: > > DAPackageAnalyzerWindow class>>#onPackagesNamed: > DAPackageCycleDetectionTreeModel class>>#onPackagesNamed: > > @Yuri, can you change that. > > > And I think we should fix RBParser. > > > 2015-09-16 11:30 GMT+02:00 Thierry Goubier <thierry.goubier(a)gmail.com>: > >> Nicolai, >> >> can you try with the RBParser directly? I believe Opal uses the RBParser. >> >> RBParser parseMethod: 'createRedMorph >> ^ (self new color:Color red); yourself' >> >> Oh, RBParser sees it as: >> >> self new >> color: Color red; >> yourself >> >> :) >> >> Thierry >> >> >> 2015-09-16 10:56 GMT+02:00 Nicolai Hess <nicolaihess(a)web.de>: >> >>> The following method compiles with Opal: >>> >>> createRedMorph >>> ^ (self new color:Color red); yourself >>> >>> but gives a syntax error with the old compilers parser >>> >>> createRedMorph >>> ^ (self new color:Color red)End of block expected -> ; yourself >>> >>> >>> removing the parenthesis of course works for both. >>> Who is right ? >>> >>> >>> (for those who understand the ParseTreeSearcher syntax, how would >>> a search expression look, for finding code like: >>> >>> "(some expression);yourself" >>> >>> >>> nicolai >>> >>> >> >

Sept. 16, 2015

Re: [Pharo-dev] SyntaxError: parentheses; cascades and yourself (Opal vs. old compilers parser)

by Nicolai Hess

OK, I think Sven is right and a cascade needs at least one message send "self ; yourself" doesn't work too (both parser don't accept this). There are currently two methods in Pharo 5.0 with this syntax: DAPackageAnalyzerWindow class>>#onPackagesNamed: DAPackageCycleDetectionTreeModel class>>#onPackagesNamed: @Yuri, can you change that. And I think we should fix RBParser. 2015-09-16 11:30 GMT+02:00 Thierry Goubier <thierry.goubier(a)gmail.com>: > Nicolai, > > can you try with the RBParser directly? I believe Opal uses the RBParser. > > RBParser parseMethod: 'createRedMorph > ^ (self new color:Color red); yourself' > > Oh, RBParser sees it as: > > self new > color: Color red; > yourself > > :) > > Thierry > > > 2015-09-16 10:56 GMT+02:00 Nicolai Hess <nicolaihess(a)web.de>: > >> The following method compiles with Opal: >> >> createRedMorph >> ^ (self new color:Color red); yourself >> >> but gives a syntax error with the old compilers parser >> >> createRedMorph >> ^ (self new color:Color red)End of block expected -> ; yourself >> >> >> removing the parenthesis of course works for both. >> Who is right ? >> >> >> (for those who understand the ParseTreeSearcher syntax, how would >> a search expression look, for finding code like: >> >> "(some expression);yourself" >> >> >> nicolai >> >> >

Sept. 16, 2015

Re: [Pharo-dev] Reflectivity: Links that de-install themselves (oneShot)

by Tudor Girba

This is really beautiful :). Doru On Wed, Sep 16, 2015 at 10:52 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Hi, > > This is just a one-liner to add to the framework, but that makes it even > more fun: One-Shot links. > > A link now can have the #optionOneShot, which means that it will > de-install itself when activated for > the first time: > > link := MetaLink new > metaObject: self; > options: #(optionOneShot); > selector: #tagExec. > > The full test looks like this: > > testLinkOneShot > | sendNode link | > sendNode := (ReflectivityExamples>>#exampleMethod) sendNodes first. > link := MetaLink new > metaObject: self; > options: #(optionOneShot); > selector: #tagExec. > sendNode link: link. > self assert: sendNode hasMetalink. > self assert: tag isNil. > self assert: (ReflectivityExamples new exampleMethod = 5). > self assert: (tag = #yes). > self deny: sendNode hasMetalink. > tag := nil. > self assert: (ReflectivityExamples new exampleMethod = 5). > self assert: tag isNil. > > > https://pharo.fogbugz.com/f/cases/16581/one-shot-links > > Marcus > -- www.tudorgirba.com "Every thing has its own flow"

Sept. 16, 2015

[Ann] Phratch 4.1 is here !

by jannik laval

Based on Phratch 4.0 we made some bug fixes and added new small features. Phratch is now on top of Pharo 4.0. The new features are: - languages are more stable. Thanks to the community for the feedback and the enhancement of the language files. - Add a "follow" option that allows one to see which block is currently executed. Phratch 4.1 is already available on phratch.com. If you detect an issue, you can submit a description on https://github.com/janniklaval/phratch/issues And you can always download the latest build on the continuous integration server: https://ci.inria.fr/pharo-contribution/view/Phratch/ See you on phratch.com -- ~~Jannik Laval~~ Enseignant-chercheur IUT LumiÃ¨re <http://iut.univ-lyon2.fr/>, UniversitÃ© Lyon LumiÃ¨re <http://www.univ-lyon2.fr/> laboratoire DISP <http://disp-lab.fr/> http://www.jannik-laval.eu http://www.phratch.com http://www.approchealpes.info

Sept. 16, 2015

[pharo-project/pharo-core]

by GitHub

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

Sept. 16, 2015

[pharo-project/pharo-core] 313e4a: 50327

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 313e4a2da2d22b03bcd18e80acf64a1692cc0250 https://github.com/pharo-project/pharo-core/commit/313e4a2da2d22b03bcd18e80… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-09-16 (Wed, 16 Sep 2015) Changed paths: M Announcements-Tests-Core.package/AnnouncerTest.class/instance/testing/testSubscribeSend.st M Announcements-Tests-Core.package/AnnouncerTest.class/instance/testing/testUnsubscribeSend.st M Announcements-Tests-Core.package/WeakAnnouncerTest.class/instance/testing/testWeakObject.st M Nautilus.package/AbstractNautilusUI.class/instance/build ui text/buildNewCommentText.st M Nautilus.package/AbstractNautilusUI.class/instance/build ui/addAll_.st M Nautilus.package/NautilusAnnotationDisplayer.class/instance/submorphs-accessing/noteNewOwner_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50326.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50327.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50326.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50327.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Core.package/TabManagerModel.class/instance/api/addTab_.st M Spec-Core.package/TabManagerModel.class/instance/private/basicRemoveTab_.st M Spec-Core.package/TabModel.class/README.md M Spec-Core.package/TabModel.class/instance/api/model_.st A Spec-Tests.package/TabManagerModelTest.class/README.md A Spec-Tests.package/TabManagerModelTest.class/definition.st A Spec-Tests.package/TabManagerModelTest.class/instance/running/setUp.st A Spec-Tests.package/TabManagerModelTest.class/instance/running/tearDown.st A Spec-Tests.package/TabManagerModelTest.class/instance/tabs creation/redMorphTab.st A Spec-Tests.package/TabManagerModelTest.class/instance/tests/testAddTabOpened.st A Spec-Tests.package/TabManagerModelTest.class/instance/tests/testAddTabSetOwner.st A Spec-Tests.package/TabManagerModelTest.class/instance/tests/testAddTabUnopened.st A Spec-Tests.package/TabManagerModelTest.class/instance/tests/testInitialSelectedTab.st A Spec-Tests.package/TabManagerModelTest.class/instance/tests/testRemoveTab.st A Spec-Tests.package/TabManagerModelTest.class/instance/tests/testRemoveTabFromManager.st A Spec-Tests.package/TabManagerModelTest.class/instance/tests/testRemoveTabFromManager2.st A Spec-Tests.package/TabManagerModelTest.class/instance/tests/testRemoveTabFromMorphic.st A Spec-Tests.package/TabManagerModelTest.class/instance/tests/testRemoveTabUnsetOwner.st A Spec-Tests.package/TabManagerModelTest.class/instance/utility/morphicTabsFor_.st R Spec-Tests.package/TabModelTest.class/instance/tests/testAddTabOpened.st R Spec-Tests.package/TabModelTest.class/instance/tests/testAddTabUnopened.st R Spec-Tests.package/TabModelTest.class/instance/tests/testInitialSelectedTab.st R Spec-Tests.package/TabModelTest.class/instance/tests/testRemoveTab.st R Spec-Tests.package/TabModelTest.class/instance/tests/testRemoveTabFromManager.st R Spec-Tests.package/TabModelTest.class/instance/tests/testRemoveTabFromManager2.st R Spec-Tests.package/TabModelTest.class/instance/tests/testRemoveTabFromMorphic.st A Spec-Tests.package/TabModelTest.class/instance/tests/testSetOwner.st R Spec-Tests.package/TabModelTest.class/instance/utility/morphicTabsFor_.st M Tool-FileList.package/FileList.class/instance/user interface/morphicFileContentsPane.st M Tool-Workspace.package/Workspace.class/instance/view/textView.st Log Message: ----------- 50327 16500 Remove senders of subscribe:send:to: in the image https://pharo.fogbugz.com/f/cases/16500 16564 Remove senders of Announcer>>#subscribe:send:to: in Tool-Workspace https://pharo.fogbugz.com/f/cases/16564 16562 Remove senders of Announcer>>#subscribe:send:to: in Tool-FileList https://pharo.fogbugz.com/f/cases/16562 16553 TabModel/TabModelManager are not setting owner: https://pharo.fogbugz.com/f/cases/16553 http://files.pharo.org/image/50/50327.zip

Sept. 16, 2015