- Pharo-users - lists.pharo.org

What next for Pharo vm?

by henry

I was thinking the vm is able to run more than one bytecode set. Why couldnât our vm support both Pharo and Java bytecodes? Sent from ProtonMail Mobile

April 22, 2018

Sorry - Please Stay!!!

by sean＠clipperadams.com

> Well, I guess I don't belong here anymoreâ¦ Please don't let one personality define our community. I'm sure there are a lot of people, like me, who appreciate your perspective and efforts. Steph has said the same thing to me multiple times about talking vs. action and I've worked on hundreds of issues. It can be frustrating, but I certainly believe it's worth it because while not perfect, Pharo is the closest to my Dynabook dream with enough of a community around it to have good up-to-date libraries around it, etc. GT, Roassal, Grafoscopio, and the new AI stuff are getting really exciting. Let's focus on inventing the future! _____________________________________ Sent from http://forum.world.st

April 22, 2018

Re: [Pharo-users] question re. meaning of 'self' in a method used for testing

by Sean P. DeNigris

Gregg Williams wrote > HiâIâm a beginner in Pharo and am working my way through Pharo by Example > 5.0 (PbE) and Learning OOP and TDD with Pharo (LOTWP). Welcome! That's a great way to start :) Gregg Williams wrote > 1) These two methods are defined on the instance side (the Class button is > *not* selected). If so, what is the receiver when they are used? I think the other two replies covered this and your other questions technically, but I just want to mention that the TestCase class can be a bit confusing. It represents a convenient way to deal with tests in a class browser, at the expense of being the most understandable OOP design. Suffice it to say that whenever a test is run, SUnit, the testing system, will do the magic to create an instance of your TestCase subclass. This is what happens when you click the test bubble in the browser, and this instance is what `self` refers to in tests. HTH ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

April 22, 2018

Re: [Pharo-users] question re. meaning of 'self' in a method used for testing

by Stephane Ducasse

tx guys for your help. cleaning the garden (was a junggle -well still). On Sun, Apr 22, 2018 at 12:18 PM, Hilaire <hilaire(a)drgeo.eu> wrote: > Le 22/04/2018 Ã 05:25, Gregg Williams a Ã©crit : >> >> 2) In testAllIsogramSet, why do you need âselfâ? After all âisogramsâ is a >> data structure, and its message is âdo:â > > > You defined isograms as a method of the class. Therefore only this method > returns the data structure you defined there. > It is not an instance variable declared in your GramCheckerTest class. In > that case you may want to initialize it in your initialize GramCheckerTest > class (or for a test case it is better to do it it in the setUp method as it > will be called before each test method call): > > initialize > super initialize. > isograms := #('pharo' 'pathfinder' 'xavier' 'lumberjacksâ) > > > Then your test method can access it directly (without self): > > > isograms do: [ :word | self assert: word isIsogramSet ] > > > Hilaire > > -- > Dr. Geo > http://drgeo.eu > > >

April 22, 2018

Re: [Pharo-users] question re. meaning of 'self' in a method used for testing

by Hilaire

Le 22/04/2018 Ã 05:25, Gregg Williams a Ã©critÂ : > 2) In testAllIsogramSet, why do you need âselfâ? After all âisogramsâ is a data structure, and its message is âdo:â You defined isograms as a method of the class. Therefore only this method returns the data structure you defined there. It is not an instance variable declared in your GramCheckerTest class. In that case you may want to initialize it in your initialize GramCheckerTest class (or for a test case it is better to do it it in the setUp method as it will be called before each test method call): initialize Â Â Â super initialize. Â Â Â isograms := #('pharo' 'pathfinder' 'xavier' 'lumberjacksâ) Then your test method can access it directly (without self): isograms do: [ :word | self assert: word isIsogramSet ] Hilaire -- Dr. Geo http://drgeo.eu

April 22, 2018

Re: [Pharo-users] #(foo bar baz) min

by Richard O'Keefe

