February 2014 - Pharo-dev - lists.pharo.org

[OT] Esteban Lorenzano's interview published!

by Nicolas Petton

Hi! This is the second post of my series of interviews, in which I interview my colleagues of RMoD in Lille. This time Esteban accepted to play the game, and the interview is online here: http://nicolas-petton.fr/blog/interview-esteban.html Cheers! Nico -- Nicolas Petton http://nicolas-petton.fr

Feb. 6, 2014

Re: [Pharo-dev] What will change in Pharo with Spur the new Cog memory manager ...

by Sven Van Caekenberghe

Thanks ClÃ©ment, for the blog post and for taking care. The future sure looks exciting. On 06 Feb 2014, at 15:48, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > Hello pharoers, > > The new Cog memory manager, Spur, is simply *amazing*. I saw at FOSDEM that some of you were interested in it, but unfortunately you were lacking information about it. > > I wrote a one page article that sums up Spur's new features so every one can know what will be better. There's no VM technical details here, it's just about what will change for a regular pharo user. > > http://clementbera.wordpress.com/2014/02/06/7-points-summary-of-the-spur-me… > > Let me know if you think I forgot yet another feature. > > If you have questions, I'll try to answer, but ask Eliot, he implemented Spur so he can answer your questions much better than I can :-). > > Regards, > > ClÃ©ment

Feb. 6, 2014

[pharo-project/pharo-core] 2254ec: 30746

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 2254ec3643dba0c387cc9a301b6d52866b913a68 https://github.com/pharo-project/pharo-core/commit/2254ec3643dba0c387cc9a30… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-02-06 (Thu, 06 Feb 2014) Changed paths: M ConfigurationCommandLineHandler-Core.package/ConfigurationCommandLineHandler.class/README.md M ConfigurationCommandLineHandler-Tests.package/ConfigurationCommandLineHandlerTest.class/README.md M Monticello.package/MCChangeSelectionRequest.class/README.md M Monticello.package/MCClassTraitDefinition.class/README.md M Monticello.package/MCDictionaryRepository.class/README.md M Monticello.package/MCDiffyVersion.class/README.md M Monticello.package/MCDirectoryRepository.class/README.md M Monticello.package/MCDirtyPackageInfo.class/README.md M Monticello.package/MCEmptyPackageInfo.class/README.md M Monticello.package/MCFileBasedRepository.class/README.md M Monticello.package/MCFilteredVersionSorter.class/README.md M Monticello.package/MCFrontier.class/README.md M Monticello.package/MCMcdReader.class/README.md M Monticello.package/MCMcdWriter.class/README.md M Monticello.package/MCMczReader.class/README.md M Monticello.package/MCMczWriter.class/README.md M Monticello.package/MCMergeRecord.class/README.md M Monticello.package/MCMergeResolutionRequest.class/README.md M Monticello.package/MCMock.class/README.md M Monticello.package/MCMockAPoolDictionary.class/README.md M Monticello.package/MCMockDefinition.class/README.md M Monticello.package/MCMockDependentItem.class/README.md M Monticello.package/MCNoChangesException.class/README.md M Monticello.package/MCPostscriptDefinition.class/README.md M Monticello.package/MCPreambleDefinition.class/README.md M Monticello.package/MCReader.class/README.md M Monticello.package/MCRemovalPostscriptDefinition.class/README.md M Monticello.package/MCRemovalPreambleDefinition.class/README.md M Monticello.package/MCRepository.class/README.md M Monticello.package/MCScriptDefinition.class/README.md M Monticello.package/MCServerRegistry.class/README.md M Monticello.package/MCVersion.class/README.md M Monticello.package/MCVersionDependency.class/README.md M Monticello.package/MCVersionMerger.class/README.md M Monticello.package/MCVersionNameAndMessageRequest.class/README.md M Monticello.package/MCVersionNotification.class/README.md M Monticello.package/MCVersionReader.class/README.md M Monticello.package/MCVersionSorter.class/README.md M Monticello.package/MCWriter.class/README.md M OpalCompiler-Core.package/OCASTSemanticAnalyzer.class/instance/visitor/visitSequenceNode_.st M OpalCompiler-Core.package/OCUninitializedVariableWarning.class/instance/correcting/openMenuIn_.st M OpalCompiler-Core.package/OCUnknownSelectorWarning.class/instance/correcting/openMenuIn_.st A OpalCompiler-Core.package/OCUnknownSelectorWarning.class/instance/correcting/replaceSelectorTextTo_.st M OpalCompiler-Core.package/OCUnusedVariableWarning.class/instance/correcting/defaultAction.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script399.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30746.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 30746 12514 OCSemanticWarnings ignore "cancel" from a confirmation dialog https://pharo.fogbugz.com/f/cases/12514 12824 Class comment missing for package ConfigurationCommandLineHandler https://pharo.fogbugz.com/f/cases/12824 12512 SemanticAnalyzer ignores answer from UnknownSelectorWarning https://pharo.fogbugz.com/f/cases/12512 12442 Nautilus brakes code when removing more than one unused local variables https://pharo.fogbugz.com/f/cases/12442 12823 Class comment missing in Monticello package https://pharo.fogbugz.com/f/cases/12823 http://files.pharo.org/image/30/30746.zip

Feb. 6, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/30746 Home: https://github.com/pharo-project/pharo-core

Feb. 6, 2014

Re: [Pharo-dev] how does zip filesystem work?

by Max Leske

Yeah I knowâ¦ Itâs all just one big hack at the moment (Iâm not particularly proud of #binaryReadStream eitherâ¦). Again: letâs hope that XStreams will solve all our problems :) On 06.02.2014, at 15:33, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 06 Feb 2014, at 15:30, Max Leske <maxleske(a)gmail.com> wrote: > >> No, not my bug :) >> >> The problem seems to be that WriteStream expects #size to be implemented but MemoryFileSystemFile only knows #fileSize. Apart from that I think it would work. > > But again, this is a problem (of the (G)Zip implementation) regarding the stream API. Certain stream, like network or serial streams, cannot respond to size in all conditions. > >> Add this to MemoryFileSystemFile (not as a final solution!): >> >> size >> ^ bytes size >> >> Cheers, >> Max >> >> On 06.02.2014, at 15:22, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >>> Thanks, Max. >>> >>> Doru >>> >>> >>> On Thu, Feb 6, 2014 at 3:11 PM, Max Leske <maxleske(a)gmail.com> wrote: >>> On 06.02.2014, at 15:07, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> >>>> I am trying to get the ZipFileSystem to work, but I cannot quite manage it. >>>> >>>> I am doing this: >>>> (FileSystem zip: >>>> (FileSystem disk workingDirectory / 'sample.zip')) >>>> open >>>> >>>> and I get an error. >>>> >>>> The error comes from the fact that the code uses readStreamDo: which does not work anymore with binary streams. I tried to use binaryReadStreamDo:, but that crashes in another place. >>>> >>>> I think this is a bug. Or am I doing something wrong? >>> >>> You shouldnât beâ¦ Iâll take a look later since that would be me who introduced the bug (probably). >>> >>>> >>>> Cheers, >>>> Doru >>>> >>>> -- >>>> www.tudorgirba.com >>>> >>>> "Every thing has its own flow" >>> >>> >>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "Every thing has its own flow" >> > >

Feb. 6, 2014

What will change in Pharo with Spur the new Cog memory manager ...

by ClÃ©ment Bera

Hello pharoers, The new Cog memory manager, Spur, is simply *amazing*. I saw at FOSDEM that some of you were interested in it, but unfortunately you were lacking information about it. I wrote a one page article that sums up Spur's new features so every one can know what will be better. There's no VM technical details here, it's just about what will change for a regular pharo user. http://clementbera.wordpress.com/2014/02/06/7-points-summary-of-the-spur-me… Let me know if you think I forgot yet another feature. If you have questions, I'll try to answer, but ask Eliot, he implemented Spur so he can answer your questions much better than I can :-). Regards, ClÃ©ment

Feb. 6, 2014

Re: [Pharo-dev] how does zip filesystem work?

by Tudor Girba

Ok. I confirm that if I modify the code to use binaryReadStreamDo: and then add the MemoryFileSystemFile>>size method, it works fine. So there were two problems :) In any case, I opened an issue: https://pharo.fogbugz.com/f/cases/12826/Zip-FileSystem-does-not-work Cheers, Doru On Thu, Feb 6, 2014 at 3:30 PM, Max Leske <maxleske(a)gmail.com> wrote: > No, not my bug :) > > The problem seems to be that WriteStream expects #size to be implemented > but MemoryFileSystemFile only knows #fileSize. Apart from that I think it > would work. > > Add this to MemoryFileSystemFile (not as a final solution!): > > size > ^ bytes size > > Cheers, > Max > > On 06.02.2014, at 15:22, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Thanks, Max. > > Doru > > > On Thu, Feb 6, 2014 at 3:11 PM, Max Leske <maxleske(a)gmail.com> wrote: > >> On 06.02.2014, at 15:07, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> I am trying to get the ZipFileSystem to work, but I cannot quite manage >> it. >> >> I am doing this: >> (FileSystem zip: >> (FileSystem disk workingDirectory / 'sample.zip')) >> open >> >> and I get an error. >> >> The error comes from the fact that the code uses readStreamDo: which does >> not work anymore with binary streams. I tried to use binaryReadStreamDo:, >> but that crashes in another place. >> >> I think this is a bug. Or am I doing something wrong? >> >> >> You shouldn't be... I'll take a look later since that would be me who >> introduced the bug (probably). >> >> >> Cheers, >> Doru >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > > -- www.tudorgirba.com "Every thing has its own flow"

Feb. 6, 2014

Re: [Pharo-dev] how does zip filesystem work?

by Sven Van Caekenberghe

On 06 Feb 2014, at 15:30, Max Leske <maxleske(a)gmail.com> wrote: > No, not my bug :) > > The problem seems to be that WriteStream expects #size to be implemented but MemoryFileSystemFile only knows #fileSize. Apart from that I think it would work. But again, this is a problem (of the (G)Zip implementation) regarding the stream API. Certain stream, like network or serial streams, cannot respond to size in all conditions. > Add this to MemoryFileSystemFile (not as a final solution!): > > size > ^ bytes size > > Cheers, > Max > > On 06.02.2014, at 15:22, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> Thanks, Max. >> >> Doru >> >> >> On Thu, Feb 6, 2014 at 3:11 PM, Max Leske <maxleske(a)gmail.com> wrote: >> On 06.02.2014, at 15:07, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >>> I am trying to get the ZipFileSystem to work, but I cannot quite manage it. >>> >>> I am doing this: >>> (FileSystem zip: >>> (FileSystem disk workingDirectory / 'sample.zip')) >>> open >>> >>> and I get an error. >>> >>> The error comes from the fact that the code uses readStreamDo: which does not work anymore with binary streams. I tried to use binaryReadStreamDo:, but that crashes in another place. >>> >>> I think this is a bug. Or am I doing something wrong? >> >> You shouldnât beâ¦ Iâll take a look later since that would be me who introduced the bug (probably). >> >>> >>> Cheers, >>> Doru >>> >>> -- >>> www.tudorgirba.com >>> >>> "Every thing has its own flow" >> >> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >

Feb. 6, 2014

Re: [Pharo-dev] how does zip filesystem work?

by Max Leske

No, not my bug :) The problem seems to be that WriteStream expects #size to be implemented but MemoryFileSystemFile only knows #fileSize. Apart from that I think it would work. Add this to MemoryFileSystemFile (not as a final solution!): size ^ bytes size Cheers, Max On 06.02.2014, at 15:22, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Thanks, Max. > > Doru > > > On Thu, Feb 6, 2014 at 3:11 PM, Max Leske <maxleske(a)gmail.com> wrote: > On 06.02.2014, at 15:07, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> I am trying to get the ZipFileSystem to work, but I cannot quite manage it. >> >> I am doing this: >> (FileSystem zip: >> (FileSystem disk workingDirectory / 'sample.zip')) >> open >> >> and I get an error. >> >> The error comes from the fact that the code uses readStreamDo: which does not work anymore with binary streams. I tried to use binaryReadStreamDo:, but that crashes in another place. >> >> I think this is a bug. Or am I doing something wrong? > > You shouldnât beâ¦ Iâll take a look later since that would be me who introduced the bug (probably). > >> >> Cheers, >> Doru >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Feb. 6, 2014

Re: [Pharo-dev] how does zip filesystem work?

by Tudor Girba

Thanks, Max. Doru On Thu, Feb 6, 2014 at 3:11 PM, Max Leske <maxleske(a)gmail.com> wrote: > On 06.02.2014, at 15:07, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > I am trying to get the ZipFileSystem to work, but I cannot quite manage it. > > I am doing this: > (FileSystem zip: > (FileSystem disk workingDirectory / 'sample.zip')) > open > > and I get an error. > > The error comes from the fact that the code uses readStreamDo: which does > not work anymore with binary streams. I tried to use binaryReadStreamDo:, > but that crashes in another place. > > I think this is a bug. Or am I doing something wrong? > > > You shouldn't be... I'll take a look later since that would be me who > introduced the bug (probably). > > > Cheers, > Doru > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > > -- www.tudorgirba.com "Every thing has its own flow"

Feb. 6, 2014