- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Pedantic on Random>>nextValue method name

by Henrik Nergaard

The method #nextValue actually calculates the next value the seed should be, the current value can be accessed by sending #seed. I do agree that #nextValue might not be the clearest method name for its use; perhaps #nextSeed would be a better name? Best regards, Henrik -- View this message in context: http://forum.world.st/Pedantic-on-Random-nextValue-method-name-tp4850582p48… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 16, 2015

Re: [Pharo-dev] Configuration Madness

by Max Leske

> On 16 Sep 2015, at 16:39, roberto.minelli(a)usi.ch wrote: > > Dear all, > > I have a question about the ConfigurationOf my project, and I really hope you can help. > > In my project I have a package called âDevFlow-Extensionsâ that is a âplaceholderâ for code that is dependent on the Pharo version. > > On the ConfigurationOf, according to the Pharo version I do something like > > spec for: #'pharo3.x' > do: [ > > spec blessing: #baseline. > spec repository: 'http://smalltalkhub.com/mc/RobertoMinelli/DevFlow/main'. > > spec package: 'DevFlow-Extensions' with: 'DevFlow-Extensions30'. > ]. > > spec for: #'pharo4.x' > do: [ > > spec blessing: #baseline. > spec repository: 'http://smalltalkhub.com/mc/RobertoMinelli/DevFlow/main'. > > spec package: 'DevFlow-Extensions' with: 'DevFlow-Extensions40'. > ]. > > In this way, in Pharo 3.0 Iâd load DevFlow-Extensions30 and in Pharo 4.0 Iâd load DevFlow-Extensions40. Super cool. > I am using a single package (âDevFlow-Extensionsâ) to specify of groups, for example: > > spec group: 'User' with: #( > 'DevFlow-Meta' > ... > 'DevFlow-Announcement' > 'DevFlow-Extensions'). > > Now the problem is that for Pharo 5 I have to load both 'DevFlow-Extensions40â and 'DevFlow-Extensions50â. > I read the chapter on Metacello, but didnât find a solution. I tried some combinations of #includes: and #requires: but with no luck. > > Any help is appreciated, thank you very much! > > Roberto Shouldnât this work? spec package: 'DevFlow-Extensions' with: #('DevFlow-Extensions40â âDevFlow-Extensions50).

Sept. 16, 2015

Configuration Madness

by roberto.minelli＠usi.ch

Dear all, I have a question about the ConfigurationOf my project, and I really hope you can help. In my project I have a package called âDevFlow-Extensionsâ that is a âplaceholderâ for code that is dependent on the Pharo version. On the ConfigurationOf, according to the Pharo version I do something like spec for: #'pharo3.x' do: [ spec blessing: #baseline. spec repository: 'http://smalltalkhub.com/mc/RobertoMinelli/DevFlow/main'. spec package: 'DevFlow-Extensions' with: 'DevFlow-Extensions30'. ]. spec for: #'pharo4.x' do: [ spec blessing: #baseline. spec repository: 'http://smalltalkhub.com/mc/RobertoMinelli/DevFlow/main'. spec package: 'DevFlow-Extensions' with: 'DevFlow-Extensions40'. ]. In this way, in Pharo 3.0 Iâd load DevFlow-Extensions30 and in Pharo 4.0 Iâd load DevFlow-Extensions40. Super cool. I am using a single package (âDevFlow-Extensionsâ) to specify of groups, for example: spec group: 'User' with: #( 'DevFlow-Meta' ... 'DevFlow-Announcement' 'DevFlow-Extensions'). Now the problem is that for Pharo 5 I have to load both 'DevFlow-Extensions40â and 'DevFlow-Extensions50â. I read the chapter on Metacello, but didnât find a solution. I tried some combinations of #includes: and #requires: but with no luck. Any help is appreciated, thank you very much! Roberto

Sept. 16, 2015

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