I did say that the code I posted was a *GNU Smalltalk* extension. The version of GNU Smalltalk on my machine doesn't have #detectMin: or #detectMax:. As for test cases: self assert: #(3 1 4 2) min equals: 1. self assert: #(3 1 4 2) max equals: 4. self assert: #('C' 'A' 'D' 'B') min equals: 'A'. self assert: #('C' 'A' 'D' 'B') max equals: 'D'. self assert: #(c a d b) min equals: #a. self assert: #(c a d b) max equals: #d. On 22 April 2018 at 02:33, Herbert VojÄÃk <herby(a)mailbox.sk> wrote: > Note: no need for #collect:thenFold: family, one can implement min as > > min > ^ self detectMin: [ :x | x ] > > if you want to reuse existing one. > > But actually, the issue is, min: and max: are not there (correctly) for > strings. > > Herby > > > Richard O'Keefe wrote: > >> #('a' 'b' 'c') min >> also fails on the grounds that ByteStrings don't understand #min:. >> What's worse is that ByteString and ByteSymbol *do* have #max:, >> but it's something quite different (and arguably broken). >> >> max: aBlock >> | max | >> self ifEmpty: [ ^ nil ]. >> max := aBlock value: self first. >> self >> allButFirstDo: >> [ :each | >> | value | >> value := aBlock value: each. >> max := max max: value ]. >> ^ max >> >> It would be better if the TComparable #min: and #max: >> were available and the current #max: renamed to something else. >> I have this in an extension to GNU Smalltalk: >> >> Collection extend [ >> collect: collectBlock thenFold: foldBlock [ >> |started result| >> started := result := nil. >> self do: [:each | |v| >> v := collectBlock value: each. >> result := started ifNil: [started := self. v] >> ifNotNil: [foldBlock value: result value: v]]. >> ^started ifNil: [SystemExceptions.EmptyCollection signalOn: >> self] >> ifNotNil: [result] >> ] >> >> collectThenMin: collectBlock [ >> ^self collect: collectBlock thenFold: [:acc :y | acc min: y] >> ] >> min [ >> ^self collectThenMin: [:each | each] >> ] >> >> collectThenMax: collectBlock [ >> ^self collect: collectBlock thenFold: [:acc :y | acc max: y] >> ] >> max [ >> ^self collectThenMax: [:each | each] >> ] >> ] >> >> CharacterArray extend [ >> max: other [ >> ^self < other ifTrue: [other] ifFalse: [self] >> ] >> >> min: other [ >> ^self < other ifTrue: [self] ifFalse: [other] >> ] >> ] >> >> >

April 22, 2018

Re: [Pharo-users] min:max:

by Richard O'Keefe

Smalltalk/X has both #min:max: and #clampBetween:and: in its Magnitude.st. Dolphin 7 has neither. The definition of #clampBetween:and: in ST/X is clampBetween: min and: max max < self ifTrue: [^max]. self < min ifTrue: [^min]. ^self I've deleted the comment because it doesn't help with the question "what is the CONTRACT for this method?" In particular, you would naturally expect from the name that (x clampBetween: y and: z) between: y and: z Example: 3 clampBetween: 2 and: 1 ==> 1 1 between: 2 and: 1 ==> false On 22 April 2018 at 04:35, Hilaire <hilaire(a)drgeo.eu> wrote: > The #min:max: message is present in the Squeak/Pharo/Cuis familly but not > in GNU Smalltalk for example. No idea about the other ones. > > > Le 21/04/2018 Ã 00:12, Chris Cunningham a Ã©crit : > >> A name like this would be clearer (although much more annoying): >> >> returnAtLeast: minValue butNoMoreThan: maxValue >> 10 returnAtLeast: 12 butNoMoreThan: 48 >> >> > -- > Dr. Geo > http://drgeo.eu > > > >

April 22, 2018

Re: [Pharo-users] min:max:

by Richard O'Keefe

On 22 April 2018 at 05:59, PBKResearch <peter(a)pbkresearch.co.uk> wrote: > I can find no reference to #min:max: in Dolphin X6.1. > > Peter Kenny > > -----Original Message----- > From: Pharo-users <pharo-users-bounces(a)lists.pharo.org> On Behalf Of > Hilaire > Sent: 21 April 2018 17:36 > To: pharo-users(a)lists.pharo.org > Subject: Re: [Pharo-users] min:max: > > The #min:max: message is present in the Squeak/Pharo/Cuis familly but not > in GNU Smalltalk for example. No idea about the other ones. > > > Le 21/04/2018 Ã 00:12, Chris Cunningham a Ã©crit : > > A name like this would be clearer (although much more annoying): > > > > returnAtLeast: minValue butNoMoreThan: maxValue > > 10 returnAtLeast: 12 butNoMoreThan: 48 > > > > -- > Dr. Geo > http://drgeo.eu > > > > >

April 22, 2018

