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

2018-04-21 Thread 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

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

2018-04-21 Thread Benoit St-Jean via Pharo-users
--- Begin Message --- >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

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

2018-04-21 Thread Gregg Williams
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). 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

Re: [Pharo-users] [ANN] Agile Artificial Intelligence: Programming Neural Networks in Pharo

2018-04-21 Thread Alexandre Bergel
Thanks Sean! This is really a great review! I owe you one! Alexandre > On Apr 21, 2018, at 9:16 PM, Sean P. DeNigris wrote: > > abergel wrote >> Feedback is very welcome. > > Copy edit pass on Chapters 1 & 2: > https://github.com/AgileArtificialIntelligence/AgileArtificialIntelligence.github.

Re: [Pharo-users] [ANN] Agile Artificial Intelligence: Programming Neural Networks in Pharo

2018-04-21 Thread Sean P. DeNigris
abergel wrote > Feedback is very welcome. Copy edit pass on Chapters 1 & 2: https://github.com/AgileArtificialIntelligence/AgileArtificialIntelligence.github.io/pull/2 A few more observations on Chapter 2 requiring deeper investigation: - When you introduce the #assert:equals:, it would be great

Re: [Pharo-users] min:max:

2018-04-21 Thread PBKResearch
I can find no reference to #min:max: in Dolphin X6.1. Peter Kenny -Original Message- From: Pharo-users On Behalf Of Hilaire Sent: 21 April 2018 17:36 To: pharo-users@lists.pharo.org Subject: Re: [Pharo-users] min:max: The #min:max: message is present in the Squeak/Pharo/Cuis familly bu

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

2018-04-21 Thread Sean P. DeNigris
Herby Vojčík wrote > … detectMin: [ :x | x ] Or `detectMin: #yourself` if you prefer - Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Re: [Pharo-users] min:max:

2018-04-21 Thread Hilaire
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: maxVa

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

2018-04-21 Thread Stephane Ducasse
What I find sad is that people spent hours talking instead of doing. This is why Smalltalk is for them. Personally I prefer Pharo. Let me migrate another Seaside chapter so that people can complain after all. Stef On Sat, Apr 21, 2018 at 11:48 AM, Peter Uhnák wrote: > How a project is named is

Re: [Pharo-users] min:max:

2018-04-21 Thread Stephane Ducasse
Yes :) On Sat, Apr 21, 2018 at 4:21 PM, Sven Van Caekenberghe wrote: > > >> On 21 Apr 2018, at 15:35, Stephane Ducasse wrote: >> >> Oh yes >> >> On Sat, Apr 21, 2018 at 12:12 AM, Chris Cunningham >> wrote: >>> A name like this would be clearer (although much more annoying): >>> >>> returnA

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

2018-04-21 Thread Herbert Vojčík
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

Re: [Pharo-users] min:max:

2018-04-21 Thread Sven Van Caekenberghe
> On 21 Apr 2018, at 15:35, Stephane Ducasse wrote: > > Oh yes > > On Sat, Apr 21, 2018 at 12:12 AM, Chris Cunningham > wrote: >> A name like this would be clearer (although much more annoying): >> >> returnAtLeast: minValue butNoMoreThan: maxValue >>10 returnAtLeast: 12 butNoMoreTha

Re: [Pharo-users] min:max:

2018-04-21 Thread Stephane Ducasse
Oh yes On Sat, Apr 21, 2018 at 12:12 AM, Chris Cunningham wrote: > A name like this would be clearer (although much more annoying): > > returnAtLeast: minValue butNoMoreThan: maxValue > 10 returnAtLeast: 12 butNoMoreThan: 48 > > Thanks, > cbc > > On Fri, Apr 20, 2018 at 12:51 PM, Hilaire

Re: [Pharo-users] min:max:

2018-04-21 Thread Stephane Ducasse
On Fri, Apr 20, 2018 at 9:51 PM, Hilaire wrote: > Hi, > > Out of curiosity. > > I always found the #min:max: confusing and lost in its expressiveness. > > One should write: > > 10 min: 48 max: 12 I do not understand the result :) To me this method is illnamed. > > to expect 12. > > but logi

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

2018-04-21 Thread Stephane Ducasse
Hi richard do you have some tests around? Stef On Sat, Apr 21, 2018 at 3:07 PM, 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

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

2018-04-21 Thread Richard O'Keefe
#('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.

Re: [Pharo-users] [squeak-dev] min:max:

