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

Message>>#= & Message>>#hash
by Eliot Miranda Nov. 20, 2018

Nov. 20, 2018

Hi All, In VisualWorks Message implements #= & #hash naturally; two messages whose selectors and arguments are #= are also equal. But in Cuis, Squeak and Pharo Message inherits #= and #hash from Object, i.e. uses identity comparison. This is, to say the least, annoying. Any objections to implementing comparing in Message to match VisualWorks? _,,,^..^,,,_ best, Eliot

4 5

Re: [Pharo-dev] [squeak-dev] Message>>#= & Message>>#hash
by Chris Muller Nov. 20, 2018

Nov. 20, 2018

It sounds good, but an Inbox submission would go a long way to understanding exactly what you mean esp. re: understanding this special condition with the lookupClass being nil... and whether it deserves a first-class name or not... On Tue, Nov 20, 2018 at 4:10 AM Levente Uzonyi <leves(a)caesar.elte.hu> wrote: > > On Mon, 19 Nov 2018, Eliot Miranda wrote: > > > Hi David, > > > > On Mon, Nov 19, 2018 at 9:52 AM David T. Lewis <lewis(a)mail.msen.com> wrote: > > On Mon, Nov 19, 2018 at 09:32:17AM -0800, Eliot Miranda wrote: > > > Hi All, > > > > > > In VisualWorks Message implements #= & #hash naturally; two messages > > > whose selectors and arguments are #= are also equal. But in Cuis, Squeak > > > and Pharo Message inherits #= and #hash from Object, i.e. uses identity > > > comparison. This is, to say the least, annoying. Any objections to > > > implementing comparing in Message to match VisualWorks? > > > > > > > That sounds like an obviously good thing to do :-) > > > > Is the lookupClass instance variable relevant for comparisons? I am > > guessing not, since we already have #analogousCodeTo: for that type of > > comparison. > > > > > > For me it is relevant. Two messages with different lookupClasses, e.g. one with nil and one with a specific class, represent different messages, one a normal send one a super send. So my changes in > > waiting include lookupClass in both hash and =. I don't think it makes much difference, but the incompatibility with VisualWorks, while regrettable, feels correct to me. > > What about Behavior >> #hash? It uses the name of the class, which is fine > as long as you don't rename your classes while you store them in hashed > collections. > > Levente > > > > > Dave > > > > > > _,,,^..^,,,_ > > best, Eliot > > > >

1 0

[Pharo 7.0-dev] Build #1409: 22685-add-value-reification-support-for-Literal-node
by ci-pharo-ci-jenkins2＠inria.fr Nov. 20, 2018

Nov. 20, 2018

There is a new Pharo build available! The status of the build #1409 was: FAILURE. The Pull Request #2005 was integrated: "22685-add-value-reification-support-for-Literal-node" Pull request url: https://github.com/pharo-project/pharo/pull/2005 Issue Url: https://pharo.fogbugz.com/f/cases/22685 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1408: Add AST dump from an existing AST
by ci-pharo-ci-jenkins2＠inria.fr Nov. 20, 2018

Nov. 20, 2018

There is a new Pharo build available! The status of the build #1408 was: SUCCESS. The Pull Request #2001 was integrated: "Add AST dump from an existing AST" Pull request url: https://github.com/pharo-project/pharo/pull/2001 Issue Url: https://pharo.fogbugz.com/f/cases/feature/parseDump Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

2 1

Contributor license agreement via modern transport?
by Hans-Martin Nov. 19, 2018

Nov. 19, 2018

Hi, do you know whether StÃ©phane will accept contributor license agreements as scanned and e-mailed documents (can be digitally signed using PGP as well)? Or does one really have to print out and mail a piece of dead tree? :-) Cheers, Hans-Martin -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

2 1

Pharo 7 speed compared to VW
by Shaping Nov. 19, 2018

Nov. 19, 2018

