[Pharo-dev] [Pharo 7.0-dev] Build #1382: 22558-FFICalloutresolveType-ignores-class-side-definition (v2)

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:

[Pharo-dev] [Pharo 7.0-dev] Build #1383: 22666-add-refications-for-operation-for-message-and-method

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:

[Pharo-dev] [Pharo 7.0-dev] Build #1384: 22667-operation-support-for-Global-var-read-and-more-tests

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:

[Pharo-dev] [Pharo 7.0-dev] Build #1385: 22662-IntervalTest-is-failing-on-64-bit-image

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

Re: [Pharo-dev] Better management of encoding of environment variables

I have to add also > Other Implementation Details > = > >- VM primitives returning paths Strings should be carefuly managed to >decode them, since they are actually C strings (so byte arrays) disguised >as ByteStrings. >- Similar changes had to be applied

[Pharo-dev] [Pharo 7.0-dev] Build #1390: 22659-generated-artifacts-should-have-the-version-tag (V2)

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:

[Pharo-dev] [Pharo 7.0-dev] Build #1391: 22659-generated-artifacts-should-have-the-version-tag (V3)

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:

[Pharo-dev] [Pharo 7.0-dev] Build #1389: 22659-generated-artifacts-should-have-the-version-tag (V2)

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:

Re: [Pharo-dev] Better management of encoding of environment variables

Hi all, Thanks Ben for reading. For those wanting a follow up, I've proposed this pull request: https://github.com/pharo-project/pharo/pull/1980. I'm still working on avoiding dependencies against UFFI, fixing one other test. This is however almost finished, and given that I had to adapt the

[Pharo-dev] [Pharo 7.0-dev] Build #1388: 22657-The-closing-of-a-window-using-a-keyboard-can-close-a-window-without-focus

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:

[Pharo-dev] [Pharo 7.0-dev] Build #1386: 22664-many-Opal-tests-are-failing-on-64-bit-image

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

[Pharo-dev] [Pharo 7.0-dev] Build #1387: 22665-NECContextTesttestReceiverTempVar-is-failing-in-64-bit-image

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:

Re: [Pharo-dev] How do I create a binary stream

Thanks you all for the discussion. We should improve the comment of File and probably the one of FileReference. Tx Sven for the improvement of the comment of ImageReadWriter. Good comments are so important! We underestimate their impact. S On Sun, Nov 11, 2018 at 2:10 PM Hilaire wrote: > > I am

[Pharo-dev] Debugger "Through" acting like "Into"

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

[Pharo-dev] [Pharo 7.0-dev] Build #1392: 22659-generated-artifacts-should-have-the-version-tag (V4)

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:

[Pharo-dev] [Pharo 7.0-dev] Build #1393: 22659-generated-artifacts-should-have-the-version-tag (V5)

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: