- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Github and Pharo

by StÃ©phane Ducasse

On Nov 4, 2013, at 11:34 AM, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: > <rant> > Now, I am more and more leaning towards having a debian VM into which I can do all the development. That's the kind of system production ends up on anyway. Debian 6 for me, as 7 requires to go into Multiarch + 32 bits libs which is not on by default and is a headache to get right. This is why what eliot is doing with the 64 bits is really key for our future. > I had a hard time getting Pharo to run on Debian 7. And when faced with a given default server box, it was worse as there was no way to add the packages. This excluded Pharo while Rails/PHP people ran happily. :-( > </rant>

Nov. 4, 2013

Re: [Pharo-dev] Github and Pharo

by StÃ©phane Ducasse

On Nov 4, 2013, at 11:02 AM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > Hi Stef, > > I don't have a blog ;) yet. But yes, I think I should write things up. You can write in Pier format and this will generate a pdf and html. look at pharo for the entreprise on github. I can help also if you write in ascii to make it processed. I can add you to the github project. > > Thierry > > Le 04/11/2013 00:04, StÃ©phane Ducasse a Ã©crit : >> one of you should write a blog entry on Git support and the process :) >> Because we will get this repeat that often. >> >> Stef >> >> >> On Nov 3, 2013, at 2:11 PM, kilon alios <kilon.alios(a)gmail.com >> <mailto:kilon.alios@gmail.com>> wrote: >> >>> ok it was my bad, i had not correctly initialized my git repo. Now it >>> works fine. Thanks for the help this awesome. >>> >>> >>> On Sun, Nov 3, 2013 at 2:56 PM, kilon alios <kilon.alios(a)gmail.com >>> <mailto:kilon.alios@gmail.com>> wrote: >>> >>> I installed OSProcess but I get a new Error : Git Error : bad >>> default revision 'Head' >>> >>> just to clarify i try to commit to an existing git repo that I >>> have create manually via terminal. >>> >>> >>> MCFileTreeGitRepository(Object)>>error: >>> MCFileTreeGitRepository>>gitVersions >>> MCFileTreeGitRepository>>loadAncestry >>> MCFileTreeGitRepository>>loadAllFileNames in Block: [ :bar | ... >>> BlockClosure>>cull: >>> Job>>run in Block: [ result := block cull: self ] >>> BlockClosure>>on:do: >>> Job>>run in Block: [ ... >>> BlockClosure>>ensure: >>> Job>>run >>> MorphicUIManager(UIManager)>>displayProgress:from:to:during: >>> ByteString(String)>>displayProgressFrom:to:during: >>> MCFileTreeGitRepository>>loadAllFileNames >>> MCFileTreeGitRepository>>allFileNames >>> MCFileTreeGitRepository>>readableFileNames >>> MCFileTreeGitRepository(MCFileTreeRepository)>>allFileNamesForVersionNamed: >>> MCFileTreeGitRepository(MCDirectoryRepository)>>includesVersionNamed: >>> MCWorkingCopy>>uniqueVersionNameIn: in Block: [ ... >>> BlockClosure>>cull: >>> Job>>run in Block: [ result := block cull: self ] >>> BlockClosure>>on:do: >>> Job>>run in Block: [ ... >>> BlockClosure>>ensure: >>> Job>>run >>> MorphicUIManager(UIManager)>>displayProgress:from:to:during: >>> ByteString(String)>>displayProgressFrom:to:during: >>> MCWorkingCopy>>uniqueVersionNameIn: >>> MCWorkingCopy>>newVersionIn: >>> MCWorkingCopyBrowser>>basicSaveVersionIn: in Block: [ ... >>> WorldState>>runStepMethodsIn: >>> >>> >>> >>> On Sun, Nov 3, 2013 at 2:40 PM, GOUBIER Thierry >>> <thierry.goubier(a)cea.fr <mailto:thierry.goubier@cea.fr>> wrote: >>> >>> Oh sorry, the OSProcess dependency is missing :( >>> >>> You can install OSProcess from the configuration browser in >>> your Pharo image or, on the command line : >>> >>> $ pharo Pharo.image config >>> http://ss3.gemstone.com/ss/MetaRepoForPharo20 >>> ConfigurationOfOSProcess --install=stable >>> >>> Thierry >>> >>> ------------------------------------------------------------------------ >>> *De :* Pharo-dev [pharo-dev-bounces(a)lists.pharo.org >>> <mailto:pharo-dev-bounces@lists.pharo.org>] de la part de >>> kilon alios [kilon.alios(a)gmail.com <mailto:kilon.alios@gmail.com>] >>> *Date d'envoi :* dimanche 3 novembre 2013 13:30 >>> >>> *Ã :* Pharo Development List >>> *Objet :* Re: [Pharo-dev] Github and Pharo >>> >>> look like it cant find PipeableOSProcess on Macos, any idea >>> where I can find this object ? >>> >>> UndefinedObject(Object)>>doesNotUnderstand: #command: >>> MCFileTreeGitRepository>>gitVersions >>> MCFileTreeGitRepository>>loadAncestry >>> MCFileTreeGitRepository>>loadAllFileNames in Block: [ :bar | ... >>> BlockClosure>>cull: >>> Job>>run in Block: [ result := block cull: self ] >>> BlockClosure>>on:do: >>> Job>>run in Block: [ ... >>> BlockClosure>>ensure: >>> Job>>run >>> MorphicUIManager(UIManager)>>displayProgress:from:to:during: >>> ByteString(String)>>displayProgressFrom:to:during: >>> MCFileTreeGitRepository>>loadAllFileNames >>> MCFileTreeGitRepository>>allFileNames >>> MCFileTreeGitRepository>>readableFileNames >>> MCFileTreeGitRepository(MCFileTreeRepository)>>allFileNamesForVersionNamed: >>> MCFileTreeGitRepository(MCDirectoryRepository)>>includesVersionNamed: >>> MCWorkingCopy>>uniqueVersionNameIn: in Block: [ ... >>> BlockClosure>>cull: >>> Job>>run in Block: [ result := block cull: self ] >>> BlockClosure>>on:do: >>> Job>>run in Block: [ ... >>> BlockClosure>>ensure: >>> Job>>run >>> MorphicUIManager(UIManager)>>displayProgress:from:to:during: >>> ByteString(String)>>displayProgressFrom:to:during: >>> MCWorkingCopy>>uniqueVersionNameIn: >>> MCWorkingCopy>>newVersionIn: >>> MCWorkingCopyBrowser>>basicSaveVersionIn: in Block: [ ... >>> WorldState>>runStepMethodsIn: >>> >>> >>> >>> On Sun, Nov 3, 2013 at 12:41 PM, GOUBIER Thierry >>> <thierry.goubier(a)cea.fr <mailto:thierry.goubier@cea.fr>> wrote: >>> >>> This is where you use GitFileTree. >>> >>> GitFileTree will do you the commit, browsing the git logs >>> and accessing all versions of your package in the git repo >>> (browsing, loading, changes with the same GUI and look as >>> a smalltalkhub repo). It won't do the push, however(*). It >>> will show you the current branch in the repo too (**). >>> >>> For pharo3, GitFileTree is available with: >>> >>> $ pharo Pharo.image eval --save Gofer new url: >>> \'http://smalltalkhub.com/mc/ThierryGoubier/MonticelloFileTree-Git/main\ >>> <http://smalltalkhub.com/mc/ThierryGoubier/MonticelloFileTree-Git/main%5C>'\; >>> package: \'MonticelloFileTree-Git\'\; load >>> >>> For pharo2, there is a group named >>> 'MonticelloFileTree-Git' in FileTree configuration. >>> >>> Feel free to ask if you have any questions or suggestions >>> on it! >>> >>> Thierry >>> >>> (*) It would be easy to do commit + push in one go, but, >>> I'm not sure I'd like to do a push each time I do a >>> commit. I tend to prefer a push a day. Maybe something >>> like a marker in the repository inspector to remind me I >>> have something to push? >>> (**) It doesn't change branches, and there is no support >>> for branches in Monticello... This tend to trigger bugs in >>> MC package cache. >>> >>> ------------------------------------------------------------------------ >>> *De :* Pharo-dev [pharo-dev-bounces(a)lists.pharo.org >>> <mailto:pharo-dev-bounces@lists.pharo.org>] de la part de >>> kilon alios [kilon.alios(a)gmail.com >>> <mailto:kilon.alios@gmail.com>] >>> *Date d'envoi :* dimanche 3 novembre 2013 10:16 >>> *Ã :* Pharo Development List >>> *Objet :* Re: [Pharo-dev] Github and Pharo >>> >>> Thank you for your efforts , I have installed filetree >>> using the instructions provided in the github pages for >>> pharo 3. I was also successful into generating the local >>> files for my packages that I have inserted to my git >>> folder. I can manually git commit and git push them from >>> terminal but how I do this from inside Monticello-Filetree ? >>> >>> >>> On Sun, Nov 3, 2013 at 9:53 AM, GOUBIER Thierry >>> <thierry.goubier(a)cea.fr <mailto:thierry.goubier@cea.fr>> >>> wrote: >>> >>> Hi, >>> >>> I've used github and work_owned git repositories as >>> primary workplaces for more than a year. First with >>> FileTree, then I wrote GitFileTree to make that >>> process simpler. >>> >>> Thierry >>> ------------------------------------------------------------------------ >>> *De :* Pharo-dev [pharo-dev-bounces(a)lists.pharo.org >>> <mailto:pharo-dev-bounces@lists.pharo.org>] de la part >>> de kilon alios [kilon.alios(a)gmail.com >>> <mailto:kilon.alios@gmail.com>] >>> *Date d'envoi :* samedi 2 novembre 2013 14:59 >>> *Ã :* Pharo Development List >>> *Objet :* [Pharo-dev] Github and Pharo >>> >>> So any information on how Pharo can be used with Github ? >>> >>> all I have is this >>> >>> https://github.com/dalehenrich/FSGit >>> >>> I dont need much, just basic git pull, push, clone, >>> add and rm should do fine for starter. >>> >>> But of course I am interesting into learning what can >>> be done, what is available , who needs help with what. >>> Github is something really important for me, so I am >>> willing to contribute as much I can into bringing >>> Pharo closer to it. >>> >>> My interest is using Github in place of smalltalkhub >>> and squeaksource. I was planning to implement >>> something like an App Store (not the purchase system) >>> for Pharo libraries and I would love to use github as >>> a backend to it and git of course. >>> >>> >>> >>> >>> >> > > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >

Nov. 4, 2013

Re: [Pharo-dev] Github and Pharo

by phil＠highoctane.be

I guess that's why I used filetree:// and not gitfiletree:// along with the git client to do the CLI commits and pushes on Windows (one can use GitBash for example, or MobaXterm Git plugin http://mobaxterm.mobatek.net/ > http://mobaxterm.mobatek.net/plugins.html > Git + Curl +Emacs [for you Gutenberg people, but Pdflatex is missing]). Additional benefit of MobaXterm on Windows: it has curl, wget etc, so Zeroconf scripts work easily. <rant> Now, I am more and more leaning towards having a debian VM into which I can do all the development. That's the kind of system production ends up on anyway. Debian 6 for me, as 7 requires to go into Multiarch + 32 bits libs which is not on by default and is a headache to get right. I had a hard time getting Pharo to run on Debian 7. And when faced with a given default server box, it was worse as there was no way to add the packages. This excluded Pharo while Rails/PHP people ran happily. :-( </rant> Phil

Nov. 4, 2013

Re: [Pharo-dev] Duplicate IVs | Bug or feature?

by Luc Fabresse

2013/11/4 Luc Fabresse <luc.fabresse(a)gmail.com> > > perhaps related to the new object layout. > arg no, not in 2.0 I guess Luc > > Luc > > 2013/11/4 Noury Bouraqadi <bouraqadi(a)gmail.com> > >> Hi, >> >> In Pharo2.0 #20625 it's possible to create two classes, one inheriting >> from the other, and declaring the exact same IV (attached code). >> It turns out that instances of the subclass hold two IVs with the exact >> name. >> When accessing the IV in the superclass, the first IV is used, while in >> the subclass the second IV is accessed. >> >> Bug or feature? >> >> Noury >> Ecole des Mines de Douai >> http://car.mines-douai.fr/noury >> -- >> >> >> >> >> >> >> Afin de contribuer au respect de l'environnement, >> >> >> merci de n'imprimer ce courriel qu'en cas de necessite >> >> >> >> >> >> Please consider the environment before you print >> >> >> >> >> >> >

Nov. 4, 2013

Re: [Pharo-dev] Duplicate IVs | Bug or feature?

by Luc Fabresse

perhaps related to the new object layout. Luc 2013/11/4 Noury Bouraqadi <bouraqadi(a)gmail.com> > Hi, > > In Pharo2.0 #20625 it's possible to create two classes, one inheriting > from the other, and declaring the exact same IV (attached code). > It turns out that instances of the subclass hold two IVs with the exact > name. > When accessing the IV in the superclass, the first IV is used, while in > the subclass the second IV is accessed. > > Bug or feature? > > Noury > Ecole des Mines de Douai > http://car.mines-douai.fr/noury > -- > > > > > > > Afin de contribuer au respect de l'environnement, > > > merci de n'imprimer ce courriel qu'en cas de necessite > > > > > > Please consider the environment before you print > > > > > >

Nov. 4, 2013

Duplicate IVs | Bug or feature?

by Noury Bouraqadi

Hi, In Pharo2.0 #20625 it's possible to create two classes, one inheriting from the other, and declaring the exact same IV (attached code). It turns out that instances of the subclass hold two IVs with the exact name. When accessing the IV in the superclass, the first IV is used, while in the subclass the second IV is accessed. Bug or feature? Noury Ecole des Mines de Douai http://car.mines-douai.fr/noury -- Afin de contribuer au respect de l'environnement, merci de n'imprimer ce courriel qu'en cas de necessite Please consider the environment before you print

Nov. 4, 2013

Re: [Pharo-dev] Github and Pharo

by kilon alios

I added the missing method to the class, adjusting it with the 'c:\' system path, unfortunately now it complains that File pipeWriter is closed. So it looks like it will need a more a careful look to make this work on windows. Will try to examine closer. On Mon, Nov 4, 2013 at 12:05 PM, Goubier Thierry <thierry.goubier(a)cea.fr>wrote: > > So far, from what I see, this is an OSProcess issue when under Windows, so > it's a bit unfamiliar territory to me. > > The design of MonticelloFileTree-Git is to call the 'git' command line to > do things, and it rely on OSProcess to provide the primitive. This was by > far the fastest way to get things done :) > > Thierry > > Le 04/11/2013 10:49, kilon alios a Ã©crit : > >> I can document this , but not before I get really familiar with the >> process. Also I have not forgotten my promise to document Nativeboost, >> expect a blog post about that really soon. >> >> I tried to use this in windows and I get a failure >> >> ExternalWindowsOSProcess class(Object)>>doesNotUnderstand: >> #defaultShellPath >> PipeableOSProcess >> class>>command:environment:workingDir:input:output:error: >> errorPipelineStream:shellSyntax: >> PipeableOSProcess >> class>>command:environment:workingDir:input:output:error: >> errorPipelineStream: >> PipeableOSProcess class>>command: >> MCFileTreeGitRepository>>gitVersions >> MCFileTreeGitRepository>>loadAncestry >> MCFileTreeGitRepository>>loadAllFileNames in Block: [ :bar | ... >> BlockClosure>>cull: >> Job>>run in Block: [ result := block cull: self ] >> BlockClosure>>on:do: >> Job>>run in Block: [ ... >> BlockClosure>>ensure: >> Job>>run >> MorphicUIManager(UIManager)>>displayProgress:from:to:during: >> ByteString(String)>>displayProgressFrom:to:during: >> MCFileTreeGitRepository>>loadAllFileNames >> MCFileTreeGitRepository>>allFileNames >> MCFileTreeGitRepository>>readableFileNames >> MCFileTreeGitRepository>>packageDescriptionsFromReadableFileNames >> MCFileTreeGitRepository(MCFileBasedRepository)>> >> retrieveVersionsWithPackageNames: >> MCFileTreeGitRepositoryInspector(MCFileRepositoryInspector)>>refresh >> MCFileTreeGitRepositoryInspector(MCFileRepositoryInspector)> >> >setRepository:workingCopy: >> in Block: [ ... >> BlockClosure>>newProcess in Block: [ ... >> >> I have loaded both OSProcess and OSWindows , are there other >> dependencies on Windows I need to load ? >> >> >> >> On Mon, Nov 4, 2013 at 6:46 AM, Tudor Girba <tudor(a)tudorgirba.com >> <mailto:tudor@tudorgirba.com>> wrote: >> >> Exactly. This would be a valuable contribution. Screencasts would be >> very helpful as well. >> >> Doru >> >> >> >> >> On Mon, Nov 4, 2013 at 12:04 AM, StÃ©phane Ducasse >> <stephane.ducasse(a)inria.fr <mailto:stephane.ducasse@inria.fr>> wrote: >> >> one of you should write a blog entry on Git support and the >> process :) >> Because we will get this repeat that often. >> >> Stef >> >> >> >> On Nov 3, 2013, at 2:11 PM, kilon alios <kilon.alios(a)gmail.com >> <mailto:kilon.alios@gmail.com>> wrote: >> >> ok it was my bad, i had not correctly initialized my git repo. >>> Now it works fine. Thanks for the help this awesome. >>> >>> >>> On Sun, Nov 3, 2013 at 2:56 PM, kilon alios >>> <kilon.alios(a)gmail.com <mailto:kilon.alios@gmail.com>> wrote: >>> >>> I installed OSProcess but I get a new Error : Git Error : >>> bad default revision 'Head' >>> >>> just to clarify i try to commit to an existing git repo >>> that I have create manually via terminal. >>> >>> >>> MCFileTreeGitRepository(Object)>>error: >>> MCFileTreeGitRepository>>gitVersions >>> MCFileTreeGitRepository>>loadAncestry >>> MCFileTreeGitRepository>>loadAllFileNames in Block: [ :bar >>> | ... >>> BlockClosure>>cull: >>> Job>>run in Block: [ result := block cull: self ] >>> BlockClosure>>on:do: >>> Job>>run in Block: [ ... >>> BlockClosure>>ensure: >>> Job>>run >>> MorphicUIManager(UIManager)>>displayProgress:from:to:during: >>> ByteString(String)>>displayProgressFrom:to:during: >>> MCFileTreeGitRepository>>loadAllFileNames >>> MCFileTreeGitRepository>>allFileNames >>> MCFileTreeGitRepository>>readableFileNames >>> MCFileTreeGitRepository(MCFileTreeRepository)>> >>> allFileNamesForVersionNamed: >>> MCFileTreeGitRepository(MCDirectoryRepository)>> >>> includesVersionNamed: >>> MCWorkingCopy>>uniqueVersionNameIn: in Block: [ ... >>> BlockClosure>>cull: >>> Job>>run in Block: [ result := block cull: self ] >>> BlockClosure>>on:do: >>> Job>>run in Block: [ ... >>> BlockClosure>>ensure: >>> Job>>run >>> MorphicUIManager(UIManager)>>displayProgress:from:to:during: >>> ByteString(String)>>displayProgressFrom:to:during: >>> MCWorkingCopy>>uniqueVersionNameIn: >>> MCWorkingCopy>>newVersionIn: >>> MCWorkingCopyBrowser>>basicSaveVersionIn: in Block: [ ... >>> WorldState>>runStepMethodsIn: >>> >>> >>> >>> On Sun, Nov 3, 2013 at 2:40 PM, GOUBIER Thierry >>> <thierry.goubier(a)cea.fr <mailto:thierry.goubier@cea.fr>> >>> >>> wrote: >>> >>> Oh sorry, the OSProcess dependency is missing :( >>> >>> You can install OSProcess from the configuration >>> browser in your Pharo image or, on the command line : >>> >>> $ pharo Pharo.image config >>> http://ss3.gemstone.com/ss/MetaRepoForPharo20 >>> ConfigurationOfOSProcess --install=stable >>> >>> Thierry >>> >>> ------------------------------ >>> ------------------------------------------ >>> *De :* Pharo-dev [pharo-dev-bounces(a)lists.pharo.org >>> <mailto:pharo-dev-bounces@lists.pharo.org>] de la part >>> de kilon alios [kilon.alios(a)gmail.com >>> >>> <mailto:kilon.alios@gmail.com>] >>> *Date d'envoi :* dimanche 3 novembre 2013 13:30 >>> >>> *Ã :* Pharo Development List >>> *Objet :* Re: [Pharo-dev] Github and Pharo >>> >>> >>> look like it cant find PipeableOSProcess on Macos, any >>> idea where I can find this object ? >>> >>> UndefinedObject(Object)>>doesNotUnderstand: #command: >>> MCFileTreeGitRepository>>gitVersions >>> MCFileTreeGitRepository>>loadAncestry >>> MCFileTreeGitRepository>>loadAllFileNames in Block: [ >>> :bar | ... >>> BlockClosure>>cull: >>> Job>>run in Block: [ result := block cull: self ] >>> BlockClosure>>on:do: >>> Job>>run in Block: [ ... >>> BlockClosure>>ensure: >>> Job>>run >>> MorphicUIManager(UIManager)>>displayProgress:from:to: >>> during: >>> ByteString(String)>>displayProgressFrom:to:during: >>> MCFileTreeGitRepository>>loadAllFileNames >>> MCFileTreeGitRepository>>allFileNames >>> MCFileTreeGitRepository>>readableFileNames >>> MCFileTreeGitRepository(MCFileTreeRepository)>> >>> allFileNamesForVersionNamed: >>> MCFileTreeGitRepository(MCDirectoryRepository)>> >>> includesVersionNamed: >>> MCWorkingCopy>>uniqueVersionNameIn: in Block: [ ... >>> BlockClosure>>cull: >>> Job>>run in Block: [ result := block cull: self ] >>> BlockClosure>>on:do: >>> Job>>run in Block: [ ... >>> BlockClosure>>ensure: >>> Job>>run >>> MorphicUIManager(UIManager)>>displayProgress:from:to: >>> during: >>> ByteString(String)>>displayProgressFrom:to:during: >>> MCWorkingCopy>>uniqueVersionNameIn: >>> MCWorkingCopy>>newVersionIn: >>> MCWorkingCopyBrowser>>basicSaveVersionIn: in Block: [ >>> ... >>> WorldState>>runStepMethodsIn: >>> >>> >>> >>> On Sun, Nov 3, 2013 at 12:41 PM, GOUBIER Thierry >>> <thierry.goubier(a)cea.fr >>> <mailto:thierry.goubier@cea.fr>> wrote: >>> >>> This is where you use GitFileTree. >>> >>> GitFileTree will do you the commit, browsing the >>> git logs and accessing all versions of your >>> package in the git repo (browsing, loading, >>> changes with the same GUI and look as a >>> smalltalkhub repo). It won't do the push, >>> however(*). It will show you the current branch in >>> the repo too (**). >>> >>> For pharo3, GitFileTree is available with: >>> >>> $ pharo Pharo.image eval --save Gofer new url: >>> \'http://smalltalkhub.com/mc/ThierryGoubier/ >>> MonticelloFileTree-Git/main\ >>> <http://smalltalkhub.com/mc/ThierryGoubier/ >>> MonticelloFileTree-Git/main%5C>'\; >>> >>> package: \'MonticelloFileTree-Git\'\; load >>> >>> For pharo2, there is a group named >>> 'MonticelloFileTree-Git' in FileTree configuration. >>> >>> Feel free to ask if you have any questions or >>> suggestions on it! >>> >>> Thierry >>> >>> (*) It would be easy to do commit + push in one >>> go, but, I'm not sure I'd like to do a push each >>> time I do a commit. I tend to prefer a push a day. >>> Maybe something like a marker in the repository >>> inspector to remind me I have something to push? >>> (**) It doesn't change branches, and there is no >>> support for branches in Monticello... This tend to >>> trigger bugs in MC package cache. >>> >>> ------------------------------ >>> ------------------------------------------ >>> *De :* Pharo-dev >>> [pharo-dev-bounces(a)lists.pharo.org >>> <mailto:pharo-dev-bounces@lists.pharo.org>] de la >>> >>> part de kilon alios [kilon.alios(a)gmail.com >>> <mailto:kilon.alios@gmail.com>] >>> *Date d'envoi :* dimanche 3 novembre 2013 10:16 >>> >>> *Ã :* Pharo Development List >>> *Objet :* Re: [Pharo-dev] Github and Pharo >>> >>> >>> Thank you for your efforts , I have installed >>> filetree using the instructions provided in the >>> github pages for pharo 3. I was also successful >>> into generating the local files for my packages >>> that I have inserted to my git folder. I can >>> manually git commit and git push them from >>> terminal but how I do this from inside >>> Monticello-Filetree ? >>> >>> >>> On Sun, Nov 3, 2013 at 9:53 AM, GOUBIER Thierry >>> <thierry.goubier(a)cea.fr >>> <mailto:thierry.goubier@cea.fr>> wrote: >>> >>> Hi, >>> >>> I've used github and work_owned git >>> repositories as primary workplaces for more >>> than a year. First with FileTree, then I wrote >>> GitFileTree to make that process simpler. >>> >>> Thierry >>> ------------------------------ >>> ------------------------------------------ >>> *De :* Pharo-dev >>> [pharo-dev-bounces(a)lists.pharo.org >>> <mailto:pharo-dev-bounces@lists.pharo.org>] de >>> >>> la part de kilon alios [kilon.alios(a)gmail.com >>> <mailto:kilon.alios@gmail.com>] >>> *Date d'envoi :* samedi 2 novembre 2013 14:59 >>> >>> *Ã :* Pharo Development List >>> *Objet :* [Pharo-dev] Github and Pharo >>> >>> >>> So any information on how Pharo can be used >>> with Github ? >>> >>> all I have is this >>> >>> https://github.com/dalehenrich/FSGit >>> >>> I dont need much, just basic git pull, push, >>> clone, add and rm should do fine for starter. >>> >>> But of course I am interesting into learning >>> what can be done, what is available , who >>> needs help with what. Github is something >>> really important for me, so I am willing to >>> contribute as much I can into bringing Pharo >>> closer to it. >>> >>> My interest is using Github in place of >>> smalltalkhub and squeaksource. I was planning >>> to implement something like an App Store (not >>> the purchase system) for Pharo libraries and >>> I would love to use github as a backend to it >>> and git of course. >>> >>> >>> >>> >>> >>> >> >> >> >> -- >> www.tudorgirba.com <http://www.tudorgirba.com> >> >> >> "Every thing has its own flow" >> >> >> > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 > >

