- Pharo-users - lists.pharo.org

Re: [Pharo-users] Grease stream tests failing on Pharo7

by Johan Brichau

Hi, As Iâm diving into the changes and why it fails: (ReadWriteStream on: âabcâ) contents -> = âabcâ on Pharo 6 -> = ââ on Pharo 7 That seems wrong to me. (Iâve also sent this question via github on the commit itself https://github.com/pharo-project/pharo/commit/9e442addff3790af0c78dbc73f1f3… <https://github.com/pharo-project/pharo/commit/9e442addff3790af0c78dbc73f1f3…> ) cheers Johan > On 22 Jul 2018, at 10:52, Johan Brichau <johan(a)inceptive.be> wrote: > > Hi, > > I am taking a look at making Grease and Seaside work correctly on Pharo7. > > There have been a number of changes to the ReadWriteStream implementation in Pharo that break Grease tests: https://travis-ci.org/SeasideSt/Grease/jobs/406766720 <https://travis-ci.org/SeasideSt/Grease/jobs/406766720> > It seems ReadWriteStream is broken: the readLimit is almost always wrong meaning that the stream `atEnd`, `contents` etc.. return wrong values > > Before I dive into this, I wanted to inquire if anyone is working on this as I cannot seem to find any open cases on this on the issue tracker. > > cheers > Johan > >

July 23, 2018

Re: [Pharo-users] Pharo 7 file streams guideline

by Ben Coman

On 23 July 2018 at 15:38, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > Hello, > > I've prepared a draft of a short document that should help you with the > transition to the "new" file streams API in Pharo 7. > > https://github.com/pavel-krivanek/pharoMaterials/blob/master/Filestreams.MD > > Pull requests are welcome. > > Cheers, > -- Pavel > > > Some discussion prior to any pull request (and while I'm away from Pharo machine) I like all the new code examples until "Write a UTF-8 text to STDOUT" and I wonder "Stdio stdout writeStreamDo: [ :stream | stream nextPutAll: 'a â b' ]" would better fit the pattern of the other new code. (presuming "Stdio stdout" returns a FileReference, oherwise maybe "Stdio stdoutRef" or "Stdio stdout asFileReference") Under "Positionable streams", rather than needing "3 timesRepeat: [ stream next ]" would it be worth having #utf8position: to more intention revealing? cheers -ben

July 23, 2018

Pharo 7 file streams guideline

by Pavel Krivanek

Hello, I've prepared a draft of a short document that should help you with the transition to the "new" file streams API in Pharo 7. https://github.com/pavel-krivanek/pharoMaterials/blob/master/Filestreams.MD Pull requests are welcome. Cheers, -- Pavel

July 23, 2018

Re: [Pharo-users] Changing a BaselineOf... to include one more package

by Andrew Black

