- Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #1003: 22035-Delete-PNGReadWriter-classcreateAFormFrom
by ci-pharo-ci-jenkins2＠inria.fr June 3, 2018

June 3, 2018

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

1 0

rewrite rule help
by Eliot Miranda June 2, 2018

June 2, 2018

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

2 1

[Pharo 7.0-dev] Build #1002: 22038-Replace-World-Menu-by-Menu-bar
by ci-pharo-ci-jenkins2＠inria.fr June 1, 2018

June 1, 2018

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…

1 0

[Pharo 7.0-dev] Build #1001: 21215-FileReference--nextVersion-should-works-on-folders-too
by ci-pharo-ci-jenkins2＠inria.fr June 1, 2018

June 1, 2018

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…

1 0

[Pharo 7.0-dev] Build #1000: 14063-clean-up-definitionForNautilus
by ci-pharo-ci-jenkins2＠inria.fr June 1, 2018

June 1, 2018

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…

1 0

[Pharo 7.0-dev] Build #999: 22036-ClassBuilderWarning--Error--Hierarchy----clean-some-unused-
by ci-pharo-ci-jenkins2＠inria.fr June 1, 2018

June 1, 2018

There is a new Pharo build available! The status of the build #999 was: FAILURE. The Pull Request #1469 was integrated: "22036-ClassBuilderWarning--Error--Hierarchy----clean-some-unused-" Pull request url: https://github.com/pharo-project/pharo/pull/1469 Issue Url: https://pharo.fogbugz.com/f/cases/22036 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #998: 20324-Handy-file-automatic-numbering
by ci-pharo-ci-jenkins2＠inria.fr June 1, 2018

June 1, 2018

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

1 0

[Pharo 7.0-dev] Build #996: 20324-Handy-file-automatic-numbering
by ci-pharo-ci-jenkins2＠inria.fr June 1, 2018

June 1, 2018

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

1 0

[Pharo 7.0-dev] Build #995: 20324-Handy-file-automatic-numbering
by ci-pharo-ci-jenkins2＠inria.fr June 1, 2018

June 1, 2018

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

1 0

curious behaviour - disappearing variable scope
by Ben Coman June 1, 2018

June 1, 2018

I'm curious about the following behaviour... "In Playground, first evaluate..." s := Semaphore new. [ [ s wait. Transcript crShow: 'x' ] whileTrue ] fork. "then later..." s signal. ==> 'x' is seen in Transcript but then an error pops up "#wait was sent to nil" So... 's' *was* valid and then its not? cheers -ben

2 3