- Pharo-dev - lists.pharo.org

about threeWayCompareTo:
by ducasse Sept. 16, 2019

Sept. 16, 2019

I see threeWayCompareTo: aString "Do a three-way comparison between the receiver and anotherObject, returning -1 if self < anotherObject 0 if self = anotherObject 1 if self > anotherObject This assumes a total order in accordance with the mathematical law of trichotomy. See also: http://en.wikipedia.org/wiki/Three-way_comparison" ^ (self compare: self with: aString collated: AsciiOrder) - 2 And I thought that we got a new primitive returning -101 directly Is it not the case? Stef String>>compare: string1 with: string2 collated: order "'abc' = 'abc' asWideString >>> true" "'abc' asWideString = 'abc' >>> true" "(ByteArray with: 97 with: 0 with: 0 with: 0) asString ~= 'a000' asWideString >>> true" "('abc' sameAs: 'aBc' asWideString) >>> true" "('aBc' asWideString sameAs: 'abc') >>> true" "('a000' asWideString ~= (ByteArray with: 97 with: 0 with: 0 with: 0) asString) >>> true" "((ByteArray with: 97 with: 0 with: 0 with: 0) asString sameAs: 'Abcd' asWideString) >>> false" "('a000' asWideString sameAs: (ByteArray with: 97 with: 0 with: 0 with: 0) asString) >>> false" (string1 isByteString and: [string2 isByteString]) ifTrue: [ ^ ByteString compare: string1 with: string2 collated: order]. "Primitive does not fail properly right now" ^ String compare: string1 with: string2 collated: order ByteString>>compare: string1 with: string2 collated: order "Return 1, 2 or 3, if string1 is <, =, or > string2, with the collating order of characters given by the order array." | len1 len2 c1 c2 | <primitive: 'primitiveCompareString' module: 'MiscPrimitivePlugin'> <var: #string1 declareC: 'unsigned char *string1'> <var: #string2 declareC: 'unsigned char *string2'> <var: #order declareC: 'unsigned char *order'> len1 := string1 size. len2 := string2 size. 1 to: (len1 min: len2) do: [:i | c1 := order at: (string1 basicAt: i) + 1. c2 := order at: (string2 basicAt: i) + 1. c1 = c2 ifFalse: [c1 < c2 ifTrue: [^ 1] ifFalse: [^ 3]]]. len1 = len2 ifTrue: [^ 2]. len1 < len2 ifTrue: [^ 1] ifFalse: [^ 3].

3 4

[Pharo 8.0] Build #743: 4609-Package-comment-for-System-SessionManager
by ci-pharo-ci-jenkins2＠inria.fr Sept. 16, 2019

Sept. 16, 2019

There is a new Pharo build available! The status of the build #743 was: FAILURE. The Pull Request #4610 was integrated: "4609-Package-comment-for-System-SessionManager" Pull request url: https://github.com/pharo-project/pharo/pull/4610 Issue Url: https://github.com/pharo-project/pharo/issues/4609 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #742: 4627-Small-Stack-cleanups
by ci-pharo-ci-jenkins2＠inria.fr Sept. 16, 2019

Sept. 16, 2019

There is a new Pharo build available! The status of the build #742 was: SUCCESS. The Pull Request #4628 was integrated: "4627-Small-Stack-cleanups" Pull request url: https://github.com/pharo-project/pharo/pull/4628 Issue Url: https://github.com/pharo-project/pharo/issues/4627 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #741: 4614-Remove-unnecessary-dots
by ci-pharo-ci-jenkins2＠inria.fr Sept. 16, 2019

Sept. 16, 2019

There is a new Pharo build available! The status of the build #741 was: SUCCESS. The Pull Request #4615 was integrated: "4614-Remove-unnecessary-dots" Pull request url: https://github.com/pharo-project/pharo/pull/4615 Issue Url: https://github.com/pharo-project/pharo/issues/4614 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #740: 4559-visitSlotInitializationNode-should-not-be-subclassResponsibility
by ci-pharo-ci-jenkins2＠inria.fr Sept. 16, 2019

Sept. 16, 2019

There is a new Pharo build available! The status of the build #740 was: FAILURE. The Pull Request #4560 was integrated: "4559-visitSlotInitializationNode-should-not-be-subclassResponsibility" Pull request url: https://github.com/pharo-project/pharo/pull/4560 Issue Url: https://github.com/pharo-project/pharo/issues/4559 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #739: 4622-Cleanup-Arrayed-collections-tests
by ci-pharo-ci-jenkins2＠inria.fr Sept. 16, 2019

Sept. 16, 2019

There is a new Pharo build available! The status of the build #739 was: FAILURE. The Pull Request #4623 was integrated: "4622-Cleanup-Arrayed-collections-tests" Pull request url: https://github.com/pharo-project/pharo/pull/4623 Issue Url: https://github.com/pharo-project/pharo/issues/4622 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

I have a dream... or why I think that compatibility is an illusion and bring us to the past
by ducasse Sept. 16, 2019

Sept. 16, 2019

I would love to retract ? and ! from the list of binary selectors. Iâm super super frustrated that predicates cannot be easily identifiable. for example is lineUpBlockBrackets an action or a testing method. I think that we are trapped in mistakes from the past. In racket and scheme and I guess ruby too we can use ? in the method and this change the game. self lineUpBlockBrackets? We have plenty of binary selector parts that are not used and think that it is frustrating. Let us check: Character specialCharacters '+-/\*~<>=@,%|&?!Â·Ã·Â±Ã' + - / \ ~ < > = @ , & | % those are ok I have no idea what is Â· nor how to type it. Ã· looks from the past. Â± so funny Ã no idea what it is andâ¦. Then we have two that could really improve our language ? and ! Do not tell me that there is a value in these selectors? (#(#+ #- #/ #\ #* #~ #< #> #= #@ #, #% #| #& #? #!) combinations select: [ :each | each size = 3 and: [ each includesAnyOf: #(#? #!) ] ]) collect: [ :each | each first, each second, each third ] #(#'+-?' #'+-!' #'+/?' #'+/!' #'+\?' #'+\!' #'+*?' #'+*!' #'+~?' #'+~!' #'+<?' #'+<!' #'+>?' #'+>!' #'+=?' #'+=!' #'+@?' #'+@!' #'+,?' #'+,!' #'+%?' #'+%!' #'+|?' #'+|!' #'+&?' #'+&!' #'+?!' #'-/?' #'-/!' #'-\?' #'-\!' #'-*?' #'-*!' #'-~?' #'-~!' #'-<?' #'-<!' #'->?' #'->!' #'-=?' #'-=!' #'-@?' #'-@!' #'-,?' #'-,!' #'-%?' #'-%!' #'-|?' #'-|!' #'-&?' #'-&!' #'-?!' #'/\?' #'/\!' #'/*?' #'/*!' #'/~?' #'/~!' #'/<?' #'/<!' #'/>?' #'/>!' #'/=?' #'/=!' #'/@?' #'/@!' #'/,?' #'/,!' #'/%?' #'/%!' #'/|?' #'/|!' #'/&?' #'/&!' #'/?!' #'\*?' #'\*!' #'\~?' #'\~!' #'\<?' #'\<!' #'\>?' #'\>!' #'\=?' #'\=!' #'\@?' #'\@!' #'\,?' #'\,!' #'\%?' #'\%!' #'\|?' #'\|!' #'\&?' #'\&!' #'\?!' #'*~?' #'*~!' #'*<?' #'*<!' #'*>?' #'*>!' #'*=?' #'*=!' #'*@?' #'*@!' #'*,?' #'*,!' #'*%?' #'*%!' #'*|?' #'*|!' #'*&?' #'*&!' #'*?!' #'~<?' #'~<!' #'~>?' #'~>!' #'~=?' #'~=!' #'~@?' #'~@!' #'~,?' #'~,!' #'~%?' #'~%!' #'~|?' #'~|!' #'~&?' #'~&!' #'~?!' #'<>?' #'<>!' #'<=?' #'<=!' #'<@?' #'<@!' #'<,?' #'<,!' #'<%?' #'<%!' #'<|?' #'<|!' #'<&?' #'<&!' #'<?!' #'>=?' #'>=!' #'>@?' #'>@!' #'>,?' #'>,!' #'>%?' #'>%!' #'>|?' #'>|!' #'>&?' #'>&!' #'>?!' #'=@?' #'=@!' #'=,?' #'=,!' #'=%?' #'=%!' #'=|?' #'=|!' #'=&?' #'=&!' #'=?!' #'@,?' #'@,!' #'@%?' #'@%!' #'@|?' #'@|!' #'@&?' #'@&!' #'@?!' #',%?' #',%!' #',|?' #',|!' #',&?' #',&!' #',?!' #'%|?' #'%|!' #'%&?' #'%&!' #'%?!' #'|&?' #'|&!' #'|?!' #'&?!â) may be this one #&?! is useful for WTF! And because of that we sacrifice having nice method names! I really think that we should change that. S.

14 27

[Pharo 8.0] Build #738: Fixes: #4602 format: examples should be separated
by ci-pharo-ci-jenkins2＠inria.fr Sept. 16, 2019

Sept. 16, 2019

There is a new Pharo build available! The status of the build #738 was: SUCCESS. The Pull Request #4604 was integrated: "Fixes: #4602 format: examples should be separated" Pull request url: https://github.com/pharo-project/pharo/pull/4604 Issue Url: https://github.com/pharo-project/pharo/issues/4602 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Re: [Pharo-dev] Pharo Launcher is broken out of the box.
by Christophe Demarey Sept. 16, 2019

Sept. 16, 2019

Hi Todd, Thanks for the report. Could you create an issue on Github and explain the way to reproduce? https://github.com/pharo-project/pharo-launcher/issues Regards, Christophe > Le 15 sept. 2019 Ã 21:04, Todd Blanchard via Pharo-dev <pharo-dev(a)lists.pharo.org> a Ã©crit : > > > De: Todd Blanchard <tblanchard(a)mac.com> > Objet: Pharo Launcher is broken out of the box. > Date: 15 septembre 2019 Ã 21:04:43 UTC+2 > Ã: Pharo Development List <pharo-dev(a)lists.pharo.org> > > > I just downloaded the latest Pharo Launcher. > > It is throwing some errors. > > <PharoLauncher.image 2019-09-15 11-36-27.png> > >

2 1

Pharo Launcher is broken out of the box.
by Todd Blanchard Sept. 15, 2019

Sept. 15, 2019

I just downloaded the latest Pharo Launcher. It is throwing some errors.

1 0