Re: [Pharo-users] question re. meaning of 'self' in a method used for testing

by Martin McClure

On 04/21/2018 08:25 PM, Gregg Williams wrote: > HiâIâm a beginner in Pharo Hi Gregg, welcome! > and am working my way through Pharo by Example 5.0 (PbE) and Learning OOP and TDD with Pharo (LOTWP). > > Iâm currently going through 7.4 Designing a test, in LOTWP, which covers testing whether a string has no repeated characters, adding the method String >> isIsogramSet. > > GramCheckerTest, a class for testing, has the following methods: > > â > isograms > "list of isograms; used for testing" > > ^ #('pharo' 'pathfinder' 'xavier' 'lumberjacksâ) > > > testAllIsogramSet > "using each word in list named 'isograms'" > > self isograms do: [ :word | self assert: word isIsogramSet ] > â > > Here are my questions: > > 1) These two methods are defined on the instance side (the Class button is *not* selected). If so, what is the receiver when they are used? The receiver is an instance of the test class, which is most likely a subclass of TestCase. > > 2) In testAllIsogramSet, why do you need âselfâ? After all âisogramsâ is a data structure, and its message is âdo:â "isograms" is not, strictly speaking, the name of a data structure. It's the name (formally, "selector") of a message. The method for responding to that message is defined by the source code you list above. That method answers an object of class Array. So in order to get a reference to that array in the actual test case method, it has to send the message #isograms (the # indicates a Symbol -- all message selectors are Symbols), to self. Since the class of the receiver understands messages with that selector, it evaluates the method, and the method answers the reference to the Array. > > 3) As an add-on to 2), what does âselfâ refer to? The class GramCheckerTest? If so, wouldnât that make testAllIsogramSet a class method? But testAllIsogramSet doesnât appear in the class browser when I click the Class button when the Class pane shows GramCheckerTest. When these methods are evaluated, self will be bound to the receiver. The receiver will be an instance of GramCheckerTest. (or possibly a subclass of GramCheckerTest, if any subclasses exist -- they would inherit the method unless overridden.) The test framework creates an instance of the test class to actually run the test. Let's take a look at the code involved. One way to run your test would be to evaluate Â GramCheckerTest run: #testAllIsogramSet. GramCheckerTest most likely inherits the method for #run: from TestCase, and you can see it on the class side of TestCase. It looks like this: run: aSymbol Â Â Â "Execute a testcase name, aSymbol, and return a test result." Â Â Â Â Â Â ^(self selector: aSymbol) run So it sends the message #selector: to self. Note a potentially confusing point here -- #selector: is a selector. Kind of like if my name were "Name." Self here is the class GramCheckerTest. As long as GramCheckerTest doesn't define its own version of #selector:, it inherits that method from TestCase (class side, still), and that method looks like this: selector: aSymbol Â Â Â "Return a test case with aSymbol as selector but does not execute it." Â Â Â ^self new setTestSelector: aSymbol This sends #new to self. Self is, once again, the class GramCheckerTest. A class responds to the message #new by creating a new instance of itself. So now you've got an *instance* of GramCheckerTest, and any messages you send to that will be responded to by methods on the instance side. Well, I would not be surprised if this explanation has confused you, but I hope it's enlightened you a bit as well. Please ask more questions until you understand what's going on here -- if you understand this you will be well positioned to understand the entire language. Regards, -Martin

April 22, 2018

Re: [Pharo-users] Where do we go now ?

by Benoit St-Jean

>What I find sad is that people spent hours talking instead of doing. >This is why Smalltalk is for them. >Personally I prefer Pharo. Well, I guess I don't belong here anymore since "Pharo is NOT Smalltalk" as you keep saying! And since I've been a Smalltalker for only 25+ years, I guess Smalltalk is really for me as you wrote! Every Smalltalker is a moron as you so often imply (especially in private emails incidentally): only Pharoers "do it right"... So I'll go back to that moronic programming language! P.S. I'll let you handle the questions in #pharo on IRC as I'll no longer be on the channel : you'll see, it'll be really instructive for you! People there have those weird practical problems, it's crazy! </byebye> ----------------- BenoÃ®t St-Jean Yahoo! Messenger: bstjean Twitter: @BenLeChialeux Pinterest: benoitstjean Instagram: Chef_Benito IRC: lamneth Blogue: endormitoire.wordpress.com "A standpoint is an intellectual horizon of radius zero".Â (A. Einstein)

April 22, 2018