November 2018 - Pharo-users

Commit dates when migrating repos to github

by Ben Coman

Just a quick note sharing something I learnt recently. When migrating MCZ repos to git, set the commit-date of the first empty commit back past the first MCZ date. https://leewc.com/articles/making-past-git-commits/ After the MCZs have been exported, check the commit-date matches the author date. $ git log --format=fuller or otherwise force it so... $ git filter-branch --env-filter 'export GIT_COMMITTER_DATE="$GIT_AUTHOR_DATE"' cheers -ben

Nov. 20, 2018

glamorous toolkit alpha.3

by Tudor Girba

Hi, Another month has swooshed and now itâs time for Glamorous Toolkit alpha.3: https://feenk.com/gt The key things that changed are as follows: - We rewrote Documenter. This was challenge, but the results are more than worth it. One visible thing is that now the previews get cached, and as a consequence we can actually work inside the document. But, perhaps the more impactful thing is that we can now toggle the visibility of Pillar markup. We think it significantly improves the experience and consequently, the value of the live documents. - We advanced the work on the method Coder. To explore the boundaries, we reimagined the extract method refactoring. Thatâs : https://twitter.com/feenkcom/status/1064823381407748096 - We enhanced the navigation in Playground / Inspector: https://twitter.com/feenkcom/status/1064823381407748096 A more complete list of issues we addressed is found here: https://github.com/feenkcom/gtoolkit/milestone/1?closed=1 Have fun, The feenk team -- www.feenk.com âHow do you feenk today?"

Nov. 20, 2018

Re: [Pharo-users] Reify RBLiteralNode and RBBlockNode args/return with MetaLink?

by Marcus Denker

I already have a fix for i) i) How do I reify the value of an RB(Valuel|Literal|LiteralValue)Node? I will commit it later today. Marcus > On 19 Nov 2018, at 22:14, Manuel Leuenberger <leuenberger(a)inf.unibe.ch> wrote: > > Thanks for picking this up into the backlog. I am not blocked if I don't have them, I was just curious. I am quite intrigued with the idea of reyfing the runtime semantics, this opens a whole lot of opportunities for tools based on dynamic data. > > On Nov 19, 2018 17:40, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Hi, > > Thanks! I will check all of themâ¦ it might very well be that they are not implemented / there are bugs. > > I will add them to the bug list. > > (the problem is that each of them takes effortâ¦ write test, stare at byte-codeâ¦ so it will take some time) > > On 19 Nov 2018, at 09:30, Manuel Leuenberger <leuenberger(a)inf.unibe.ch <mailto:leuenberger@inf.unibe.ch>> wrote: > > Hi, > > I am currently playing with MetaLinks in Pharo 7 and stumbled upon some issues. For example, I found that instrumenting message sends may break compilation (see https://pharo.fogbugz.com/f/cases/22681/Metalink-on-message-may-break-compi… <https://pharo.fogbugz.com/f/cases/22681/Metalink-on-message-may-break-compi…>). Two other issues also arised: > > i) How do I reify the value of an RB(Valuel|Literal|LiteralValue)Node? RFValueReification does not work, and there is no reification for literal, value, or literal value nodes. > ii) How do I reify arguments and results of blocks? I tried reify context for the block body #before and value for #after block "last", but I often run into the problem of no reification for literals. > iii) How are cascaded message sends reified? Am I supposed to instrument the cascade node or the individual message sends? > > I am grateful for any pointers towards a solution. BTW, Marcus' lecture slides give a great intro to metalinks (http://marcusdenker.de/talks/18LectureMetaLinks/MetaLinks.pdf <http://marcusdenker.de/talks/18LectureMetaLinks/MetaLinks.pdf>). > > Cheers, > Manuel > > >

Nov. 20, 2018

Re: [Pharo-users] Reify RBLiteralNode and RBBlockNode args/return with MetaLink?

by Manuel Leuenberger

Nov. 19, 2018

Re: [Pharo-users] Pharo on Linux

by Hans-Martin

One thing that I've learned to appreciate quickly is the pharo launcher. It takes care of downloading everything you need (of course, it won't set up a 32-bit environment in a 64-bit Linux for you, that must be done manually). Used it in Linux and Windows environments with good success, it's really the simplest way of quickly comparing different without much hassle. Cheers, Hans-Martin -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Nov. 19, 2018