> On 22 Jul 2018, at 19:35 , Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Andrew Black-2 wrote >>> spec >>> baseline: 'SmaCC-Reification' >>> with: [ spec repository: 'github://apblack/SmaCC:fglr' ]. > > This line will not work. What you're saying here is load a BaselineOfXyz > where Xyz = 'SmaCC-Reification'. In fact you want to load the package. I > think you can just change the keyword #basline: to #package:, although SmaCC > has a 'Reification' group, which might be better. In any event, if you just > want to make sure that the 'SmaCC-Reification' package is loaded when you > load SmaCC, then I think what you're after is: > spec > baseline: 'SmaCC' with: [ spec loads: #('Reification' ) ] > > I think the above would replace both of your SmaCC-related lines (you can > specify multiple entities in to #loads: if needed. > > NB. the preferred syntax in a baseline is literal arrays like above i.e. #() > instead of curly-brace runtime arrays like {'Grace-Tests' . 'Grace-Ast'} > Thanks for the suggestions. But now I am more confused than ever! Can you tell me what this line actually means. That is, what does the #baseline:with: method actually declare? Where should I put this statement? In baselineOfSmaCC, or baselineOfGrace? Why? Note that the SmaCC-Reification package is not part of the current normal load for SmaCC â thatâs why I have to specify it separately. Is this declaration saying the opposite? If not, what is it saying? Earlier, you wrote: >> spec package: 'SmaCC-Reification' with: [ spec requires: >> #('SmaCC-Smalltalk-Parser' 'SmaCC-Runtime' 'SmaCC-Java') ] AFAICT this is not necessary because these dependencies are declared in BaselineOfSmaCC. These declarations are the very lines from baselineOfSmaCC that declare these dependencies â arenât they? If I take them out, how will Metacello know that loading SmaCC-Reification requires the three packages listed in the array? Iâm sorry if I sound frustrated â none of this makes any sense to me. There seems to be no documentation other than the very high-level stuff that describes th eoverall purpose of package dependencies â which I think that I understand. Andrew

July 23, 2018

Re: [Pharo-users] Changing a BaselineOf... to include one more package

by Sean P. DeNigris

Andrew Black-2 wrote >> spec >> baseline: 'SmaCC-Reification' >> with: [ spec repository: 'github://apblack/SmaCC:fglr' ]. This line will not work. What you're saying here is load a BaselineOfXyz where Xyz = 'SmaCC-Reification'. In fact you want to load the package. I think you can just change the keyword #basline: to #package:, although SmaCC has a 'Reification' group, which might be better. In any event, if you just want to make sure that the 'SmaCC-Reification' package is loaded when you load SmaCC, then I think what you're after is: spec baseline: 'SmaCC' with: [ spec loads: #('Reification' ) ] I think the above would replace both of your SmaCC-related lines (you can specify multiple entities in to #loads: if needed. NB. the preferred syntax in a baseline is literal arrays like above i.e. #() instead of curly-brace runtime arrays like {'Grace-Tests' . 'Grace-Ast'} ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

July 23, 2018

Re: [Pharo-users] Changing a BaselineOf... to include one more package

by Sean P. DeNigris

Guillermo Polito wrote >> But then I must also specify the dependencies of the SmaCC-Reification >> package, so I need to add >> >> spec package: 'SmaCC-Reification' with: [ spec requires: >> #('SmaCC-Smalltalk-Parser' 'SmaCC-Runtime' 'SmaCC-Java') ] AFAICT this is not necessary because these dependencies are declared in BaselineOfSmaCC. In fact the whole point of Metacello is that you can refer just to the specific entity within a project you want to load and Metacello should take care of bringing along all its dependencies. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

July 23, 2018

Re: [Pharo-users] Changing a BaselineOf... to include one more package

by Andrew Black

> On 21 Jul 2018, at 08:22 , Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Andrew P. Black wrote >> I donât know what else to try! > > From the error message: > Could not resolve: BaselineOfSmaCC-Reification... in > https://github.com/apblack/SmaCC.git[working] > > I'm guessing that you can't load from two different branches of the same git > repo. Can you fork the project and create a new branch that merges in the > required changes from the 'working' and 'fglr' branches? Good trysuggestion Sean. I think that there may indeed be some brokenness in the way that Pharo uses git, so that the branch spec in the baseline is not always obeyed. So I switched both of the dependencies to be on the same branch (fglr), and for good measure switched my local repo to also be on that branch. > spec > baseline: 'SmaCC' > with: [ spec repository: 'github://apblack/SmaCC:fglr' ]. > spec > baseline: 'SmaCC-Reification' > with: [ spec repository: 'github://apblack/SmaCC:fglr' ]. The result? Nothing changes. I still get a complaint Could not resolve: BaselineOfSmaCC-Reification [BaselineOfSmaCC-Reification] in /Users/black/Development/Pharo/images/Pharo 7.0 SmallGrace 33/pharo-local/package-cache git@github.com:apblack/SmaCC.git[fglr] In the git directory I can see > silverstone: ~/iceberg/apblack/SmaCC$ ls -d SmaCC-Reification.package/ > SmaCC-Reification.package/ > silverstone: ~/iceberg/apblack/SmaCC$ git br > * fglr > ... Is it supposed to be looking for `BaselineOfSmaCC-Reification` rather than for `SmaCC-Reification`? There is no `BaselineOfSmaCC-Reification`, just a `BaselineOfSmaCC` that defines a group called `SmaCC-Refication`. (I did try replacing baseline: âSmaCC-Reificationâ by group: âSmaCC-Reificationâ , but that gave a different error.) Andrew

July 23, 2018

Dynabook concept

by Hilaire

Some reflexions on the Dynabook concept: http://blog.drgeo.eu/post/2018/The-Dynabook-Concept Hilaire -- Dr. Geo http://drgeo.eu

July 22, 2018

Re: [Pharo-users] Mac OS X left/right scrolling in Pharo issues

by Manuel Leuenberger

July 22, 2018

Grease stream tests failing on Pharo7

by Johan Brichau

Hi, I am taking a look at making Grease and Seaside work correctly on Pharo7. There have been a number of changes to the ReadWriteStream implementation in Pharo that break Grease tests: https://travis-ci.org/SeasideSt/Grease/jobs/406766720 <https://travis-ci.org/SeasideSt/Grease/jobs/406766720> It seems ReadWriteStream is broken: the readLimit is almost always wrong meaning that the stream `atEnd`, `contents` etc.. return wrong values Before I dive into this, I wanted to inquire if anyone is working on this as I cannot seem to find any open cases on this on the issue tracker. cheers Johan

July 22, 2018