November 2017 - Pharo-dev - lists.pharo.org

about SortFunctions

by Nicolas Cellier

Hi all, I started a discussion with Denis in a pull request https://github.com/pharo-project/pharo/pull/430 But since it's going beyond simple code review, it probably has a better place here. First, I want to say thanks for enriching this original work of Travis Griggs. http://objology.blogspot.fr/2010/11/tag-sortfunctions-redux.html http://objology.blogspot.fr/2010/11/tag-sortfunctions.html <http://objology.blogspot.fr/2010/11/tag-sortfunctions-redux.html> Of course, I'm never satisfied. So I don't really appreciate the rewrite of space ship operator <=> into a more heavy threeWayCompareTo: In my eyes, it's so obvious that <=> means < or = or > in the context of SortFunction And also that the order matches the signs < = > -1 0 1 IOW result will be -1 if receiver is <, 0 if equal, +1 if superior #threeWayCompareTo: does not tell as well. But maybe It's a question of taste and I don't have the same eyes as Pharo people? To me it's also a question of respect to the original author, don't change a good selector for the sake of changing. Apart this detail, I wanted to speak about SortByPropertyFunction. SortByProperty is super usefull for composing / chaining like this: population sortBy: #name ascending , #age descending. But currently, SortByPropertyFunction is allways using the default hardcoded collation <=> ... He he, it's also notice it's shorter to write ;) Imagine that my properties are neither String nor Magnitude, or they are, but I want a different collation policy, because in French $Ã© must not be sorted too far from $e. It could be written quite simply with: c sortBy: #name collatedInFrench ascending , #age descending With current implementation, collatedInFrench would have to use a block (thru a CollatorBlockFunction which is a proxy to the block in a SortFunction disguise): Symbol>>collatedInFrench "interpret self as a property" ^[:a :b | FrenchCollator collate: (self value: a) with: (self value: b)] But IMO SortByPropertyFunction should better feed a reified CollatorFunction, or said differently a SortFunction, as Denis said. Symbol>>collatedInFrench ^FrenchCollator new onProperty: self SortFunction>>onProperty: aValuable ^SortByPropertyFunction sortProperty: aValuable with: self What do you think? Nicolas

Nov. 4, 2017

Re: [Pharo-dev] SqueakSSL on Pharo 64bit/Win

by Nicolas Cellier

Note that win64 SSL works at least since https://github.com/OpenSmalltalk/opensmalltalk-vm/commit/baa70862014d3bb510… and https://github.com/OpenSmalltalk/opensmalltalk-vm/commit/caa8241de11b99ecae… Maybe it's a bit too recent to be found in official Pharo distribution, but if you can live with bleeding edge, pick a more recent VM here: https://bintray.com/opensmalltalk/vm/cog/201710221351#files (or maybe you can find one from the Pharo site?) 2017-11-04 22:21 GMT+01:00 henry <henry(a)callistohouse.club>: > This is the advantage of in-image SSL solution, found in the Cryptography > repository: > > http://www.squeaksource.com/Cryptography.html > > Sent from ProtonMail Mobile > > > On Fri, Nov 3, 2017 at 12:53, Raffaello Giulietti < > raffaello.giulietti(a)lifeware.ch> wrote: > > Hi, the SqueakSSL dll is not included in the Pharo 64bit/Win vm > distribution. I guess this has to do with problems in building it. Anybody > knows where the difficulties lie? Greetings Raffaello > >

Nov. 4, 2017

Re: [Pharo-dev] SqueakSSL on Pharo 64bit/Win

by henry

This is the advantage of in-image SSL solution, found in the Cryptography repository: http://www.squeaksource.com/Cryptography.html Sent from ProtonMail Mobile On Fri, Nov 3, 2017 at 12:53, Raffaello Giulietti <raffaello.giulietti(a)lifeware.ch> wrote: > Hi, the SqueakSSL dll is not included in the Pharo 64bit/Win vm distribution. I guess this has to do with problems in building it. Anybody knows where the difficulties lie? Greetings Raffaello

Nov. 4, 2017

Fwd: Re: [saag] Fw: [internet-draft-draft] ParrotTalk: Anonymous P2P encryption

by henry