(Second try in 6 days. Does anyone have recent performance data for Pharo 7 relative to VW 7.10 or later?) From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of Shaping Sent: Tuesday, November 13, 2018 00:33 To: 'Pharo Development List' <pharo-dev(a)lists.pharo.org> Subject: [Pharo-dev] Pharo 7 speed compared to VW (was: The STON Specification, Cog speed, and namespaces/modules) Does anyone know whether Pharo 7 is as fast as VW 7.10 or later? Do we have recent comparative benchmarks? The comparison should ignore potential GPU-based improvement in my algo; that will happen later. The test should involve some math, file streaming, and the parsing that entailsâan ordinary mix of macrobenchmarks. The comparison should be based on both Pharo 7 and VW each running a single Smalltalk Process (one time-slice of one OS thread in one OS process). I need Pharo 7 speed to be comparable or better to justify the port. Pharo is definitely looking and working better. Iâve spend more time with it last few weeks than during the previous decade. Thanks to everyone for the effort and improvements. Shaping From: Shaping [mailto:shaping@uurda.org] Sent: Wednesday, November 7, 2018 00:41 To: 'Pharo Development List' <pharo-dev(a)lists.pharo.org <mailto:pharo-dev@lists.pharo.org> > Subject: RE: [Pharo-dev] [ANN] The STON Specification, Cog speed, and namespaces/modules Hi Eliot. Pharo (& Squeak & Cuis) Float subclass BoxedFloat64 maps exactly to VW's Double. In 64-bit SmallFloat64 maps exactly to SmallDouble. But I wonder whether there is any issue here. STON would use the print strings for (PSC) Float / (VW) Double, and so deseerialization on Pharo would automatically produce the right class. Going in the other direction might need some help. APF needs support in PSC before one can port, but are representable as suitably-sized word arrays. There is no support for __float128 anywhere in the VM (e.g. not even in the FFI) on PSC as yet. I see Pharoâs WordArray. Iâll work on an APF for Pharo, as time permits. Iâm using APFs in VW in the 300-bit range, and want to reduce the needed precision to 64 bits, to save space and time on large (5 million+) scalar time-series, both on the heap and during BOSSing (25 m save-time now). The problem is not so much an issue for the JulianDayNumber (JDN)-precision, which is adequate in this app at 14 to 15 digits (even though my JDN class subclasses APF, for now). Other calculations need the more extreme precision. I think I can make 128-bit floats work, and would really like to see a small, fast, boxed 128-bit float implementation in Pharo or VW. The APFs are big and slow. Where in the queue of planned improvements to Pharo does such a task lie? I suspect itâs not a very popular item. Broadening the issue somewhat, Iâm trying to find as many good reasons as possible to justify the work needed to port all my VW stuff to Pharo. Iâve seen the references to Cogâs speed and coming speed-up. Are there recent (say, in the last year) benchmarks comparing VW and Pharo? Any details here would be very much appreciated. Having no namespaces in Pharo is, I think, the biggest impediment. I prefer not to prefix class names, but there may be fewer name-collisions than I suppose--maybe none. Still, I need to know how VW and Pharo classes map in order to place overrides and extensions correctly. Besides the mentioned float-class mappings is there a reference on this? Object allSubclasses in Pharo 7 64-bit, produces 14946 classes. Pharo is a little bigger than it used to be. I suppose I donât need to check all unloaded packages because all classes in each of those will have the same unique prefix. Is that correct? Or, I could just load every package I can find, before I check names. But that little experiment has never gone well in the past. Is the Pharo-with-namespaces issue dead or merely suspended, awaiting a more fitting idea than what VW currently offers? Shaping On Tue, Nov 6, 2018 at 12:56 AM Shaping <shaping(a)uurda.org <mailto:shaping@uurda.org> > wrote: STON is able to serialise Pharoâs Floats, what do you mean by double ? Floating-point numbers in IEEE 64-bit format, 14 or 15 significant digits, with a range between =10^307 and 10^307. Additionally, I recently asked Sven if t would be possible to store ScaledDecimals (I think it implements what you call ArbitraryPrecisionFloats) without loss of precision. Iâm referring to VWâs Double (and SmallDouble in 64-bit engines/images). APFs are binary representations that can be arbitrarily large, using Integers (LargePositiveIntegers for example) to model the bits of the mantissa. Before, because STON extends JSON, it was storing all kind of numbers either as float or integer. Now, thanks to Sven, STON stores ScaledDecimals correctly (without loss of precision through serialisation as float, what was done before). But I do not know if this change is integrated in recent images yet. â¦.. Number subclass: #Float instanceVariableNames: '' classVariableNames: 'E Epsilon Halfpi Infinity Ln10 Ln2 MaxVal MaxValLn MinValLogBase2 NaN NegativeInfinity NegativeZero Pi RadiansPerDegree Sqrt2 ThreePi Twopi' poolDictionaries: '' category: 'Kernel-Numbers' My instances represent IEEE-754 floating-point double-precision numbers. They have about 16 digits of accuracy and their range is between plus and minus 10^307. Some valid examples are: 8.0 13.3 0.3 2.5e6 1.27e-30 1.27e-31 -12.987654e12 â¦. I see that Pharoâs Float is VWâs Double. So then I just need to be able to serialize APF. â¦. FIFloatType subclass: #FFIFloat128 instanceVariableNames: '' classVariableNames: '' poolDictionaries: '' category: 'UnifiedFFI-Types' I'm a 128bits (cuadruple precision) float. It is usually not used, but some compiler modes support it (__float128 in gcc) THIS IS NOT YET SUPPORTED â¦. The class above is also from the Pharo 7 image. This is the largest of the c-type FFIFloats. Any Float classes of this size and larger for the Smalltalk heap on 64-bit Pharo? Cheers, Shaping Le 6 nov. 2018 Ã 06:58, Shaping <shaping(a)uurda.org <mailto:shaping@uurda.org> > a Ã©crit : (Having domain problems recently. Please excuse this posting if you have seen it twice. I've not seen it appear yet on the list.) Can STON be extended to handle Doubles and ArbitraryPrecisionFloats? Shaping -----Original Message----- From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of David T. Lewis Sent: Wednesday, October 31, 2018 14:58 To: Pharo Development List <pharo-dev(a)lists.pharo.org <mailto:pharo-dev@lists.pharo.org> > Subject: Re: [Pharo-dev] [ANN] The STON Specification This is very clear and well written. Dave Hi, Since there can never be enough documentation I finally took some time to write a more formal description of STON as a data format. https://github.com/svenvc/ston/blob/master/ston-spec.md The idea is to let this stabilise a bit and to then update the two other documents describing STON, where necessary: https://github.com/svenvc/ston/blob/master/ston-paper.md https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuc cessfulBuild/artifact/book-result/STON/STON.html Also, the latest changes in STON have to make their way to the Pharo image as well. https://github.com/svenvc/ston All feedback is welcome. Sven -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org -- _,,,^..^,,,_ best, Eliot

2 1

[Pharo 7.0-dev] Build #1407: 22684-testNoUnusedTemporaryVariablesLeft-uses-all-CompiledMethod-instances
by ci-pharo-ci-jenkins2＠inria.fr Nov. 19, 2018

Nov. 19, 2018

There is a new Pharo build available! The status of the build #1407 was: FAILURE. The Pull Request #2003 was integrated: "22684-testNoUnusedTemporaryVariablesLeft-uses-all-CompiledMethod-instances" Pull request url: https://github.com/pharo-project/pharo/pull/2003 Issue Url: https://pharo.fogbugz.com/f/cases/22684 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1406: 22682-when-callback-fails-a-default-value-should-be-returned-to-prevent-crashes
by ci-pharo-ci-jenkins2＠inria.fr Nov. 19, 2018

Nov. 19, 2018

There is a new Pharo build available! The status of the build #1406 was: SUCCESS. The Pull Request #2002 was integrated: "22682-when-callback-fails-a-default-value-should-be-returned-to-prevent-crashes" Pull request url: https://github.com/pharo-project/pharo/pull/2002 Issue Url: https://pharo.fogbugz.com/f/cases/22682 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1405: 22643-Image-not-opening---portability-
by ci-pharo-ci-jenkins2＠inria.fr Nov. 19, 2018

Nov. 19, 2018

There is a new Pharo build available! The status of the build #1405 was: SUCCESS. The Pull Request #1996 was integrated: "22643-Image-not-opening---portability-" Pull request url: https://github.com/pharo-project/pharo/pull/1996 Issue Url: https://pharo.fogbugz.com/f/cases/22643 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Esteban's ChangeLog week of 12 November 2018
by estebanlm＠gmail.com Nov. 19, 2018

Nov. 19, 2018

Hello! This is my weekly ChangeLog, from 12 November 2018 to 18 November 2018. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=12/11/2018&to=18/11/2018 ChangeLog ========= 16 November 2018: ----------------- * I made a [pull request](https://github.com/pharo-project/pharo/pull/1998) to update Calypso to [version 0.13.0](https://github.com/pharo-ide/Calypso/releases/tag/v0.13.0) 14 November 2018: ----------------- * I needed to revisit [case: 22659](https://pharo.fogbugz.com/f/cases/22659) (and it took last two days to fix it properly :P) But well, now we should be having correct file names for all versions. 13 November 2018: ----------------- * I fixed [case: 22659](https://pharo.fogbugz.com/f/cases/22659), with this [pull request](https://github.com/pharo-project/pharo/pull/1975). Problem was that tagging system was correctly naming version inside the image, but it was not doing anything with file names (then the filenames were hardcoded to Pharo7.0-alpha). cheers! Esteban

1 0

[ANN] Camp Smalltalk 2019 in Charlotte, NC
by Mariano Martinez Peck Nov. 18, 2018

Nov. 18, 2018

Greetings Fellow Smalltalkers, We would like to invite you to Camp Smalltalk, March 29th â March 31st 2019 in Charlotte, North Carolina. Event details and registration info are available at the following link: Camp Smalltalk Charlotte 2019 <https://www.eventbrite.com/e/camp-smalltalk-charlotte-2019-tickets-52380940…> Hope to see you there! -- Mariano

2 2

Windows lack of ssh-agent versus Default Custom SSH Keys
by Ben Coman Nov. 18, 2018

Nov. 18, 2018

For Iceberg. what is the likely hood that soon something like ssh-agent will be working on Windows? So that "Custom SSH Keys" doesn't need to be set every time a new image is started? If "Custom SSH Keys" will be the main option for the foreseeable future, would it make sense to enabled it by default to make one less thing to trip up newcomers? cheers -ben

2 1

[Pharo 7.0-dev] Build #1404: 22680-add-support-for-operation-types-assignment-return-Some-cleanups
by ci-pharo-ci-jenkins2＠inria.fr Nov. 18, 2018

Nov. 18, 2018

There is a new Pharo build available! The status of the build #1404 was: SUCCESS. The Pull Request #2000 was integrated: "22680-add-support-for-operation-types-assignment-return-Some-cleanups" Pull request url: https://github.com/pharo-project/pharo/pull/2000 Issue Url: https://pharo.fogbugz.com/f/cases/22680 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1403: Add pattern to #expandMacros supporting line feeds
by ci-pharo-ci-jenkins2＠inria.fr Nov. 16, 2018

Nov. 16, 2018

There is a new Pharo build available! The status of the build #1403 was: SUCCESS. The Pull Request #1997 was integrated: "Add pattern to #expandMacros supporting line feeds" Pull request url: https://github.com/pharo-project/pharo/pull/1997 Issue Url: https://pharo.fogbugz.com/f/cases/22674 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1402: 22673-OCNewCompilerWithChangesFunctionalTeststestBlockReturning-is-failing
by ci-pharo-ci-jenkins2＠inria.fr Nov. 15, 2018

Nov. 15, 2018

There is a new Pharo build available! The status of the build #1402 was: FAILURE. The Pull Request #1995 was integrated: "22673-OCNewCompilerWithChangesFunctionalTeststestBlockReturning-is-failing" Pull request url: https://github.com/pharo-project/pharo/pull/1995 Issue Url: https://pharo.fogbugz.com/f/cases/22673 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1401: 22668-Contextual-menu-does-not-show-up-when-pressing-Ctrlleft-click-on-Pharo-7
by ci-pharo-ci-jenkins2＠inria.fr Nov. 14, 2018

Nov. 14, 2018

There is a new Pharo build available! The status of the build #1401 was: SUCCESS. The Pull Request #1988 was integrated: "22668-Contextual-menu-does-not-show-up-when-pressing-Ctrlleft-click-on-Pharo-7" Pull request url: https://github.com/pharo-project/pharo/pull/1988 Issue Url: https://pharo.fogbugz.com/f/cases/22668 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1400: 22659-generated-artifacts-should-have-the-version-tag (postscriptum to the notes to the commentaries to the addendum)
by ci-pharo-ci-jenkins2＠inria.fr Nov. 14, 2018

Nov. 14, 2018

There is a new Pharo build available! The status of the build #1400 was: FAILURE. The Pull Request #1994 was integrated: "22659-generated-artifacts-should-have-the-version-tag (postscriptum to the notes to the commentaries to the addendum)" Pull request url: https://github.com/pharo-project/pharo/pull/1994 Issue Url: https://pharo.fogbugz.com/f/cases/22659 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Re: [Pharo-dev] [Pharo-users] [ANN] Pharo v7.0.0-rc1 released!
by Alistair Grant Nov. 14, 2018

Nov. 14, 2018

Hi Vitor, On Wed, 14 Nov 2018 at 14:37, Vitor Medina Cruz <vitormcruz(a)gmail.com> wrote: > > Got instant red crossed welcome window on windows 7 64bits with the Pharo 7 64 bits: "Error: Instances of SourceFileArray are not indexable". I will try on a windows 10 version later. Which VM are you using? (pharoconsole --version) I've seen this just once on Ubuntu 16.04 (64 bit), but wasn't able to reproduce it, and think it was a more recent VM than the current stable version. Thanks, Alistair

1 0

[Pharo 7.0-dev] Build #1399: 22659-generated-artifacts-should-have-the-version-tag (notes to the commentary to the addendum)
by ci-pharo-ci-jenkins2＠inria.fr Nov. 14, 2018

Nov. 14, 2018

There is a new Pharo build available! The status of the build #1399 was: FAILURE. The Pull Request #1993 was integrated: "22659-generated-artifacts-should-have-the-version-tag (notes to the commentary to the addendum)" Pull request url: https://github.com/pharo-project/pharo/pull/1993 Issue Url: https://pharo.fogbugz.com/f/cases/22659 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1398: 22659-generated-artifacts-should-have-the-version-tag (commentary to the addendum)
by ci-pharo-ci-jenkins2＠inria.fr Nov. 14, 2018

Nov. 14, 2018

There is a new Pharo build available! The status of the build #1398 was: FAILURE. The Pull Request #1992 was integrated: "22659-generated-artifacts-should-have-the-version-tag (commentary to the addendum)" Pull request url: https://github.com/pharo-project/pharo/pull/1992 Issue Url: https://pharo.fogbugz.com/f/cases/22659 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1396: 22659-generated-artifacts-should-have-the-version-tag (addendum to the addendum)
by ci-pharo-ci-jenkins2＠inria.fr Nov. 14, 2018

Nov. 14, 2018

There is a new Pharo build available! The status of the build #1396 was: FAILURE. The Pull Request #1991 was integrated: "22659-generated-artifacts-should-have-the-version-tag (addendum to the addendum)" Pull request url: https://github.com/pharo-project/pharo/pull/1991 Issue Url: https://pharo.fogbugz.com/f/cases/22659 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1395: 22659-generated-artifacts-should-have-the-version-tag (addendum)
by ci-pharo-ci-jenkins2＠inria.fr Nov. 14, 2018

Nov. 14, 2018

There is a new Pharo build available! The status of the build #1395 was: FAILURE. The Pull Request #1990 was integrated: "22659-generated-artifacts-should-have-the-version-tag (addendum)" Pull request url: https://github.com/pharo-project/pharo/pull/1990 Issue Url: https://pharo.fogbugz.com/f/cases/22659 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1394: 22659-generated-artifacts-should-have-the-version-tag (definitive compilation)
by ci-pharo-ci-jenkins2＠inria.fr Nov. 14, 2018

Nov. 14, 2018

There is a new Pharo build available! The status of the build #1394 was: FAILURE. The Pull Request #1989 was integrated: "22659-generated-artifacts-should-have-the-version-tag (definitive compilation)" Pull request url: https://github.com/pharo-project/pharo/pull/1989 Issue Url: https://pharo.fogbugz.com/f/cases/22659 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Debugger "Through" acting like "Into"
by Martin McClure Nov. 14, 2018

Nov. 14, 2018

In the latest Pharo 7 (Pharo-7.0.0+rc1.build.1384.sha.c34d6a69d9d01a2816df1f9fdc7388580163df29 (32 Bit)) it seems like clicking "Through" in the debugger often (but not always) has the effect of "Into", which seems wrong and makes stepping through code difficult. I don't know how new this behavior is. Is this a known behavior? If not, I'll characterize it further. Regards, -Martin

2 1

How do I create a binary stream
by Stephane Ducasse Nov. 13, 2018

Nov. 13, 2018

Hi I'm checking some of the mooc code in Pharo 70. The Pharo 50/60 version is PNGReadWriter createAFormFrom: 'Sprites.png' asFileReference binaryReadStream upToEnd I came up with PNGReadWriter formFromStream: (File named: 'Sprites.png') readStream And we can also have PNGReadWriter formFromStream: 'Sprites.png' asFileReference binaryReadStream I will add this in the comment of the formFromStream: method. Stef

4 11

[Pharo 7.0-dev] Build #1393: 22659-generated-artifacts-should-have-the-version-tag (V5)
by ci-pharo-ci-jenkins2＠inria.fr Nov. 13, 2018

Nov. 13, 2018

There is a new Pharo build available! The status of the build #1393 was: FAILURE. The Pull Request #1987 was integrated: "22659-generated-artifacts-should-have-the-version-tag (V5)" Pull request url: https://github.com/pharo-project/pharo/pull/1987 Issue Url: https://pharo.fogbugz.com/f/cases/22659 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1392: 22659-generated-artifacts-should-have-the-version-tag (V4)
by ci-pharo-ci-jenkins2＠inria.fr Nov. 13, 2018

Nov. 13, 2018

There is a new Pharo build available! The status of the build #1392 was: FAILURE. The Pull Request #1986 was integrated: "22659-generated-artifacts-should-have-the-version-tag (V4)" Pull request url: https://github.com/pharo-project/pharo/pull/1986 Issue Url: https://pharo.fogbugz.com/f/cases/22659 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1391: 22659-generated-artifacts-should-have-the-version-tag (V3)
by ci-pharo-ci-jenkins2＠inria.fr Nov. 13, 2018

Nov. 13, 2018

There is a new Pharo build available! The status of the build #1391 was: FAILURE. The Pull Request #1984 was integrated: "22659-generated-artifacts-should-have-the-version-tag (V3)" Pull request url: https://github.com/pharo-project/pharo/pull/1984 Issue Url: https://pharo.fogbugz.com/f/cases/22659 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1390: 22659-generated-artifacts-should-have-the-version-tag (V2)
by ci-pharo-ci-jenkins2＠inria.fr Nov. 13, 2018

Nov. 13, 2018

There is a new Pharo build available! The status of the build #1390 was: FAILURE. The Pull Request #1983 was integrated: "22659-generated-artifacts-should-have-the-version-tag (V2)" Pull request url: https://github.com/pharo-project/pharo/pull/1983 Issue Url: https://pharo.fogbugz.com/f/cases/22659 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1389: 22659-generated-artifacts-should-have-the-version-tag (V2)
by ci-pharo-ci-jenkins2＠inria.fr Nov. 13, 2018

Nov. 13, 2018

There is a new Pharo build available! The status of the build #1389 was: FAILURE. The Pull Request #1983 was integrated: "22659-generated-artifacts-should-have-the-version-tag (V2)" Pull request url: https://github.com/pharo-project/pharo/pull/1983 Issue Url: https://pharo.fogbugz.com/f/cases/22659 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1388: 22657-The-closing-of-a-window-using-a-keyboard-can-close-a-window-without-focus
by ci-pharo-ci-jenkins2＠inria.fr Nov. 13, 2018

Nov. 13, 2018

There is a new Pharo build available! The status of the build #1388 was: FAILURE. The Pull Request #1971 was integrated: "22657-The-closing-of-a-window-using-a-keyboard-can-close-a-window-without-focus" Pull request url: https://github.com/pharo-project/pharo/pull/1971 Issue Url: https://pharo.fogbugz.com/f/cases/22657 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1387: 22665-NECContextTesttestReceiverTempVar-is-failing-in-64-bit-image
by ci-pharo-ci-jenkins2＠inria.fr Nov. 13, 2018

Nov. 13, 2018

There is a new Pharo build available! The status of the build #1387 was: FAILURE. The Pull Request #1979 was integrated: "22665-NECContextTesttestReceiverTempVar-is-failing-in-64-bit-image" Pull request url: https://github.com/pharo-project/pharo/pull/1979 Issue Url: https://pharo.fogbugz.com/f/cases/22665 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1386: 22664-many-Opal-tests-are-failing-on-64-bit-image
by ci-pharo-ci-jenkins2＠inria.fr Nov. 13, 2018

Nov. 13, 2018

There is a new Pharo build available! The status of the build #1386 was: FAILURE. The Pull Request #1982 was integrated: "22664-many-Opal-tests-are-failing-on-64-bit-image" Pull request url: https://github.com/pharo-project/pharo/pull/1982 Issue Url: https://pharo.fogbugz.com/f/cases/22664 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1385: 22662-IntervalTest-is-failing-on-64-bit-image
by ci-pharo-ci-jenkins2＠inria.fr Nov. 13, 2018

Nov. 13, 2018

There is a new Pharo build available! The status of the build #1385 was: FAILURE. The Pull Request #1978 was integrated: "22662-IntervalTest-is-failing-on-64-bit-image" Pull request url: https://github.com/pharo-project/pharo/pull/1978 Issue Url: https://pharo.fogbugz.com/f/cases/22662 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1384: 22667-operation-support-for-Global-var-read-and-more-tests
by ci-pharo-ci-jenkins2＠inria.fr Nov. 13, 2018

Nov. 13, 2018

There is a new Pharo build available! The status of the build #1384 was: FAILURE. The Pull Request #1981 was integrated: "22667-operation-support-for-Global-var-read-and-more-tests" Pull request url: https://github.com/pharo-project/pharo/pull/1981 Issue Url: https://pharo.fogbugz.com/f/cases/22667 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1383: 22666-add-refications-for-operation-for-message-and-method
by ci-pharo-ci-jenkins2＠inria.fr Nov. 13, 2018

Nov. 13, 2018

There is a new Pharo build available! The status of the build #1383 was: SUCCESS. The Pull Request #1976 was integrated: "22666-add-refications-for-operation-for-message-and-method" Pull request url: https://github.com/pharo-project/pharo/pull/1976 Issue Url: https://pharo.fogbugz.com/f/cases/22666 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1382: 22558-FFICalloutresolveType-ignores-class-side-definition (v2)
by ci-pharo-ci-jenkins2＠inria.fr Nov. 13, 2018

Nov. 13, 2018

There is a new Pharo build available! The status of the build #1382 was: FAILURE. The Pull Request #1899 was integrated: "22558-FFICalloutresolveType-ignores-class-side-definition (v2)" Pull request url: https://github.com/pharo-project/pharo/pull/1899 Issue Url: https://pharo.fogbugz.com/f/cases/22558 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Pharo 7 speed compared to VW (was: The STON Specification, Cog speed, and namespaces/modules)
by Shaping Nov. 13, 2018

Nov. 13, 2018

Does anyone know whether Pharo 7 is as fast as VW 7.10 or later? Do we have recent comparative benchmarks? The comparison should ignore potential GPU-based improvement in my algo; that will happen later. The test should involve some math, file streaming, and the parsing that entailsâan ordinary mix of macrobenchmarks. The comparison should be based on both Pharo 7 and VW each running a single Smalltalk Process (one time-slice of one OS thread in one OS process). I need Pharo 7 speed to be comparable or better to justify the port. Pharo is definitely looking and working better. Iâve spend more time with it last few weeks than during the previous decade. Thanks to everyone for the effort and improvements. Shaping From: Shaping [mailto:shaping@uurda.org] Sent: Wednesday, November 7, 2018 00:41 To: 'Pharo Development List' <pharo-dev(a)lists.pharo.org> Subject: RE: [Pharo-dev] [ANN] The STON Specification, Cog speed, and namespaces/modules Hi Eliot. Pharo (& Squeak & Cuis) Float subclass BoxedFloat64 maps exactly to VW's Double. In 64-bit SmallFloat64 maps exactly to SmallDouble. But I wonder whether there is any issue here. STON would use the print strings for (PSC) Float / (VW) Double, and so deseerialization on Pharo would automatically produce the right class. Going in the other direction might need some help. APF needs support in PSC before one can port, but are representable as suitably-sized word arrays. There is no support for __float128 anywhere in the VM (e.g. not even in the FFI) on PSC as yet. I see Pharoâs WordArray. Iâll work on an APF for Pharo, as time permits. Iâm using APFs in VW in the 300-bit range, and want to reduce the needed precision to 64 bits, to save space and time on large (5 million+) scalar time-series, both on the heap and during BOSSing (25 m save-time now). The problem is not so much an issue for the JulianDayNumber (JDN)-precision, which is adequate in this app at 14 to 15 digits (even though my JDN class subclasses APF, for now). Other calculations need the more extreme precision. I think I can make 128-bit floats work, and would really like to see a small, fast, boxed 128-bit float implementation in Pharo or VW. The APFs are big and slow. Where in the queue of planned improvements to Pharo does such a task lie? I suspect itâs not a very popular item. Broadening the issue somewhat, Iâm trying to find as many good reasons as possible to justify the work needed to port all my VW stuff to Pharo. Iâve seen the references to Cogâs speed and coming speed-up. Are there recent (say, in the last year) benchmarks comparing VW and Pharo? Any details here would be very much appreciated. Having no namespaces in Pharo is, I think, the biggest impediment. I prefer not to prefix class names, but there may be fewer name-collisions than I suppose--maybe none. Still, I need to know how VW and Pharo classes map in order to place overrides and extensions correctly. Besides the mentioned float-class mappings is there a reference on this? Object allSubclasses in Pharo 7 64-bit, produces 14946 classes. Pharo is a little bigger than it used to be. I suppose I donât need to check all unloaded packages because all classes in each of those will have the same unique prefix. Is that correct? Or, I could just load every package I can find, before I check names. But that little experiment has never gone well in the past. Is the Pharo-with-namespaces issue dead or merely suspended, awaiting a more fitting idea than what VW currently offers? Shaping On Tue, Nov 6, 2018 at 12:56 AM Shaping <shaping(a)uurda.org <mailto:shaping@uurda.org> > wrote: STON is able to serialise Pharoâs Floats, what do you mean by double ? Floating-point numbers in IEEE 64-bit format, 14 or 15 significant digits, with a range between =10^307 and 10^307. Additionally, I recently asked Sven if t would be possible to store ScaledDecimals (I think it implements what you call ArbitraryPrecisionFloats) without loss of precision. Iâm referring to VWâs Double (and SmallDouble in 64-bit engines/images). APFs are binary representations that can be arbitrarily large, using Integers (LargePositiveIntegers for example) to model the bits of the mantissa. Before, because STON extends JSON, it was storing all kind of numbers either as float or integer. Now, thanks to Sven, STON stores ScaledDecimals correctly (without loss of precision through serialisation as float, what was done before). But I do not know if this change is integrated in recent images yet. â¦.. Number subclass: #Float instanceVariableNames: '' classVariableNames: 'E Epsilon Halfpi Infinity Ln10 Ln2 MaxVal MaxValLn MinValLogBase2 NaN NegativeInfinity NegativeZero Pi RadiansPerDegree Sqrt2 ThreePi Twopi' poolDictionaries: '' category: 'Kernel-Numbers' My instances represent IEEE-754 floating-point double-precision numbers. They have about 16 digits of accuracy and their range is between plus and minus 10^307. Some valid examples are: 8.0 13.3 0.3 2.5e6 1.27e-30 1.27e-31 -12.987654e12 â¦. I see that Pharoâs Float is VWâs Double. So then I just need to be able to serialize APF. â¦. FIFloatType subclass: #FFIFloat128 instanceVariableNames: '' classVariableNames: '' poolDictionaries: '' category: 'UnifiedFFI-Types' I'm a 128bits (cuadruple precision) float. It is usually not used, but some compiler modes support it (__float128 in gcc) THIS IS NOT YET SUPPORTED â¦. The class above is also from the Pharo 7 image. This is the largest of the c-type FFIFloats. Any Float classes of this size and larger for the Smalltalk heap on 64-bit Pharo? Cheers, Shaping Le 6 nov. 2018 Ã 06:58, Shaping <shaping(a)uurda.org <mailto:shaping@uurda.org> > a Ã©crit : (Having domain problems recently. Please excuse this posting if you have seen it twice. I've not seen it appear yet on the list.) Can STON be extended to handle Doubles and ArbitraryPrecisionFloats? Shaping -----Original Message----- From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of David T. Lewis Sent: Wednesday, October 31, 2018 14:58 To: Pharo Development List <pharo-dev(a)lists.pharo.org <mailto:pharo-dev@lists.pharo.org> > Subject: Re: [Pharo-dev] [ANN] The STON Specification This is very clear and well written. Dave Hi, Since there can never be enough documentation I finally took some time to write a more formal description of STON as a data format. https://github.com/svenvc/ston/blob/master/ston-spec.md The idea is to let this stabilise a bit and to then update the two other documents describing STON, where necessary: https://github.com/svenvc/ston/blob/master/ston-paper.md https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuc cessfulBuild/artifact/book-result/STON/STON.html Also, the latest changes in STON have to make their way to the Pharo image as well. https://github.com/svenvc/ston All feedback is welcome. Sven -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org -- _,,,^..^,,,_ best, Eliot

1 0

Anyone else seen crashes like these ?
by Sven Van Caekenberghe Nov. 13, 2018

Nov. 13, 2018

Hi, I run Pharo 7 64-bit on a macOS laptop, where the images are kept running across sleep/wake cycles. For many weeks, it often happens that an image crashes before/after such a sleep/wakeup (not all the time, just regularly). Here is a crash dump from today (fresh image/vm from WE, nothing special loaded). Related to scheduling ? Event handling ?

5 8

[Pharo 7.0-dev] Build #1381: 22609-When-we-separate-a-tab-from-the-Welcome-window-you-can-not-close-it
by ci-pharo-ci-jenkins2＠inria.fr Nov. 12, 2018

Nov. 12, 2018

There is a new Pharo build available! The status of the build #1381 was: FAILURE. The Pull Request #1973 was integrated: "22609-When-we-separate-a-tab-from-the-Welcome-window-you-can-not-close-it" Pull request url: https://github.com/pharo-project/pharo/pull/1973 Issue Url: https://pharo.fogbugz.com/f/cases/22609 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1380: 22206-NautilusRefactoring-should-have-the-tests-in-a-separate-package
by ci-pharo-ci-jenkins2＠inria.fr Nov. 12, 2018

Nov. 12, 2018

There is a new Pharo build available! The status of the build #1380 was: FAILURE. The Pull Request #1974 was integrated: "22206-NautilusRefactoring-should-have-the-tests-in-a-separate-package" Pull request url: https://github.com/pharo-project/pharo/pull/1974 Issue Url: https://pharo.fogbugz.com/f/cases/22206 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1379: Added Interval>>sort: method that raises a "you can not sort an interâ¦
by ci-pharo-ci-jenkins2＠inria.fr Nov. 12, 2018

Nov. 12, 2018

There is a new Pharo build available! The status of the build #1379 was: SUCCESS. The Pull Request #1922 was integrated: "Added Interval>>sort: method that raises a "you can not sort an interâ¦" Pull request url: https://github.com/pharo-project/pharo/pull/1922 Issue Url: https://pharo.fogbugz.com/f/cases/22588 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1378: 22651-URL-color-is-hardcoded-in-welcome-window
by ci-pharo-ci-jenkins2＠inria.fr Nov. 12, 2018

Nov. 12, 2018

There is a new Pharo build available! The status of the build #1378 was: FAILURE. The Pull Request #1972 was integrated: "22651-URL-color-is-hardcoded-in-welcome-window" Pull request url: https://github.com/pharo-project/pharo/pull/1972 Issue Url: https://pharo.fogbugz.com/f/cases/22651 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1377: 22649-Remove DelaySpinScheduler
by ci-pharo-ci-jenkins2＠inria.fr Nov. 12, 2018

Nov. 12, 2018

There is a new Pharo build available! The status of the build #1377 was: SUCCESS. The Pull Request #1964 was integrated: "22649-Remove DelaySpinScheduler" Pull request url: https://github.com/pharo-project/pharo/pull/1964 Issue Url: https://pharo.fogbugz.com/f/cases/22649 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Esteban's ChangeLog week of 5 November 2018
by estebanlm＠gmail.com Nov. 12, 2018

Nov. 12, 2018

Hello! This is my weekly ChangeLog, from 5 November 2018 to 11 November 2018. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=5/11/2018&to=11/11/2018 ChangeLog ========= 5 November 2018: ---------------- * I just [announced](http://forum.world.st/ANN-Pharo-v7-0-0-rc1-released-td5088221.html) Pharo v7.0.0-rc1. Now the real work begins... :P * I worked on [case: 22628](https://pharo.fogbugz.com/f/cases/22628): merge latest FFI-Kernel changes. Thing is, now there is some overlapping between FFI-Kernel and UnifiedFFI, because they changed it in some things we already solved in UFFI, but well... we will have to see this in the future :) * I made a small PR to add a fix that Eliot contributed to it: [https://github.com/pharo-vcs/tonel/pull/60](https://github.com/pharo-vcs/to… . Is an error that happens when a snapshot contains *only* method extensions. cheers! Esteban

1 0

[Pharo 7.0-dev] Build #1376: 22656-Improve-ImageReadWriter-comments
by ci-pharo-ci-jenkins2＠inria.fr Nov. 11, 2018

Nov. 11, 2018

There is a new Pharo build available! The status of the build #1376 was: SUCCESS. The Pull Request #1970 was integrated: "22656-Improve-ImageReadWriter-comments" Pull request url: https://github.com/pharo-project/pharo/pull/1970 Issue Url: https://pharo.fogbugz.com/f/cases/22656 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Streams and FileDialog in Pharo 6 and 7
by Torsten Bergmann Nov. 11, 2018

Nov. 11, 2018

Hi, A question to those who worked on the new streams for Pharo 7: In PHARO 6 I used the following expression to open a file dialog and let the user choose a binary file: s := UITheme builder fileOpen: 'Choose a file' extensions: #('exe'). This returned - either nil (when file dialog was canceled) - a "MultiByteFileStream" instance when a file was selected The MultiByteFileStream instance already had the name of the file (= full path) and I was able to query it for further use: s := UITheme builder fileOpen: 'Choose a file' extensions: #('exe'). s name inspect (for instance to display which file is processed in a window by showing the full path) Now in PHARO 7 same expression returns an instance of ZnCharacterReadStream (as MultiByteFileStream is deprecated): s := UITheme builder fileOpen: 'Choose a file' extensions: #('exe'). and ZnCharacterReadStream does not understand #name - and in fact the info about the name is totally lost/not available. To me this looks missing/broken. So what is the recommended way in Pharo 7 to open a file dialog, let the use choose a file and get a file stream but also the name? IMHO this is either broken or missing... Thanks T.

6 10

[Pharo 7.0-dev] Build #1375: 22561-uFFI-should-not-require-decompilation-to-extract-sender-selector
by ci-pharo-ci-jenkins2＠inria.fr Nov. 10, 2018

Nov. 10, 2018

There is a new Pharo build available! The status of the build #1375 was: SUCCESS. The Pull Request #1897 was integrated: "22561-uFFI-should-not-require-decompilation-to-extract-sender-selector" Pull request url: https://github.com/pharo-project/pharo/pull/1897 Issue Url: https://pharo.fogbugz.com/f/cases/22561 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

WELL512 PRNG
by Sven Van Caekenberghe Nov. 9, 2018

Nov. 9, 2018

Hi, By accident I came across a pseudo random number generator that I never heard off before. It is supposed to be pretty good and had a very simple implementation. So I ported it to Pharo. <class comment> I am RandomWELL512, a random number generator. I use the PRNG (Pseudo Randon Number Generator) WELL (Well equidistributed long-period linear) with a 512 bit state. https://en.wikipedia.org/wiki/Well_equidistributed_long-period_linear http://www.iro.umontreal.ca/~lecuyer/myftp/papers/wellrng.pdf Implementation algorithm (See #nextUInt32) http://www.lomont.org/Math/Papers/2008/Lomont_PRNG_2008.pdf (Chris Lomont, www.lomont.org) Usage RandomWELL512 new in: [ :r | (1 to: 10) collect: [ :i | r nextUInt32 ] ]. RandomWELL512 new useUnixRandomGeneratorSeed; in: [ :r | (1 to: 10) collect: [ :i | r next ] ]. RandomWELL512 new in: [ :r | (1 to: 10) collect: [ :i | r nextInt: 1000 ] ]. RandomWELL512 new in: [ :random | | count all | random useUnixRandomGeneratorSeed. count := 1024 * 1024. all := Array new: count streamContents: [ :out | count timesRepeat: [ out nextPut: random next ] ]. { all min. all max. all average. all stdev } ]. [ RandomWELL512 new in: [ :random | 1 to: 1e6 do: [ :i | random next ] ] ] timeToRun. Note that you should create one instance, seed it properly, and keep using it. </class comment> It is acceptably fast, generating 1M [0,1) Floats in about 0.1s. I compared the output with a fixed initial state to the C code that I started from and I got the same numbers. Maybe some people find this interesting. I attached a file out. Sven

4 4

Action list for Pharo 70 release
by Stephane Ducasse Nov. 9, 2018

Nov. 9, 2018

Hi The team got a meeting about the final points to address before the release. Here is the summary of action points one and to do to the meeting next month. Done: Release - version info from tag Calypso - Traits (In calypso repository, not yet in Pharo) - Extensions (In calypso repository, not yet in Pharo) Doing: Release - File name / repository should take tag information => Esteban - Launcher should be updated automatically without having to touch it => Christophe - Update Zeronconf => Esteban + Vincent Calypso - Review refactorings => Vincent - Integrated Spotter shortcut => Esteban - Selection/Navigation => ??? Selection glitches (see why sometimes focus is broken and cmd+W is wrong) => Pavel FFI recompilation of Structures => Guille Backport Unicode Support from Launcher => Guille FT2 bug, update Freetype library => Esteban Cleaning pharo-scripts repository => ??? Start preparing changes log => Marcus >From what I understood the window 64 bits is to unstable to be proposed. Stef

1 0