2018-04-21 Thread Richard O'Keefe
I looked hard at #min:max: some years ago and decided it was way too confusing to ever use. My own library has Magnitude>> median: lower and: upper "I considered adding a method clampedBetween: lower and: upper ^self < lower ifTrue: [lower] ifFalse: [ upper

Re: [Pharo-users] Proper way to file in code

2018-04-21 Thread Sven Van Caekenberghe
> On 21 Apr 2018, at 13:18, Hilaire wrote: > > Not in my working P7 image. Is it a recent change? Yes, relatively recent, weeks I guess, maybe a month, at least since half March. FileSystem (part of the image for ages), File and new streams (most also long part of the image) are the replacem

Re: [Pharo-users] Proper way to file in code

2018-04-21 Thread Hilaire
Not in my working P7 image. Is it a recent change? Hilaire Le 21/04/2018 à 13:01, Sven Van Caekenberghe a écrit : The whole of FileStream is deprecated in P7, use [Abstract]FileReference>>#fileIn: -- Dr. Geo http://drgeo.eu

Re: [Pharo-users] Proper way to file in code

2018-04-21 Thread Sven Van Caekenberghe
> On 21 Apr 2018, at 10:34, Hilaire wrote: > > Hi, > > To use Smalltalk sketch scripts for additional unit tests, I need to file in > these script files. > > I found FileStream>>fileIn: does the job. Is it the proper way to do it? The whole of FileStream is deprecated in P7, use [Abstract]

Re: [Pharo-users] Time limit to execute a test

2018-04-21 Thread Hilaire
Ah yes, it does it. Thanks Le 21/04/2018 à 11:58, Cyril Ferlicot a écrit : I don't have a computer to check but inside the test you should be able to call a method as #timeLimit:. I'm not sure of the name. -- Dr. Geo http://drgeo.eu

Re: [Pharo-users] Time limit to execute a test

2018-04-21 Thread Cyril Ferlicot
On sam. 21 avr. 2018 at 11:55, Hilaire wrote: > Hi, > > I have a test taking more than the 10 seconds limit to execute completely. > > I tried to adjust this limit but failed to get it taken in > consideration. I tried from 3 places: > > - in the test method itself > > - in TestCase setUp > > - i

[Pharo-users] Time limit to execute a test

2018-04-21 Thread Hilaire
Hi, I have a test taking more than the 10 seconds limit to execute completely. I tried to adjust this limit but failed to get it taken in consideration. I tried from 3 places: - in the test method itself - in TestCase setUp - in a dedicated TestResources The adjustment seems to alway been

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

2018-04-21 Thread Peter Uhnák
How a project is named is a choice of the author. Nobody gets to demand how someone should name their projects. Now how project is actually named is not a issue if it is properly handled on pharo side, which in some places is, in some places isn't. For instance, there's a gazillion UI frameworks

Re: [Pharo-users] Projects using Magritte meta models

2018-04-21 Thread Stephane Ducasse
Cool I will have a look when I go back to Magritte Rafael if you see mistake in the booklet please report them to me. I will do a pass in a couple of weeks I hope On Sat, Apr 21, 2018 at 4:07 AM, Sean P. DeNigris wrote: > Rafael Luque wrote >> I wonder if there are other relevant projects I could

Re: [Pharo-users] Proper way to file in code

2018-04-21 Thread Stephane Ducasse
I think so On Sat, Apr 21, 2018 at 10:34 AM, Hilaire wrote: > Hi, > > To use Smalltalk sketch scripts for additional unit tests, I need to file in > these script files. > > I found FileStream>>fileIn: does the job. Is it the proper way to do it? > > Thanks > > Hilaire > > -- > Dr. Geo > http://dr

[Pharo-users] Proper way to file in code

2018-04-21 Thread Hilaire
Hi, To use Smalltalk sketch scripts for additional unit tests, I need to file in these script files. I found FileStream>>fileIn: does the job. Is it the proper way to do it? Thanks Hilaire -- Dr. Geo http://drgeo.eu

[Pharo-users] Migrating Seaside book to Pillar on github

2018-04-21 Thread Stephane Ducasse
Hi I decided to start to migrate the Seaside book to Pillar and make it a community-oriented book. I will work regularly on it and offer it as a gift to the community. https://github.com/SquareBracketAssociates/DynamicWebDevelopmentWithSeaside If some of you want to join the effort, you are welc