- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] enclosing compile errors & <PrintIt> in double quotes

by Camillo Bruni

That is the first step :), if you have a decent text editor, you could add a real print-it or do-it token, which is not regarged as source code, but just as meta information. I think we could quite easily do this in Amber right now ;). But yes, why not, sounds like a reasonable idea to put print-its and compilation errors in double quotes. On 2013-10-18, at 14:59, btc(a)openinworld.com wrote: > > Just a random idea flitting thought my mind... When trying to <Accept> some code with an error in it, the error message gets inserted into the code such that it screws up syntax highlighting and also you need to use <Undo> to remove it. I wonder if the error might be inserted between double-quotes making it a comment. The same could be said for if you <PrintIt> from a debugger. It seems such a simple and obvious idea that I presume its been considered before and there are good reasons not to do it. I am curious what others think might be the pros/cons of it. > In the case of <PrintIt> one benefit might be that the code could still be saved, with the result left as a kind-of example. This might be good for temporary code development in a Workspace. > > cheers -ben >

Oct. 18, 2013

Re: [Pharo-dev] recovering from a deep disc crashâ¦.

by Igor Stasenko

On 18 October 2013 12:52, Nicolas Cellier < nicolas.cellier.aka.nice(a)gmail.com> wrote: > Igor, > your hardware never failed? > It must be some special brand crafted in former soviet union ;) > > well, sure i had problems with it, but not at cost of total data loss. couple times its keyboard, mouse, once it was monitor and once is motherboard, but never the hard drive :) > 2013/10/18 Igor Stasenko <siguctua(a)gmail.com> > >> thankfully, i never had problems with hardware: it serves me well. >> But still didn't prevented from losing precious data: the humans who >> break into my apartment and stole the machine, >> with all data it has :( >> >> >> >> On 18 October 2013 11:18, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: >> >>> I remember trying to recover mail folders by reading the blocks on disk >>> one by one with a binary editor... >>> >>> Ended learning far too much about the internal layout of an ext2 >>> filesystem. >>> >>> But dead harddrive is nice in one way: you don't loose time trying to >>> recover stuff, you know it's dead :( >>> >>> Thierry >>> >>> Le 17/10/2013 23:10, StÃ©phane Ducasse a Ã©crit : >>> >>> so backup your machineâ¦ because mine was still working at 8h this >>>> morning and 8h40 dropped dead >>>> >>>> >>>> >>>> >>> -- >>> 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 >>> >>> >> >> >> -- >> Best regards, >> Igor Stasenko. >> > > -- Best regards, Igor Stasenko.

Oct. 18, 2013

Second Scheduler migration from SqS to STHub

by Torsten Bergmann

Hi Hernan, I've seen that you now registered "TaskScheduler" on STHub with the Scheduler code on STHub. But the "Scheduler" project was already migrated to SmalltalkHub, together with a config and documented STHub page: http://smalltalkhub.com/#!/~TorstenBergmann/Scheduler and it is available also in the config browser for Pharo 2.0 since a long time. No need for duplicated effort... Is there a reason you provide it a second time? May I kindly ask that you remove your second copy to avoid confusion. Thanks Torsten

Oct. 18, 2013

Mac VM Maintainer resignation (for the general purpose VM, not for PharoVM)

by Esteban Lorenzano

Hi, This is an announce for VM-dev and Squeak-dev list, Pharo-dev list is copy to keep people informed. Last years I tried to keep a working version of the Mac builds of VM while at the same time trying to keep my job going. It was a hard work but I did my best. When I assumed the responsibility I said that my first task was going to be to automatize the builds and at the same time Igor was doing the same so I joined that effort. Since then the VM is buildable even by the not so good at VM level and I never seen the point in keeping the manual build or the non-smalltalk-generated configuration files. Nevertheless, I preferred to work on the new builds of Eliot than in the old interpreter and when keeping all working became more work that what I could manage, I choose to keep Stack and Cog VM working. Maybe because of that, or because the animosity between communities, or because what I'm doing just does not match Squeak vision, or because since Eliot is providing regular builds mine are not needed, truth is that I've seen my work mostly ignored in squeak community and for some of the people in vm-dev list. That's why I resign as a maintainer. I have a process that does not match squeak vision and is fair for squeak community to look for someone who does. I have no bad feelings, I'm complete grateful to the community for give me the opportunity (specially to John, who thrusted me) and to all the rest. I also know that there is great people both in vm-dev and in squeak-dev, but I cannot your mac-guy anymore (and I think this is obvious since ever). And of course I will continue working in the pharo flavor of VM :) Cheers, Esteban

Oct. 18, 2013

[pharo-project/pharo-core]

by GitHub

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

Oct. 18, 2013

[pharo-project/pharo-core] 3ab076: 30500

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 3ab0764a1658214c915a01509eaaf9aec8e78b17 https://github.com/pharo-project/pharo-core/commit/3ab0764a1658214c915a0150… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-10-18 (Fri, 18 Oct 2013) Changed paths: M Collections-Abstract.package/SequenceableCollection.class/instance/splitjoin/joinUsing_last_.st M CollectionsTests.package/SplitJoinTest.class/instance/running/testJoinUsingLastOnArray.st M MenuRegistration.package/PragmaMenuBuilder.class/instance/menu building/buildTree.st M Morphic-Base.package/ImageMorph.class/instance/geometry/extent_.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script155.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30500.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Inspector.package/EyeMorphViewer.class/class/spec/inspectorSpec.st M Spec-Inspector.package/EyeMorphViewer.class/instance/accessing/container.st M Spec-Inspector.package/EyeMorphViewer.class/instance/event-handling/objectChanged.st A Spec-Inspector.package/EyeMorphViewer.class/instance/initialization/initializePresenter.st R Spec-Inspector.package/EyeMorphViewer.class/instance/initialization/initializeWidgets.st A Spec-Inspector.package/EyeMorphViewer.class/instance/initialize/initialize.st A Spec-Inspector.package/extension/ImageMorph/instance/resize_.st Log Message: ----------- 30500 11835 Cannnot revert <Make uncloseable> https://pharo.fogbugz.com/f/cases/11835 11924 Resize the morph while inspecting it https://pharo.fogbugz.com/f/cases/11924 11915 #joinUsing:last: incorrect for single item collection https://pharo.fogbugz.com/f/cases/11915 http://files.pharo.org/image/30/30500.zip

Oct. 18, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation-M-Z/labe… 1 regressions found. Tests.Release.ReleaseTest.testLocalMethodsOfTheClassShouldNotBeRepeatedInItsTraits

Oct. 18, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation-M-Z/labe… 1 regressions found. Tests.Release.ReleaseTest.testLocalMethodsOfTheClassShouldNotBeRepeatedInItsTraits

Oct. 18, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation-M-Z/labe… 1 regressions found. Tests.Release.ReleaseTest.testLocalMethodsOfTheClassShouldNotBeRepeatedInItsTraits

Oct. 18, 2013

Question about Opal

by Goubier Thierry

Hi Markus, I have an Opal-related question: I want to get the ast of an expression analysed in the context of a particular class... I.e. something like: anAst doSemanticAnalysisIn: aClass. This code works if the ast is a methodNode, but not if this is a simple expression (a MessageNode for instance). I know there is a doSemanticAnalysis (which should work, but probably on the UndefinedObject class). So how do I do that? (in 2.0 and the old compiler, the solution is to do anAst annotateInClass: aClass) Thanks, Thierry -- 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

Oct. 18, 2013