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

Re: [Pharo-dev] Updated syntax postcard

by phil＠highoctane.be

I would love to see: select: thenCollect: Or at lease collect: since this is where we do have more power. do: yeah but not that inspiring. Phil On Fri, Jun 1, 2018, 12:57 Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > Hi, > > for the Wikipedia article I prepared an updated version of Phar syntax > postcard: > > > https://upload.wikimedia.org/wikipedia/commons/a/a7/Pharo_syntax_postcard.s… > > Cheers, > -- Pavel >

June 2, 2018

Re: [Pharo-dev] Updated syntax postcard

by phil＠highoctane.be

Super light gray on white is hard to see for me (and I guess other vision challenged people). Other than that, yes, definitely great. Phil On Fri, Jun 1, 2018, 13:21 Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > This is a really nice overview! > > Two "p" characters are rendered weirdly for me (Chrome 66), but the > remaining "p"s are good. The zoom level doesn't matter. > > > Could you please include keyword message with multiple parameters? From my > teaching this always confuses people. :) > > And if you want it to be really complete (maybe you've just missed these): > annotation for block (only block parameter is annotated), and mayhaps > definition of unary/binary message? > > Peter > > On Fri, Jun 1, 2018 at 12:56 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> > wrote: > >> Hi, >> >> for the Wikipedia article I prepared an updated version of Phar syntax >> postcard: >> >> >> https://upload.wikimedia.org/wikipedia/commons/a/a7/Pharo_syntax_postcard.s… >> >> Cheers, >> -- Pavel >> > >

June 2, 2018

Re: [Pharo-dev] Updated syntax postcard

by Tudor Girba

Excellent work! Doru > On Jun 1, 2018, at 11:56 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > Thanks to all for feedback. Updated. > > https://upload.wikimedia.org/wikipedia/commons/a/a7/Pharo_syntax_postcard.s… > > Related can be found here: https://github.com/pavel-krivanek/pharoMaterials/tree/master/postcard > > -- Pavel > > 2018-06-01 13:20 GMT+02:00 Peter UhnÃ¡k <i.uhnak(a)gmail.com>: > This is a really nice overview! > > Two "p" characters are rendered weirdly for me (Chrome 66), but the remaining "p"s are good. The zoom level doesn't matter. > > <image.png> > Could you please include keyword message with multiple parameters? From my teaching this always confuses people. :) > > And if you want it to be really complete (maybe you've just missed these): annotation for block (only block parameter is annotated), and mayhaps definition of unary/binary message? > > Peter > > On Fri, Jun 1, 2018 at 12:56 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > Hi, > > for the Wikipedia article I prepared an updated version of Phar syntax postcard: > > https://upload.wikimedia.org/wikipedia/commons/a/a7/Pharo_syntax_postcard.s… > > Cheers, > -- Pavel > > -- www.tudorgirba.com www.feenk.com "We cannot reach the flow of things unless we let go."

June 2, 2018

Iceberg "Duplicated project!"

by Martin McClure

On a Pharo7, Linux, from yesterday: Build information: Pharo-7.0+alpha.build.994.sha.6b52ae62b755d8778fa0b5a4ac53b39b6c107dc9 (32 Bit) During an Iceberg load of a Metacello baseline, I get a dialog Duplicated project! There is already a project "OSSubprocess" in this installation. It's true that I do have a Git clone of OSSubprocess in my pharo-local/iceberg directory, since this is the second image I've loaded into, but before it's always just used the already-cloned repo rather than trying to create a new one. Any ideas on what the correct behavior currently is (for the system, and for me) at this point? Thanks, -Martin

June 2, 2018

Re: [Pharo-dev] rewrite rule help

by John Brant

On Jun 1, 2018, at 8:25 PM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > Hi All, > > can anyone tell me why the following rules > > rules > replace: '``@statements. interpreterProxy pop: ``@const. interpreterProxy pushInteger: ``@integer' > with: '``@statements. interpreterProxy methodReturnInteger: ``@integer'; > replace: '``@statements. interpreterProxy pop: ``@const. ^interpreterProxy pushInteger: ``@integer' > with: '``@statements. ^interpreterProxy methodReturnInteger: ``@integer'. > You need a â.â in your ``@statements (i.e., ``@.statements). The ``@ prefix matches any node, but ``@. will match a list of statements (0 or more). Currently, you are only matching sequence nodes with exactly 3 statements. You also need to add some temps in case the sequence node has temps: | `@temps | ``@.statements. interpreterProxy pop: ``@const. ^interpreterProxy pushInteger: ``@integer -> | `@temps | ``@.statements. ^interpreterProxy methodReturnInteger: ``@integer John Brant