Nov. 4, 2013

Re: [Pharo-dev] Github and Pharo

by Goubier Thierry

So far, from what I see, this is an OSProcess issue when under Windows, so it's a bit unfamiliar territory to me. The design of MonticelloFileTree-Git is to call the 'git' command line to do things, and it rely on OSProcess to provide the primitive. This was by far the fastest way to get things done :) Thierry Le 04/11/2013 10:49, kilon alios a Ã©crit : > I can document this , but not before I get really familiar with the > process. Also I have not forgotten my promise to document Nativeboost, > expect a blog post about that really soon. > > I tried to use this in windows and I get a failure > > ExternalWindowsOSProcess class(Object)>>doesNotUnderstand: #defaultShellPath > PipeableOSProcess > class>>command:environment:workingDir:input:output:error:errorPipelineStream:shellSyntax: > PipeableOSProcess > class>>command:environment:workingDir:input:output:error:errorPipelineStream: > PipeableOSProcess class>>command: > MCFileTreeGitRepository>>gitVersions > MCFileTreeGitRepository>>loadAncestry > MCFileTreeGitRepository>>loadAllFileNames in Block: [ :bar | ... > BlockClosure>>cull: > Job>>run in Block: [ result := block cull: self ] > BlockClosure>>on:do: > Job>>run in Block: [ ... > BlockClosure>>ensure: > Job>>run > MorphicUIManager(UIManager)>>displayProgress:from:to:during: > ByteString(String)>>displayProgressFrom:to:during: > MCFileTreeGitRepository>>loadAllFileNames > MCFileTreeGitRepository>>allFileNames > MCFileTreeGitRepository>>readableFileNames > MCFileTreeGitRepository>>packageDescriptionsFromReadableFileNames > MCFileTreeGitRepository(MCFileBasedRepository)>>retrieveVersionsWithPackageNames: > MCFileTreeGitRepositoryInspector(MCFileRepositoryInspector)>>refresh > MCFileTreeGitRepositoryInspector(MCFileRepositoryInspector)>>setRepository:workingCopy: > in Block: [ ... > BlockClosure>>newProcess in Block: [ ... > > I have loaded both OSProcess and OSWindows , are there other > dependencies on Windows I need to load ? > > > > On Mon, Nov 4, 2013 at 6:46 AM, Tudor Girba <tudor(a)tudorgirba.com > <mailto:tudor@tudorgirba.com>> wrote: > > Exactly. This would be a valuable contribution. Screencasts would be > very helpful as well. > > Doru > > > > > On Mon, Nov 4, 2013 at 12:04 AM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr <mailto:stephane.ducasse@inria.fr>> wrote: > > one of you should write a blog entry on Git support and the > process :) > Because we will get this repeat that often. > > Stef > > > > On Nov 3, 2013, at 2:11 PM, kilon alios <kilon.alios(a)gmail.com > <mailto:kilon.alios@gmail.com>> wrote: > >> ok it was my bad, i had not correctly initialized my git repo. >> Now it works fine. Thanks for the help this awesome. >> >> >> On Sun, Nov 3, 2013 at 2:56 PM, kilon alios >> <kilon.alios(a)gmail.com <mailto:kilon.alios@gmail.com>> wrote: >> >> I installed OSProcess but I get a new Error : Git Error : >> bad default revision 'Head' >> >> just to clarify i try to commit to an existing git repo >> that I have create manually via terminal. >> >> >> MCFileTreeGitRepository(Object)>>error: >> MCFileTreeGitRepository>>gitVersions >> MCFileTreeGitRepository>>loadAncestry >> MCFileTreeGitRepository>>loadAllFileNames in Block: [ :bar >> | ... >> BlockClosure>>cull: >> Job>>run in Block: [ result := block cull: self ] >> BlockClosure>>on:do: >> Job>>run in Block: [ ... >> BlockClosure>>ensure: >> Job>>run >> MorphicUIManager(UIManager)>>displayProgress:from:to:during: >> ByteString(String)>>displayProgressFrom:to:during: >> MCFileTreeGitRepository>>loadAllFileNames >> MCFileTreeGitRepository>>allFileNames >> MCFileTreeGitRepository>>readableFileNames >> MCFileTreeGitRepository(MCFileTreeRepository)>>allFileNamesForVersionNamed: >> MCFileTreeGitRepository(MCDirectoryRepository)>>includesVersionNamed: >> MCWorkingCopy>>uniqueVersionNameIn: in Block: [ ... >> BlockClosure>>cull: >> Job>>run in Block: [ result := block cull: self ] >> BlockClosure>>on:do: >> Job>>run in Block: [ ... >> BlockClosure>>ensure: >> Job>>run >> MorphicUIManager(UIManager)>>displayProgress:from:to:during: >> ByteString(String)>>displayProgressFrom:to:during: >> MCWorkingCopy>>uniqueVersionNameIn: >> MCWorkingCopy>>newVersionIn: >> MCWorkingCopyBrowser>>basicSaveVersionIn: in Block: [ ... >> WorldState>>runStepMethodsIn: >> >> >> >> On Sun, Nov 3, 2013 at 2:40 PM, GOUBIER Thierry >> <thierry.goubier(a)cea.fr <mailto:thierry.goubier@cea.fr>> >> wrote: >> >> Oh sorry, the OSProcess dependency is missing :( >> >> You can install OSProcess from the configuration >> browser in your Pharo image or, on the command line : >> >> $ pharo Pharo.image config >> http://ss3.gemstone.com/ss/MetaRepoForPharo20 >> ConfigurationOfOSProcess --install=stable >> >> Thierry >> >> ------------------------------------------------------------------------ >> *De :* Pharo-dev [pharo-dev-bounces(a)lists.pharo.org >> <mailto:pharo-dev-bounces@lists.pharo.org>] de la part >> de kilon alios [kilon.alios(a)gmail.com >> <mailto:kilon.alios@gmail.com>] >> *Date d'envoi :* dimanche 3 novembre 2013 13:30 >> >> *Ã :* Pharo Development List >> *Objet :* Re: [Pharo-dev] Github and Pharo >> >> look like it cant find PipeableOSProcess on Macos, any >> idea where I can find this object ? >> >> UndefinedObject(Object)>>doesNotUnderstand: #command: >> MCFileTreeGitRepository>>gitVersions >> MCFileTreeGitRepository>>loadAncestry >> MCFileTreeGitRepository>>loadAllFileNames in Block: [ >> :bar | ... >> BlockClosure>>cull: >> Job>>run in Block: [ result := block cull: self ] >> BlockClosure>>on:do: >> Job>>run in Block: [ ... >> BlockClosure>>ensure: >> Job>>run >> MorphicUIManager(UIManager)>>displayProgress:from:to:during: >> ByteString(String)>>displayProgressFrom:to:during: >> MCFileTreeGitRepository>>loadAllFileNames >> MCFileTreeGitRepository>>allFileNames >> MCFileTreeGitRepository>>readableFileNames >> MCFileTreeGitRepository(MCFileTreeRepository)>>allFileNamesForVersionNamed: >> MCFileTreeGitRepository(MCDirectoryRepository)>>includesVersionNamed: >> MCWorkingCopy>>uniqueVersionNameIn: in Block: [ ... >> BlockClosure>>cull: >> Job>>run in Block: [ result := block cull: self ] >> BlockClosure>>on:do: >> Job>>run in Block: [ ... >> BlockClosure>>ensure: >> Job>>run >> MorphicUIManager(UIManager)>>displayProgress:from:to:during: >> ByteString(String)>>displayProgressFrom:to:during: >> MCWorkingCopy>>uniqueVersionNameIn: >> MCWorkingCopy>>newVersionIn: >> MCWorkingCopyBrowser>>basicSaveVersionIn: in Block: [ ... >> WorldState>>runStepMethodsIn: >> >> >> >> On Sun, Nov 3, 2013 at 12:41 PM, GOUBIER Thierry >> <thierry.goubier(a)cea.fr >> <mailto:thierry.goubier@cea.fr>> wrote: >> >> This is where you use GitFileTree. >> >> GitFileTree will do you the commit, browsing the >> git logs and accessing all versions of your >> package in the git repo (browsing, loading, >> changes with the same GUI and look as a >> smalltalkhub repo). It won't do the push, >> however(*). It will show you the current branch in >> the repo too (**). >> >> For pharo3, GitFileTree is available with: >> >> $ pharo Pharo.image eval --save Gofer new url: >> \'http://smalltalkhub.com/mc/ThierryGoubier/MonticelloFileTree-Git/main\ >> <http://smalltalkhub.com/mc/ThierryGoubier/MonticelloFileTree-Git/main%5C>'\; >> package: \'MonticelloFileTree-Git\'\; load >> >> For pharo2, there is a group named >> 'MonticelloFileTree-Git' in FileTree configuration. >> >> Feel free to ask if you have any questions or >> suggestions on it! >> >> Thierry >> >> (*) It would be easy to do commit + push in one >> go, but, I'm not sure I'd like to do a push each >> time I do a commit. I tend to prefer a push a day. >> Maybe something like a marker in the repository >> inspector to remind me I have something to push? >> (**) It doesn't change branches, and there is no >> support for branches in Monticello... This tend to >> trigger bugs in MC package cache. >> >> ------------------------------------------------------------------------ >> *De :* Pharo-dev >> [pharo-dev-bounces(a)lists.pharo.org >> <mailto:pharo-dev-bounces@lists.pharo.org>] de la >> part de kilon alios [kilon.alios(a)gmail.com >> <mailto:kilon.alios@gmail.com>] >> *Date d'envoi :* dimanche 3 novembre 2013 10:16 >> *Ã :* Pharo Development List >> *Objet :* Re: [Pharo-dev] Github and Pharo >> >> Thank you for your efforts , I have installed >> filetree using the instructions provided in the >> github pages for pharo 3. I was also successful >> into generating the local files for my packages >> that I have inserted to my git folder. I can >> manually git commit and git push them from >> terminal but how I do this from inside >> Monticello-Filetree ? >> >> >> On Sun, Nov 3, 2013 at 9:53 AM, GOUBIER Thierry >> <thierry.goubier(a)cea.fr >> <mailto:thierry.goubier@cea.fr>> wrote: >> >> Hi, >> >> I've used github and work_owned git >> repositories as primary workplaces for more >> than a year. First with FileTree, then I wrote >> GitFileTree to make that process simpler. >> >> Thierry >> ------------------------------------------------------------------------ >> *De :* Pharo-dev >> [pharo-dev-bounces(a)lists.pharo.org >> <mailto:pharo-dev-bounces@lists.pharo.org>] de >> la part de kilon alios [kilon.alios(a)gmail.com >> <mailto:kilon.alios@gmail.com>] >> *Date d'envoi :* samedi 2 novembre 2013 14:59 >> *Ã :* Pharo Development List >> *Objet :* [Pharo-dev] Github and Pharo >> >> So any information on how Pharo can be used >> with Github ? >> >> all I have is this >> >> https://github.com/dalehenrich/FSGit >> >> I dont need much, just basic git pull, push, >> clone, add and rm should do fine for starter. >> >> But of course I am interesting into learning >> what can be done, what is available , who >> needs help with what. Github is something >> really important for me, so I am willing to >> contribute as much I can into bringing Pharo >> closer to it. >> >> My interest is using Github in place of >> smalltalkhub and squeaksource. I was planning >> to implement something like an App Store (not >> the purchase system) for Pharo libraries and >> I would love to use github as a backend to it >> and git of course. >> >> >> >> >> > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > > "Every thing has its own flow" > > -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Nov. 4, 2013

