- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] New Files in Pharo - Migration Guide, How To's and examples

by Nicolas Cellier

2018-03-19 21:21 GMT+01:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > > > 2018-03-19 20:39 GMT+01:00 Esteban A. Maringolo <emaringolo(a)gmail.com>: > >> 2018-03-19 16:32 GMT-03:00 Denis Kudriashov <dionisiydk(a)gmail.com>: >> > >> > Hi Guille. >> >> > What you think to add helpfull converting methods? >> >> I'd like them. Anything that saves me from passing a string literal as >> parameter is good. :) >> >> > aStream buffered. >> >> I'd only change this one, to #beBuffered. >> > > But #be sounds like it modifies receiver. > But idea is same as #reversed or #sorted for collections. > > -1 for beBuffered, it's not about adding states to the stream. As Denis said, it's a transform producing a new stream. > >> > aStream withLineEnding: String cr. >> > aStream withPlatformLineEnding. >> >> These two seem ambiguous to me, #with prefix signals something else in my >> head. > > >> I'd remove the "with" and use instead: >> >> aStream lineEnding: String cr. >> aStream usePlatformLineEnding. >> > > Same here. They will return new instances wrapping receiver. And #with is > like #copyWith: for arrays. > Maybe something like: > > aStream forcedLineEnding: String cr. > aStream forcedPlatformLineEnding. > > > >> >> Regards! >> >> >> >> Esteban A. Maringolo >> >> >

March 19, 2018

Re: [Pharo-dev] New Files in Pharo - Migration Guide, How To's and examples

by Denis Kudriashov

2018-03-19 20:39 GMT+01:00 Esteban A. Maringolo <emaringolo(a)gmail.com>: > 2018-03-19 16:32 GMT-03:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > > > > Hi Guille. > > > What you think to add helpfull converting methods? > > I'd like them. Anything that saves me from passing a string literal as > parameter is good. :) > > > aStream buffered. > > I'd only change this one, to #beBuffered. > But #be sounds like it modifies receiver. But idea is same as #reversed or #sorted for collections. > > > aStream withLineEnding: String cr. > > aStream withPlatformLineEnding. > > These two seem ambiguous to me, #with prefix signals something else in my > head. > I'd remove the "with" and use instead: > > aStream lineEnding: String cr. > aStream usePlatformLineEnding. > Same here. They will return new instances wrapping receiver. And #with is like #copyWith: for arrays. Maybe something like: aStream forcedLineEnding: String cr. aStream forcedPlatformLineEnding. > > Regards! > > > > Esteban A. Maringolo > >

March 19, 2018

Re: [Pharo-dev] New Files in Pharo - Migration Guide, How To's and examples

by Stephane Ducasse

+ one to Esteban gret suggestions! On Mon, Mar 19, 2018 at 8:39 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > 2018-03-19 16:32 GMT-03:00 Denis Kudriashov <dionisiydk(a)gmail.com>: >> >> Hi Guille. > >> What you think to add helpfull converting methods? > > I'd like them. Anything that saves me from passing a string literal as > parameter is good. :) > >> aStream buffered. > > I'd only change this one, to #beBuffered. > >> aStream withLineEnding: String cr. >> aStream withPlatformLineEnding. > > These two seem ambiguous to me, #with prefix signals something else in my head. > > I'd remove the "with" and use instead: > > aStream lineEnding: String cr. > aStream usePlatformLineEnding. > > Regards! > > > > Esteban A. Maringolo >

March 19, 2018

Re: [Pharo-dev] New Files in Pharo - Migration Guide, How To's and examples

by Esteban A. Maringolo

2018-03-19 16:32 GMT-03:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > > Hi Guille. > What you think to add helpfull converting methods? I'd like them. Anything that saves me from passing a string literal as parameter is good. :) > aStream buffered. I'd only change this one, to #beBuffered. > aStream withLineEnding: String cr. > aStream withPlatformLineEnding. These two seem ambiguous to me, #with prefix signals something else in my head. I'd remove the "with" and use instead: aStream lineEnding: String cr. aStream usePlatformLineEnding. Regards! Esteban A. Maringolo

March 19, 2018

Re: [Pharo-dev] New Files in Pharo - Migration Guide, How To's and examples

by Denis Kudriashov

Hi Guille. What you think to add helpfull converting methods? aStream buffered. aStream encodedWith: 'utf8'. aStream utf8Encoded. "because it is very common case". aStream decodedFrom: 'utf8'. aStream utf8Decoded. "because it is very common case". aStream withLineEnding: String cr. aStream withPlatformLineEnding. (all methods will return new streams) 2018-03-19 17:19 GMT+01:00 Guillermo Polito <guillermopolito(a)gmail.com>: > 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 <+33%206%2052%2070%2066%2013> >

March 19, 2018

Re: [Pharo-dev] Released versions in Pharo Bootstrap

by Cyril Ferlicot D.

Le 19/03/2018 Ã 18:49, Stephan Eggermont a Ã©crit : > Then why bother releasing? > Hi, For people using Pharo 7 to not get the same bugs for more than 1 year, to get the new functionalities and to be able to detect new bugs introduced in releases. > Stephan > > > > > -- Cyril Ferlicot https://ferlicot.fr

March 19, 2018

Re: [Pharo-dev] Released versions in Pharo Bootstrap

by Stephan Eggermont

Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > 2018-03-19 9:16 GMT+01:00 Stephan Eggermont <stephan(a)stack.nl>: > >> Denis Kudriashov <dionisiydk(a)gmail.com> >> wrote: >>> 2018-03-17 17:01 GMT+01:00 Stephan Eggermont >> <stephan(a)stack.nl>: >>> >>>> Denis Kudriashov <dionisiydk(a)gmail.com> >>>> wrote: >>>>> >>>>> No. Each build just loads specified version. I do not need to create >> new >>>>> version for new build. >>>>> But I think I still not understand you >>>> >>>> That specified version will no longer work in a newer pharo build. Pharo >>>> changes, making it necessary for your dependencies to change. Will you >> make >>>> a new release each time one of your dependencies needs to change? >>>> >>> >>> I do not put dependencies of projects which are part of standard Pharo >>> image. So Pharo updates do not affect my baselines >> >> And your dependencies are not impacted by standard pharo changes? >> > > It can be impacted of course. But it is normal process for alpha Pharo 7. > And Pharo 6 is fixed, so I do not care. Then why bother releasing? Stephan

March 19, 2018

New Files in Pharo - Migration Guide, How To's and examples

by Guillermo Polito

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

March 19, 2018

[Pharo 7.0-dev] Build #704: Fix #21602. Choose line ending convention in ZnCrPortableWriteStream.

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

There is a new Pharo build available! The status of the build #704 was: SUCCESS. The Pull Request #1116 was integrated: "Fix #21602. Choose line ending convention in ZnCrPortableWriteStream." Pull request url: https://github.com/pharo-project/pharo/pull/1116 Issue Url: https://pharo.fogbugz.com/f/cases/21602 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 19, 2018

[Pharo 7.0-dev] Build #703: 21619-Integrate-new-Calypso-version-0110

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

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

March 19, 2018