I am preparing an Internet Draft for submission through IETF. Listed below. Sent from ProtonMail Mobile > ---------- Forwarded message ---------- > From: Bob<robert.withers(a)protonmail.com> > Date: On Sat, Nov 4, 2017 at 13:56 > Subject: Fwd: Re: [saag] Fw: [internet-draft-draft] ParrotTalk: Anonymous P2P encryption > To: Bob <robert.withers(a)protonmail.com> > Cc: SAAG <saag(a)ietf.org> > > I updated the I-D located here: http://jmp.sh/VRejS2g > > Thank you for your consideration, > - HH > >> -------- Original Message -------- >> Subject: [saag] Fw: [internet-draft-draft] ParrotTalk: Anonymous P2P encryption >> Local Time: November 3, 2017 9:07 AM >> UTC Time: November 3, 2017 1:07 PM >> From: robert.withers(a)protonmail.com >> To: SAAG <saag(a)ietf.org> >> >> Good morning, >> >> I am forwarding this announcement of the ParrotTalk v3.6 specification and 2 reference implementations, in Squeak/Pharo and Java, to the SAAG list. I was advised that this mailing list regarding the Security Area is the correct home for this announcement. Below, I corrected the version of the Squeak/Pharo ParrotTalk code to version 11, interoperable with the Java version. I am proceeding to work on the Internet-Draft and I hope some discussion builds around this work. >> >> Thank you. >> - HH >> >>> -------- Original Message -------- >>> Subject: [internet-draft-draft] ParrotTalk: Anonymous P2P encryption >>> Local Time: November 2, 2017 9:19 PM >>> UTC Time: November 3, 2017 1:19 AM >>> From: henry(a)callistohouse.club >>> To: IETF <ietf(a)ietf.org> >>> >>> I have developed the ParrotTalk Protocol, and am starting an internet draft document[1] for submission to the process at IETF. >>> >>> ParrotTalk Protocol is documented in part here[2], while I have two implementations: 1 in Squeak/Pharo[3 a/b] and the other in Java[4 a/b]. The particulars of MAC key and ivSequence derivation, as well as constrained traffic signing, are the implementations, yet missing from the specification. They will be added to the internet-draft. >>> >>> How do I go about submitting a specification for ParrotTalk for IETF review and consideration? >>> >>> Thank you. >>> >>> - HH >>> - HH >>> - HH >>> - HH >>> - HH >>> - HH >>> - HH >>> - HH

Nov. 4, 2017

Re: [Pharo-dev] How to update currently used VM for PharoLauncher?

by Christophe Demarey

Hi Stefan, > Le 3 nov. 2017 Ã 17:23, stephan <stephan(a)stack.nl> a Ã©crit : > > I've noticed a few VM updates I want to use with PharoLauncher. > What is the currently recommended way to update my PharoLauncher to use > a non-stable version? For now, the way to get a fresh VM for the current development image (i.e. 70) is to delete it from the VM store ($HOME/Documents/Pharo/vms/70 on OS X) and try to run again the image will download the latest stable VM. If you need another VM, you will have to install it by hand in the same directory. There is currently no option to get an alpha VM. It makes sense only for the development image but it could be a nice option to add to the launcher. Do you think it will be used? Christophe

Nov. 4, 2017

Re: [Pharo-dev] [Pharo 7.0-dev] Build #259: 20634 missing super messages in set up and tear down in kernel tests unit tests

by Pavel Krivanek

[32] Executing: program /usr/bin/ssh host file-pharo.inria.fr, user filepharosync, command scp -v -d -t /appli/files.pharo.org/image/70/ [32] OpenSSH_7.2p2 Ubuntu-4ubuntu2.1, OpenSSL 1.0.2g 1 Mar 2016 [32] debug1: Reading configuration data /etc/ssh/ssh_config [32] debug1: /etc/ssh/ssh_config line 19: Applying options for * [32] debug1: Connecting to file-pharo.inria.fr [128.93.162.72] port 22. [32] debug1: Connection established. [32] debug1: key_load_public: No such file or directory [32] debug1: identity file /builds/.ssh/id_rsa type -1 2017-11-04 10:50 GMT+01:00 <ci-pharo-ci-jenkins2(a)inria.fr>: > There is a new Pharo build available! > > The status of the build #259 was: FAILURE. > > The Pull Request #432 was integrated: "20634 missing super messages in set > up and tear down in kernel tests unit tests" > Pull request url: https://github.com/pharo-project/pharo/pull/432 > > Issue Url: https://pharo.fogbugz.com/f/cases/20634 > Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending% > 20pull%20request%20and%20branch%20Pipeline/job/development/259/ >

Nov. 4, 2017

[Pharo 7.0-dev] Build #259: 20634 missing super messages in set up and tear down in kernel tests unit tests

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #259 was: FAILURE. The Pull Request #432 was integrated: "20634 missing super messages in set up and tear down in kernel tests unit tests" Pull request url: https://github.com/pharo-project/pharo/pull/432 Issue Url: https://pharo.fogbugz.com/f/cases/20634 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 4, 2017

Re: [Pharo-dev] How to update currently used VM for PharoLauncher?

by Sean P. DeNigris

Stephan Eggermont-3 wrote > way to update my PharoLauncher to use > a non-stable version? On the Mac, I delete Launcher's VM for that Pharo image version and let Launcher DL a new one. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Nov. 4, 2017

SqueakSSL on Pharo 64bit/Win

by Raffaello Giulietti

Hi, the SqueakSSL dll is not included in the Pharo 64bit/Win vm distribution. I guess this has to do with problems in building it. Anybody knows where the difficulties lie? Greetings Raffaello

Nov. 3, 2017

[Pharo 7.0-dev] Build #258: 20623-Tests-in-the-CI-should-say-the-Architecture-and-the-OS

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #258 was: SUCCESS. The Pull Request #424 was integrated: "20623-Tests-in-the-CI-should-say-the-Architecture-and-the-OS" Pull request url: https://github.com/pharo-project/pharo/pull/424 Issue Url: https://pharo.fogbugz.com/f/cases/20623 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 3, 2017