Re: [Pharo-dev] Github and Pharo

by Goubier Thierry

Hi Stef, I don't have a blog ;) yet. But yes, I think I should write things up. Thierry Le 04/11/2013 00:04, StÃ©phane Ducasse a Ã©crit : > one of you should write a blog entry on Git support and the process :) > Because we will get this repeat that often. > > Stef > > > On Nov 3, 2013, at 2:11 PM, kilon alios <kilon.alios(a)gmail.com > <mailto:kilon.alios@gmail.com>> wrote: > >> ok it was my bad, i had not correctly initialized my git repo. Now it >> works fine. Thanks for the help this awesome. >> >> >> On Sun, Nov 3, 2013 at 2:56 PM, kilon alios <kilon.alios(a)gmail.com >> <mailto:kilon.alios@gmail.com>> wrote: >> >> I installed OSProcess but I get a new Error : Git Error : bad >> default revision 'Head' >> >> just to clarify i try to commit to an existing git repo that I >> have create manually via terminal. >> >> >> MCFileTreeGitRepository(Object)>>error: >> MCFileTreeGitRepository>>gitVersions >> MCFileTreeGitRepository>>loadAncestry >> MCFileTreeGitRepository>>loadAllFileNames in Block: [ :bar | ... >> BlockClosure>>cull: >> Job>>run in Block: [ result := block cull: self ] >> BlockClosure>>on:do: >> Job>>run in Block: [ ... >> BlockClosure>>ensure: >> Job>>run >> MorphicUIManager(UIManager)>>displayProgress:from:to:during: >> ByteString(String)>>displayProgressFrom:to:during: >> MCFileTreeGitRepository>>loadAllFileNames >> MCFileTreeGitRepository>>allFileNames >> MCFileTreeGitRepository>>readableFileNames >> MCFileTreeGitRepository(MCFileTreeRepository)>>allFileNamesForVersionNamed: >> MCFileTreeGitRepository(MCDirectoryRepository)>>includesVersionNamed: >> MCWorkingCopy>>uniqueVersionNameIn: in Block: [ ... >> BlockClosure>>cull: >> Job>>run in Block: [ result := block cull: self ] >> BlockClosure>>on:do: >> Job>>run in Block: [ ... >> BlockClosure>>ensure: >> Job>>run >> MorphicUIManager(UIManager)>>displayProgress:from:to:during: >> ByteString(String)>>displayProgressFrom:to:during: >> MCWorkingCopy>>uniqueVersionNameIn: >> MCWorkingCopy>>newVersionIn: >> MCWorkingCopyBrowser>>basicSaveVersionIn: in Block: [ ... >> WorldState>>runStepMethodsIn: >> >> >> >> On Sun, Nov 3, 2013 at 2:40 PM, GOUBIER Thierry >> <thierry.goubier(a)cea.fr <mailto:thierry.goubier@cea.fr>> wrote: >> >> Oh sorry, the OSProcess dependency is missing :( >> >> You can install OSProcess from the configuration browser in >> your Pharo image or, on the command line : >> >> $ pharo Pharo.image config >> http://ss3.gemstone.com/ss/MetaRepoForPharo20 >> ConfigurationOfOSProcess --install=stable >> >> Thierry >> >> ------------------------------------------------------------------------ >> *De :* Pharo-dev [pharo-dev-bounces(a)lists.pharo.org >> <mailto:pharo-dev-bounces@lists.pharo.org>] de la part de >> kilon alios [kilon.alios(a)gmail.com <mailto:kilon.alios@gmail.com>] >> *Date d'envoi :* dimanche 3 novembre 2013 13:30 >> >> *Ã :* Pharo Development List >> *Objet :* Re: [Pharo-dev] Github and Pharo >> >> look like it cant find PipeableOSProcess on Macos, any idea >> where I can find this object ? >> >> UndefinedObject(Object)>>doesNotUnderstand: #command: >> MCFileTreeGitRepository>>gitVersions >> MCFileTreeGitRepository>>loadAncestry >> MCFileTreeGitRepository>>loadAllFileNames in Block: [ :bar | ... >> BlockClosure>>cull: >> Job>>run in Block: [ result := block cull: self ] >> BlockClosure>>on:do: >> Job>>run in Block: [ ... >> BlockClosure>>ensure: >> Job>>run >> MorphicUIManager(UIManager)>>displayProgress:from:to:during: >> ByteString(String)>>displayProgressFrom:to:during: >> MCFileTreeGitRepository>>loadAllFileNames >> MCFileTreeGitRepository>>allFileNames >> MCFileTreeGitRepository>>readableFileNames >> MCFileTreeGitRepository(MCFileTreeRepository)>>allFileNamesForVersionNamed: >> MCFileTreeGitRepository(MCDirectoryRepository)>>includesVersionNamed: >> MCWorkingCopy>>uniqueVersionNameIn: in Block: [ ... >> BlockClosure>>cull: >> Job>>run in Block: [ result := block cull: self ] >> BlockClosure>>on:do: >> Job>>run in Block: [ ... >> BlockClosure>>ensure: >> Job>>run >> MorphicUIManager(UIManager)>>displayProgress:from:to:during: >> ByteString(String)>>displayProgressFrom:to:during: >> MCWorkingCopy>>uniqueVersionNameIn: >> MCWorkingCopy>>newVersionIn: >> MCWorkingCopyBrowser>>basicSaveVersionIn: in Block: [ ... >> WorldState>>runStepMethodsIn: >> >> >> >> On Sun, Nov 3, 2013 at 12:41 PM, GOUBIER Thierry >> <thierry.goubier(a)cea.fr <mailto:thierry.goubier@cea.fr>> wrote: >> >> This is where you use GitFileTree. >> >> GitFileTree will do you the commit, browsing the git logs >> and accessing all versions of your package in the git repo >> (browsing, loading, changes with the same GUI and look as >> a smalltalkhub repo). It won't do the push, however(*). It >> will show you the current branch in the repo too (**). >> >> For pharo3, GitFileTree is available with: >> >> $ pharo Pharo.image eval --save Gofer new url: >> \'http://smalltalkhub.com/mc/ThierryGoubier/MonticelloFileTree-Git/main\ >> <http://smalltalkhub.com/mc/ThierryGoubier/MonticelloFileTree-Git/main%5C>'\; >> package: \'MonticelloFileTree-Git\'\; load >> >> For pharo2, there is a group named >> 'MonticelloFileTree-Git' in FileTree configuration. >> >> Feel free to ask if you have any questions or suggestions >> on it! >> >> Thierry >> >> (*) It would be easy to do commit + push in one go, but, >> I'm not sure I'd like to do a push each time I do a >> commit. I tend to prefer a push a day. Maybe something >> like a marker in the repository inspector to remind me I >> have something to push? >> (**) It doesn't change branches, and there is no support >> for branches in Monticello... This tend to trigger bugs in >> MC package cache. >> >> ------------------------------------------------------------------------ >> *De :* Pharo-dev [pharo-dev-bounces(a)lists.pharo.org >> <mailto:pharo-dev-bounces@lists.pharo.org>] de la part de >> kilon alios [kilon.alios(a)gmail.com >> <mailto:kilon.alios@gmail.com>] >> *Date d'envoi :* dimanche 3 novembre 2013 10:16 >> *Ã :* Pharo Development List >> *Objet :* Re: [Pharo-dev] Github and Pharo >> >> Thank you for your efforts , I have installed filetree >> using the instructions provided in the github pages for >> pharo 3. I was also successful into generating the local >> files for my packages that I have inserted to my git >> folder. I can manually git commit and git push them from >> terminal but how I do this from inside Monticello-Filetree ? >> >> >> On Sun, Nov 3, 2013 at 9:53 AM, GOUBIER Thierry >> <thierry.goubier(a)cea.fr <mailto:thierry.goubier@cea.fr>> >> wrote: >> >> Hi, >> >> I've used github and work_owned git repositories as >> primary workplaces for more than a year. First with >> FileTree, then I wrote GitFileTree to make that >> process simpler. >> >> Thierry >> ------------------------------------------------------------------------ >> *De :* Pharo-dev [pharo-dev-bounces(a)lists.pharo.org >> <mailto:pharo-dev-bounces@lists.pharo.org>] de la part >> de kilon alios [kilon.alios(a)gmail.com >> <mailto:kilon.alios@gmail.com>] >> *Date d'envoi :* samedi 2 novembre 2013 14:59 >> *Ã :* Pharo Development List >> *Objet :* [Pharo-dev] Github and Pharo >> >> So any information on how Pharo can be used with Github ? >> >> all I have is this >> >> https://github.com/dalehenrich/FSGit >> >> I dont need much, just basic git pull, push, clone, >> add and rm should do fine for starter. >> >> But of course I am interesting into learning what can >> be done, what is available , who needs help with what. >> Github is something really important for me, so I am >> willing to contribute as much I can into bringing >> Pharo closer to it. >> >> My interest is using Github in place of smalltalkhub >> and squeaksource. I was planning to implement >> something like an App Store (not the purchase system) >> for Pharo libraries and I would love to use github as >> a backend to it and git of course. >> >> >> >> >> > -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Nov. 4, 2013

Re: [Pharo-dev] Peek

by Sven Van Caekenberghe

Hi Diego, Streams as they are currently defined, especially ReadStreams, can hardly be called IO streams. Many operations assume that there is a single collection over which you can move in any direction without restrictions. As a consequence most parsing code relies this ability, looking forward and going back multiple times, like using #skip: with a negative argument. Real IO ReadStreams like a SocketStreams or FileStreams cannot be assumed to keep more than just a buffer in memory, hence the unrestricted operations are not implementable. IMO, parsing code should be written against a much more restricted API, assuming at most a one element peek/buffer. I always try to do that, I even have Mock ReadStreams that ensure this. While benchmarking I have also found that slow #peek behaviour can be a bottleneck, especially on some of the more complex streams. Sven PS: Have a look at ZnCharacterReadStream for example, which implements this restricted behaviour: it is not positionable, but allows a one character peek using a one character internal buffer. On 04 Nov 2013, at 09:57, Diego Lont <diego.lont(a)delware.nl> wrote: > Working on Petit Delphi we found a strange implementation for asPetitStream: > Stream>asPetitStream > ^ self contents asPetitStream > > Further investigation showed that the basic peek was not fast enough for Petit Parser, as it is used a lot. So it implemented a "improved unchecked peek": > PPStream>peek > "An improved version of peek, that is slightly faster than the built in version." > ^ self atEnd ifFalse: [ collection at: position + 1 ] > > PPStream>uncheckedPeek > "An unchecked version of peek that throws an error if we try to peek over the end of the stream, even faster than #peek." > ^ collection at: position + 1 > > But in my knowledge a basic peek should be fast. The real problem is the peek in the underlying peek: > PositionableStream>peek > "Answer what would be returned if the message next were sent to the > receiver. If the receiver is at the end, answer nil." > > | nextObject | > self atEnd ifTrue: [^nil]. > nextObject := self next. > position := position - 1. > ^nextObject > > That actually uses "self next". The least thing one should do is to cache the next object. But isn't there a primitive for peek in a file stream? Because al overriding peeks of PositionableStream have basically the same implementation: reading the next and restoring the state to before the peek (that is slow). So we would like to be able to remove PPStream without causing performance issues, as the only added method is the "improved peek". > > Stephan and Diego

Nov. 4, 2013