Re: [Pharo-users] Pharo 7 Loading stops at Seaside-Pharo-JSON-Jo....5

by Sven Van Caekenberghe

You need to tell us how are loading Seaside, exactly. Using Metacello new baseline:'Seaside3'; repository: 'github://SeasideSt/Seaside:master/repository'; load. ? The dev build on P7 passes it seems https://travis-ci.org/SeasideSt/Seaside > On 19 Nov 2018, at 17:34, Sanjay Minni <sm(a)planage.com> wrote: > > How do I proceed from here ? > > (Pharo 7 32 bit on Win 10) > > whle installing a developed package - Loading stops at > Seaside-Pharo-JSON-Jo....5 > > This package depends on the following classes: > WAPharoEncoder > You must resolve these dependencies before you will be able to load these > definitions: > WAPharoJsonEncoder > WAPharoJsonEncoder>>#delegateOn: > WAPharoJsonEncoder>>#initialize > WAPharoJsonEncoder>>#initializeJsonTable > > > > > > ----- > --- > Regards, Sanjay > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

Nov. 19, 2018

Re: [Pharo-users] [Pharo-dev] Pharo 7 speed compared to VW

by Eliot Miranda

Hi Shaping, On Mon, Nov 19, 2018 at 5:04 AM Shaping <shaping(a)uurda.org> wrote: > (Second try in 6 days. Does anyone have recent performance data for Pharo > 7 relative to VW 7.10 or later?) > I don't have access to recent vnc versions beyond 7.7. If you have access perhaps you could run the computer language shootout benchmarks ( https://benchmarksgame-team.pages.debian.net/benchmarksgame/faster/smalltal…) and report the results. > > > *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 <shaping(a)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> 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> 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 > <pharo-dev-bounces(a)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> > 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 > -- _,,,^..^,,,_ best, Eliot

Nov. 19, 2018

Re: [Pharo-users] Reify RBLiteralNode and RBBlockNode args/return with MetaLink?

by Marcus Denker

Hi, Thanks! I will check all of themâ¦ it might very well be that they are not implemented / there are bugs. I will add them to the bug list. (the problem is that each of them takes effortâ¦ write test, stare at byte-codeâ¦ so it will take some time) > On 19 Nov 2018, at 09:30, Manuel Leuenberger <leuenberger(a)inf.unibe.ch> wrote: > > Hi, > > I am currently playing with MetaLinks in Pharo 7 and stumbled upon some issues. For example, I found that instrumenting message sends may break compilation (see https://pharo.fogbugz.com/f/cases/22681/Metalink-on-message-may-break-compi… <https://pharo.fogbugz.com/f/cases/22681/Metalink-on-message-may-break-compi…>). Two other issues also arised: > > i) How do I reify the value of an RB(Valuel|Literal|LiteralValue)Node? RFValueReification does not work, and there is no reification for literal, value, or literal value nodes. > ii) How do I reify arguments and results of blocks? I tried reify context for the block body #before and value for #after block "last", but I often run into the problem of no reification for literals. > iii) How are cascaded message sends reified? Am I supposed to instrument the cascade node or the individual message sends? > > I am grateful for any pointers towards a solution. BTW, Marcus' lecture slides give a great intro to metalinks (http://marcusdenker.de/talks/18LectureMetaLinks/MetaLinks.pdf <http://marcusdenker.de/talks/18LectureMetaLinks/MetaLinks.pdf>). > > Cheers, > Manuel >

Nov. 19, 2018

Pharo 7 Loading stops at Seaside-Pharo-JSON-Jo....5

by Sanjay Minni

How do I proceed from here ? (Pharo 7 32 bit on Win 10) whle installing a developed package - Loading stops at Seaside-Pharo-JSON-Jo....5 This package depends on the following classes: WAPharoEncoder You must resolve these dependencies before you will be able to load these definitions: WAPharoJsonEncoder WAPharoJsonEncoder>>#delegateOn: WAPharoJsonEncoder>>#initialize WAPharoJsonEncoder>>#initializeJsonTable ----- --- Regards, Sanjay -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Nov. 19, 2018

Iceberg documentation, tutorial, video

by nacho

Hi! I'm trying to learn how to use Iceberg to switch my projects to GutHub. Are there any docs, tutorials o video showing how to configure, use, Iceberg? Thanks in advance! cheers nacho ----- Nacho Smalltalker apprentice. Buenos Aires, Argentina. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Nov. 19, 2018