June 2, 2018

rewrite rule help

by Eliot Miranda

Hi All, can anyone tell me why the following rules rules replace: '``@statements. interpreterProxy pop: ``@const. interpreterProxy pushInteger: ``@integer' with: '``@statements. interpreterProxy methodReturnInteger: ``@integer'; replace: '``@statements. interpreterProxy pop: ``@const. ^interpreterProxy pushInteger: ``@integer' with: '``@statements. ^interpreterProxy methodReturnInteger: ``@integer'. or rules replace: 'interpreterProxy pop: ``@const. interpreterProxy pushInteger: ``@integer' with: 'interpreterProxy methodReturnInteger: ``@integer'; replace: 'interpreterProxy pop: ``@const. ^interpreterProxy pushInteger: ``@integer' with: '^interpreterProxy methodReturnInteger: ``@integer'. do edit this primitiveRendererVersion <export: true> interpreterProxy methodArgumentCount = 0 ifFalse:[^interpreterProxy primitiveFail]. interpreterProxy pop: 1. ^interpreterProxy pushInteger: 1. to primitiveRendererVersion <export: true> interpreterProxy methodArgumentCount = 0 ifFalse: [ ^ interpreterProxy primitiveFail ]. ^ interpreterProxy methodReturnInteger: 1 but not this? primitiveTextureDepth | handle result renderer | <export: true> interpreterProxy methodArgumentCount = 2 ifFalse:[^interpreterProxy primitiveFail]. handle := interpreterProxy stackIntegerValue: 0. renderer := interpreterProxy stackIntegerValue: 1. interpreterProxy failed ifTrue:[^nil]. result := self cCode:'b3dxActualTextureDepth(renderer, handle)' inSmalltalk:[-1]. result < 0 ifTrue:[^interpreterProxy primitiveFail]. interpreterProxy pop: 3. ^interpreterProxy pushInteger: result. _,,,^..^,,,_ best, Eliot

June 2, 2018

Re: [Pharo-dev] Updated syntax postcard

by Pavel Krivanek

Thanks to all for feedback. Updated. https://upload.wikimedia.org/wikipedia/commons/a/a7/Pharo_syntax_postcard.s… Related can be found here: https://github.com/pavel-krivanek/pharoMaterials/tree/master/postcard -- Pavel 2018-06-01 13:20 GMT+02:00 Peter UhnÃ¡k <i.uhnak(a)gmail.com>: > This is a really nice overview! > > Two "p" characters are rendered weirdly for me (Chrome 66), but the > remaining "p"s are good. The zoom level doesn't matter. > > > Could you please include keyword message with multiple parameters? From my > teaching this always confuses people. :) > > And if you want it to be really complete (maybe you've just missed these): > annotation for block (only block parameter is annotated), and mayhaps > definition of unary/binary message? > > Peter > > On Fri, Jun 1, 2018 at 12:56 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> > wrote: > >> Hi, >> >> for the Wikipedia article I prepared an updated version of Phar syntax >> postcard: >> >> https://upload.wikimedia.org/wikipedia/commons/a/a7/Pharo_sy >> ntax_postcard.svg >> >> Cheers, >> -- Pavel >> > >

June 1, 2018

[Pharo 7.0-dev] Build #1002: 22038-Replace-World-Menu-by-Menu-bar

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

There is a new Pharo build available! The status of the build #1002 was: SUCCESS. The Pull Request #1470 was integrated: "22038-Replace-World-Menu-by-Menu-bar" Pull request url: https://github.com/pharo-project/pharo/pull/1470 Issue Url: https://pharo.fogbugz.com/f/cases/22038 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 1, 2018

[Pharo 7.0-dev] Build #1001: 21215-FileReference--nextVersion-should-works-on-folders-too

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

There is a new Pharo build available! The status of the build #1001 was: SUCCESS. The Pull Request #1433 was integrated: "21215-FileReference--nextVersion-should-works-on-folders-too" Pull request url: https://github.com/pharo-project/pharo/pull/1433 Issue Url: https://pharo.fogbugz.com/f/cases/21215 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 1, 2018

[Pharo 7.0-dev] Build #1000: 14063-clean-up-definitionForNautilus

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

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

June 1, 2018