- Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #711: 21634-add-AST-and-Bytecode-view-to-RGMethodDefinition-inspector
by ci-pharo-ci-jenkins2＠inria.fr March 20, 2018

March 20, 2018

There is a new Pharo build available! The status of the build #711 was: SUCCESS. The Pull Request #1140 was integrated: "21634-add-AST-and-Bytecode-view-to-RGMethodDefinition-inspector" Pull request url: https://github.com/pharo-project/pharo/pull/1140 Issue Url: https://pharo.fogbugz.com/f/cases/21634 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #710: 21583 Cleanup EventSensorConstants
by ci-pharo-ci-jenkins2＠inria.fr March 20, 2018

March 20, 2018

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

1 0

[Pharo 7.0-dev] Build #709: 21627-CoverageDemo-should-have-open-method-on-class-side
by ci-pharo-ci-jenkins2＠inria.fr March 20, 2018

March 20, 2018

There is a new Pharo build available! The status of the build #709 was: SUCCESS. The Pull Request #1137 was integrated: "21627-CoverageDemo-should-have-open-method-on-class-side" Pull request url: https://github.com/pharo-project/pharo/pull/1137 Issue Url: https://pharo.fogbugz.com/f/cases/21627 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #708: 21629-Fix-inspect-MetaLink
by ci-pharo-ci-jenkins2＠inria.fr March 20, 2018

March 20, 2018

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

1 0

[Pharo 7.0-dev] Build #707: 21626-remove-localClassMethod-pragma-unused
by ci-pharo-ci-jenkins2＠inria.fr March 20, 2018

March 20, 2018

There is a new Pharo build available! The status of the build #707 was: SUCCESS. The Pull Request #1136 was integrated: "21626-remove-localClassMethod-pragma-unused" Pull request url: https://github.com/pharo-project/pharo/pull/1136 Issue Url: https://pharo.fogbugz.com/f/cases/21626 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #706: 21617-Better-implementation-of-package-comments
by ci-pharo-ci-jenkins2＠inria.fr March 20, 2018

March 20, 2018

There is a new Pharo build available! The status of the build #706 was: SUCCESS. The Pull Request #1131 was integrated: "21617-Better-implementation-of-package-comments" Pull request url: https://github.com/pharo-project/pharo/pull/1131 Issue Url: https://pharo.fogbugz.com/f/cases/21617 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #705: 21618-Saving-code-as-file-tree-is-broken
by ci-pharo-ci-jenkins2＠inria.fr March 20, 2018

March 20, 2018

There is a new Pharo build available! The status of the build #705 was: FAILURE. The Pull Request #1132 was integrated: "21618-Saving-code-as-file-tree-is-broken" Pull request url: https://github.com/pharo-project/pharo/pull/1132 Issue Url: https://pharo.fogbugz.com/f/cases/21618 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

2 1

New Files in Pharo - Migration Guide, How To's and examples
by Guillermo Polito March 20, 2018

March 20, 2018

Hi all, I've put some minutes summarizing the new APIs provided by the combination of the new File implementation and the Zn encoders. They all basically follow the decorator pattern to stack different responsibilities such as buffering, encoding, line ending convertions. Please, do not hesitate to give your feedback. Guille 1. Basic Files By default files are binary. Not buffered. (File named: 'name') readStream. (File named: 'name') readStreamDo: [ :stream | ... ]. (File named: 'name') writeStream. (File named: 'name') writeStreamDo: [ :stream | ... ]. 2. Encoding To add encoding, wrap a stream with a corresponding ZnCharacterRead/WriteStream. "Reading" utf8Encoded := ZnCharacterReadStream on: aBinaryStream encoding: 'utf8'. utf16Encoded := ZnCharacterReadStream on: aBinaryStream encoding: 'utf16'. "Writing" utf8Encoded := ZnCharacterWriteStream on: aBinaryStream encoding: 'utf8'. utf16Encoded := ZnCharacterWriteStream on: aBinaryStream encoding: 'utf16'. 3. Buffering To add buffering, wrap a stream with a corresponding ZnBufferedRead/WriteStream. bufferedReadStream := ZnBufferedReadStream on: aStream. bufferedWriteStream := ZnBufferedWriteStream on: aStream. It is in general better to buffer the reading on the binary file and apply the encoding on the buffer in memory than the other way around. See [file := Smalltalk sourcesFile fullName. (File named: file) readStreamDo: [ :binaryFile | (ZnCharacterReadStream on: (ZnBufferedReadStream on: binaryFile) encoding: 'utf8') upToEnd ]] timeToRun. "0:00:00:09.288" [file := Smalltalk sourcesFile fullName. (File named: file) readStreamDo: [ :binaryFile | (ZnBufferedReadStream on: (ZnCharacterReadStream on: binaryFile encoding: 'utf8')) upToEnd ]] timeToRun. "0:00:00:14.189" 4. File System By default, file system files are buffered and utf8 encoded to keep backwards compatibility. 'name' asFileReference readStreamDo: [ :bufferedUtf8Stream | ... ]. 'name' asFileReference writeStreamDo: [ :bufferedUtf8Stream | ... ]. FileStream also provides access to plain binary files using the #binaryRead/WriteStream messages. Binary streams are buffered by default also. 'name' asFileReference binaryReadStreamDo: [ :bufferedBinaryStream | ... ]. 'name' asFileReference binaryWriteStreamDo: [ :bufferedBinaryStream | ... ]. If you want a file with another encoding (to come in the PR https://github.com/pharo-project/pharo/pull/1134) you can specify it while obtaining the stream: 'name' asFileReference readStreamEncoded: 'utf16' do: [ :bufferedUtf16Stream | ... ]. 'name' asFileReference writeStreamEncoded: 'utf8' do: [ :bufferedUtf16Stream | ... ]. 5. Line Ending Conventions If you want to write files following a specific line ending convention, use the ZnNewLineWriterStream. This stream decorator will transform any line ending (cr, lf, crlf) into a defined line ending. By default it chooses the platform line ending convention. lineWriter := ZnNewLineWriterStream on: aStream. If you want to choose another line ending convention you can do: lineWriter forCr. lineWriter forLf. lineWriter forCrLf. lineWriter forPlatformLineEnding. -- 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

5 8

[Pharo 7] Help needed reviewing Pull requests
by Marcus Denker March 20, 2018

March 20, 2018

Hello, we need more people helping to review and tests Pull Requests. https://github.com/pharo-project/pharo/pulls <https://github.com/pharo-project/pharo/pulls> Especially, it is very important to add a note if you think that something should be merged. Even if it is clear from the context. We need an explicit âthis is good to integrateâ. Marcus

1 0

Released versions in Pharo Bootstrap
by tesonep＠gmail.com March 19, 2018

March 19, 2018

Hello, i have seen in the latest version of Pharo baselines pointing to "floating" versions. A version that is not fixed. I want to know why this is like that? To me this is basically wrong, because basically this goes against the idea of having repeatable builds. Also using semantic versions with tags in Git is wrong, as tags should be immutable (that is why you have to use --force to update them, in Guille's words "If you have to force it, it is not good"). Cheers, -- Pablo Tesone. tesonep(a)gmail.com

12 49