- Pharo-dev - lists.pharo.org

[Pharo 8.0] Build #273: 3338-Slots-isSpecial-cleanup-part-2
by ci-pharo-ci-jenkins2＠inria.fr May 15, 2019

May 15, 2019

There is a new Pharo build available! The status of the build #273 was: SUCCESS. The Pull Request #3339 was integrated: "3338-Slots-isSpecial-cleanup-part-2" Pull request url: https://github.com/pharo-project/pharo/pull/3339 Issue Url: https://github.com/pharo-project/pharo/issues/3338 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Some more effort to make Slang and VMMaker work on Pharo [for review]
by Guillermo Polito May 15, 2019

May 15, 2019

Hi all, Just to keep everyone informed, last week Iâve spent a couple of days making slang work on Pharo again, based on the initial effort of Eliot. The summary of what I did is: - we can generate, compile and run a stack vm - we can generate, compile and run a cog vm - for this, Iâve done a couple of patches to VMMaker - the ones specific to Pharo has been pushed - the ones that touch cross dialect code are still in review (I think) To do this work - I had to review the AST-to-AST transformation, checking the output, comparing it to what squeak does and so on... - Iâve written several unit tests to ensure that future migrations are easier to do - Iâve introduced several compatibility classes/methods related to PackageInfo, Time and so onâ¦ Cheers, Guille > Inicio del mensaje reenviado: > > De: Guillermo Polito <guillermopolito(a)gmail.com> > Asunto: Re: [Vm-dev] Some more effort to make Slang and VMMaker work on Pharo [for review] > Fecha: 9 de mayo de 2019, 17:48:03 CEST > Para: Open Smalltalk Virtual Machine Development Discussion <vm-dev(a)lists.squeakfoundation.org> > > I've decided for the moment to put the tests in the PharoCompatibility package, since they are too close of Pharo's AST. > I've tried to make them work in squeak but I've found too many incompatibilities in the AST and some in the collections that would make the tests too verbose to make them reusable... > Maybe we can do an iteration afterwards. > > Cheers, > Guille > > On Thu, May 9, 2019 at 5:21 PM Guillermo Polito <guillermopolito(a)gmail.com <mailto:guillermopolito@gmail.com>> wrote: > Hi all, > > On Wed, May 8, 2019 at 2:17 AM David T. Lewis <lewis(a)mail.msen.com <mailto:lewis@mail.msen.com>> wrote: > > > On Tue, May 07, 2019 at 03:36:32PM -0700, Eliot Miranda wrote: > > > In VMMaker.oscog-GAP.2533 I would prefer to see printString instead of > > asString. asString is a horrible hack. printString says what we mean. > > Sure. I've submitted another version to the inbox: > > Name: VMMaker.oscog-GAP.2534 > Author: GAP > Time: 9 May 2019, 5:12:22.055089 pm > UUID: cd6aae16-6f20-4ddb-9328-64b19b413cb1 > Ancestors: VMMaker.oscog-eem.2532 > > Convert numeric constants to strings for concatenation using #printString. > Required for Pharo compatibility, where the arguments of concatenation are not automatically coerced to strings. > > > ==== Patch 1 ==== > > > Name: VMMaker.oscog-GAP.2533 > > > Author: GAP > > > Time: 7 May 2019, 10:57:16.034354 am > > > UUID: 3209319f-60f3-4586-8d03-cfac3c9fddee > > > Ancestors: VMMaker.oscog-eem.2532 > > > > > > Convert numeric constants to strings for concatenation. > > > Required for Pharo compatibility, where the arguments of concatenation are > > > not automatically coerced to strings. > > > > > > > I trust you on these. I'm not really in a position to test this out right > > now. I suggest you push the VMMakerCompatibilityForPharo6 packages to > > VMMaker as soon as you'd like. You can write VMMaker right? > > > > +1 > > Guille, if you want commit access to the repo, you can make an account > on source.squeak.org <http://source.squeak.org/> and I'll add you the the VMMaker project. Or if > it's easier, just say which packages you are ready to move and either > I or Eliot (or any of the others with commit access) will move it to > VMMaker for you. > > I note that VMMaker.oscog-GAP.2533 package is part of the main > VMMaker.oscog package. If you need to have that tested on Squeak I > can probably do that for you within the next couple of days if no > one else gets to it first. > > Well, the change I did in that package was fairly small, and I'm using squeak to generate also some parts of the VM to compare to what I generate from Pharo. > So, I'd say I've tried it myself already. > > For the Pharo specific package, I've already uploaded it to the VMMaker repository. > I had already rights to do it :). > > Name: VMMakerCompatibilityForPharo6-GuillermoPolito.11 > Author: GuillermoPolito > Time: 9 May 2019, 5:15:50.00473 pm > UUID: e1a685a9-d744-0d00-b3c1-ad600f1a7e9a > Ancestors: VMMakerCompatibilityForPharo6-GuillermoPolito.10 > > With these changes I can already compile and run Cog and almost all tests pass :) > > > > I have also a couple dozen tests about AST translation and C generation, mainly about those parts that are covered differently between Pharo's and Squeak's ASTs. > Would you like that I push them inside the VMMaker package or make a separate package? > > Thanks! > Guille > > > -- > > Guille Polito > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > CRIStAL - UMR 9189 > French National Center for Scientific Research - http://www.cnrs.fr <http://www.cnrs.fr/> > > Web: http://guillep.github.io <http://guillep.github.io/> > Phone: +33 06 52 70 66 13

7 10

[Pharo 8.0] Build #272: 3342-Integrate-Iceberg-170
by ci-pharo-ci-jenkins2＠inria.fr May 14, 2019

May 14, 2019

There is a new Pharo build available! The status of the build #272 was: FAILURE. The Pull Request #3344 was integrated: "3342-Integrate-Iceberg-170" Pull request url: https://github.com/pharo-project/pharo/pull/3344 Issue Url: https://github.com/pharo-project/pharo/issues/3342 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Metacello/Iceberg detached head of cascade loaded requirements
by Ben Coman May 14, 2019

May 14, 2019

I have a query about "Detached HEAD" status after a Metacello/Iceberg cascade load of required packages. Starting with the general questions... Is that a common status for this scenario? How to leave the status looking good as "Up to date"? Here is a case example... To avoid the a Filetree repo "filename too long" error on Windows, I pre-cloned the repo to specify s shorter path name... Repositories > Add > Clone from github.com Owner: dionisiydk Project name: Mocketry Local directory: C:\Temp\Mocketry Protocol: SSH Then in Playground evaluated... Metacello new baseline: 'Mocketry'; repository: 'github://dionisiydk/Mocketry'; load This cascade loaded Ghost and StateSpecs repos leaving them with a status of "Detached HEAD". What does this mean? And how to have these load cleanly so they are left "Up to date" ? To ease others testing on Windows, I forked the repo and converted to Tonel, so the same result comes by just evaluating.... Metacello new baseline: 'Mocketry'; repository: 'github://bencoman/Mocketry'; load cheers -ben P.S. I've issued a PR upstream for the Tonel conversion.

3 3

[Pharo 8.0] Build #271: 2272-Spec-Model-classes-still-contains-extensions
by ci-pharo-ci-jenkins2＠inria.fr May 14, 2019

May 14, 2019

There is a new Pharo build available! The status of the build #271 was: SUCCESS. The Pull Request #3346 was integrated: "2272-Spec-Model-classes-still-contains-extensions" Pull request url: https://github.com/pharo-project/pharo/pull/3346 Issue Url: https://github.com/pharo-project/pharo/issues/2272 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Need help to help newbies on discord mooc channel
by ducasse May 13, 2019

May 13, 2019

1 0

[Pharo 8.0] Build #270: 3229-RubAnnotationDisplayer-fontToUse-has-a-trait-conflict
by ci-pharo-ci-jenkins2＠inria.fr May 13, 2019

May 13, 2019

There is a new Pharo build available! The status of the build #270 was: FAILURE. The Pull Request #3259 was integrated: "3229-RubAnnotationDisplayer-fontToUse-has-a-trait-conflict" Pull request url: https://github.com/pharo-project/pharo/pull/3259 Issue Url: https://github.com/pharo-project/pharo/issues/3229 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

ESUG 2019 - Call for IWST
by ducasse May 13, 2019

May 13, 2019

Here is the announce for the IWST19 â International Workshop on Smalltalk Technologies Cologne, Germany; August 27-29th, 2019 More information at: https://esug.github.io/2019-Conference/cfpIWST2019.html On behalf of the pc chairs

1 0

May 13, 2019

Please distribute the following call The ESUG board is pleased to announce that the 27th ESUG conference/summer-school will be held in Cologne, Germany 26-30 August 2019; with Camp Smalltalk 24-25 August 2019. The conference is co-organized by ZWEIDENKER. More information at: https://esug.github.io/2019-Conference/call2019.html -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr http://www.synectique.eu / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

1 0

[Pharo 8.0] Build #269: 3323-V2-traits-definition-message-should-use-package-instead-of-category
by ci-pharo-ci-jenkins2＠inria.fr May 12, 2019

May 12, 2019

There is a new Pharo build available! The status of the build #269 was: SUCCESS. The Pull Request #3331 was integrated: "3323-V2-traits-definition-message-should-use-package-instead-of-category" Pull request url: https://github.com/pharo-project/pharo/pull/3331 Issue Url: https://github.com/pharo-project/pharo/issues/3323 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0