May 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] What is a ExclusiveWeakMessageSend?

by stephane ducasse

thanks Yes we saw that with alain that it is was used in diff and I will add a comment soemhwere. Stef On May 23, 2013, at 1:57 PM, Gary Chambers <gazzaguru2(a)btinternet.com> wrote: > Hi, > It is used in DiffMorph so that the two text panes have their scrolling synchronised > without infinite recursion (scroll source pane, dest pane matches (and exclusive prevents source pane being told to match dest pane etc.)). > > Regards, Gary > > ----- Original Message ----- From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> > To: "Discusses Development of Pharo" <pharo-dev(a)lists.pharo.org> > Sent: Thursday, May 23, 2013 9:04 AM > Subject: [Pharo-dev] What is a ExclusiveWeakMessageSend? > > > Hi Gary > > We are working with alain on removing all the triggering event facilities from Object and porting it to announcement. > Now I was wondering what is the ExclusiveWeakMessageSend. > > Stef >

May 23, 2013

Re: [Pharo-dev] DND refactoring

by stephane ducasse

did you check the smart suggestions :) Stef On May 23, 2013, at 1:35 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: > Yun Young Lee recently did a talk on improvements in refactoring UI. > > https://wiki.engr.illinois.edu/display/cs599yyl/DNDRefactoring > > It has a nice demo video. It looks like something that could help > reduce the current menu complexity. > > Stephan > >

May 23, 2013

Re: [Pharo-dev] Latest vm on Ubuntu 8.04.4 LTS

by Dale K. Henrichs

Sven, I know what you are talking about. Frankly I make an effort to ensure that the latest version of Metacello continues to run on older versions of Squeak/Pharo/GemStone because I know that it doesn't always make sense to port perfectly good production apps to the latest version of a platform ... With that said, I did have to "drop support" of Pharo1.0 because I couldn't get it to run on travis:) Dale ----- Original Message ----- | From: "Sven Van Caekenberghe" <sven(a)stfx.eu> | To: "Discusses Development of Pharo" <pharo-dev(a)lists.pharo.org> | Sent: Thursday, May 23, 2013 10:23:26 AM | Subject: Re: [Pharo-dev] Latest vm on Ubuntu 8.04.4 LTS | | | On 23 May 2013, at 19:15, Norbert Hartl <norbert(a)hartl.name> wrote: | | > Am 23.05.2013 um 18:41 schrieb Sven Van Caekenberghe | > <sven(a)stfx.eu>: | > | >> BTW, 8.04 expired just 2 weeks ago, and Pharo 2.0 was released | >> before that ;-) | > | > The LTS support expired two weeks ago. LTS does mostly include | > security fixes not kernel backports. So installing your 08.04 on a | > modern machine might not work. And installing the newest virtual | > machine inside 08.04. might not work either. You should stay with | > old stuff :) | > | > Norbert | | I feel old ;-) | | No seriously, it is really strange how these things evolve: one day | you install a production machine and then you are happy that it | keeps on running fine for months and months and then years and | years, and then suddenly you no longer dare to upgrade or reboot it. | Especially for systems that are required to run 24/7/365. | | Sven |

May 23, 2013

Re: [Pharo-dev] Latest vm on Ubuntu 8.04.4 LTS

by Norbert Hartl

Why should they be better suited for "those long term things"? Norbert Am 23.05.2013 um 20:10 schrieb "phil(a)highoctane.be" <phil(a)highoctane.be>: > CentOS may be a better bet for those long term things. > > http://centos.org/modules/tinycontent/index.php?id=5 > > Or pure Debian http://en.wikipedia.org/wiki/Debian (Chart at the bottom) > > I am now using Debian for my own stuff FWIW. > > Phil > > > On Thu, May 23, 2013 at 7:23 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> On 23 May 2013, at 19:15, Norbert Hartl <norbert(a)hartl.name> wrote: >> >> > Am 23.05.2013 um 18:41 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: >> > >> >> BTW, 8.04 expired just 2 weeks ago, and Pharo 2.0 was released before that ;-) >> > >> > The LTS support expired two weeks ago. LTS does mostly include security fixes not kernel backports. So installing your 08.04 on a modern machine might not work. And installing the newest virtual machine inside 08.04. might not work either. You should stay with old stuff :) >> > >> > Norbert >> >> I feel old ;-) >> >> No seriously, it is really strange how these things evolve: one day you install a production machine and then you are happy that it keeps on running fine for months and months and then years and years, and then suddenly you no longer dare to upgrade or reboot it. Especially for systems that are required to run 24/7/365. >> >> Sven >

May 23, 2013

Corrupt BlockClosure

by Max Leske

Hi Marcus Roberto sent this mail to the Fuel-dev list. When we looked at the problem we noticed that serialization fails because of a corrupt BlockClosure. Since that's not really our territorry Mariano suggested to forward this to you. The image with the corrupt BlockClosure is available here: https://dl.dropboxusercontent.com/u/6281855/DFlow-SubscriptOutOfBounds.zip. To see the stack, right click on the only entry in the right window and click "export session". You'll find the corrupt BlockClosure at BlockClosure>>fuelAccept: @Roberto Is it possible to reproduce the stack with a new session? Or did this only happen once? Cheers, Max Begin forwarded message: > From: Mariano Martinez Peck <marianopeck(a)gmail.com> > Subject: Re: [Pharo-fuel] [Fuel] SubscriptOutOfBounds: 27 > Date: 23. Mai 2013 14:23:45 MESZ > To: The Fuel Project <pharo-fuel(a)lists.gforge.inria.fr> > Reply-To: The Fuel Project <pharo-fuel(a)lists.gforge.inria.fr> > > Indeed, it would be nice if you can known which CompiledMethod and blockclosure are having the problem. Not only the source code but the real bytecodes. > Also, can you isolate and just try to serialize them alone and reproduce the problem? In other words, a reproducible test case? :) > Thanks! > > > On Thu, May 23, 2013 at 8:41 AM, Max Leske <maxleske(a)gmail.com> wrote: > What's the compiled method? Is it a special one? Which selector in which class? > > Max > > On 23.05.2013, at 12:45, "roberto.minelli(a)usi.ch" <roberto.minelli(a)usi.ch> wrote: > > > Hi, > > > > While using Fuel in a 2.0 image to serialize some objects (including CompiledMethods) I'm getting this error: SubscriptOutOfBounds: 27. > > > > I spent hours in the debugger before writing this email, but I'm not able to figure out why this is happening. I attach the full stack of the error (STACK#1). > > > > I understood that it has something to do with a particular CompiledMethod in my image and/or a BlockClosure which for some reason cannot be printed (i.e., the printString returns <error in printString: evaluate "self printString" to debug>) and when I try to printString to debug I got the STACK#2 which in turn does not bring me to any possible solution. > > > > Hope some of you will have an intuition on that or at least tell me where to look or how to script a possible workaround. > > > > Thanks in advance, > > Roby > > > > ############################################################################################ > > ######################################### STACK#1 ########################################### > > ########################################################################################### > > CompiledMethod(Object)>>errorSubscriptBounds: > > CompiledMethod(Object)>>at: > > InstructionStream>>interpretNextInstructionFor: > > CompiledMethod>>abstractBytecodeMessageAt: in Block: [(InstructionStream new method: self pc: pc)... > > BlockClosure>>on:do: > > CompiledMethod>>abstractBytecodeMessageAt: > > BlockClosure>>blockCreationBytecodeMessage > > BlockClosure>>endPC > > BlockClosure>>abstractBytecodeMessagesDo: > > BlockClosure>>isClean > > BlockClosure>>shouldBeSubstitutedByCleanCopy > > BlockClosure>>fuelAccept: > > FLFullGeneralMapper(FLLightGeneralMapper)>>mapAndTrace: > > FLFullGlobalMapper>>mapAndTrace: in Block: [(anObject class == CompiledMethod... > > FLLargeIdentityDictionary>>at:ifAbsent: > > FLFullGlobalMapper>>mapAndTrace: > > FLPluggableSubstitutionMapper>>mapAndTrace: > > FLPluggableSubstitutionMapper>>mapAndTrace: > > FLAnalysis>>mapAndTrace: > > FLAnalysis>>run > > FLAnalyzer>>setDefaultAnalysis in Block: [:anObject | (FLAnalysis... > > FLAnalyzer>>analysisFor: > > FLSerialization>>analysisStep > > FLSerialization>>run > > DFSerializer(FLSerializer)>>setDefaultSerialization in Block: [:anObject :anEncoder | (FLSerialization... > > DFSerializer(FLSerializer)>>serialize:on: in Block: [:anEncoder | ... > > FLEncoder class>>on:globalEnvironment:do: in Block: [aBlock value: anEncoder] > > BlockClosure>>ensure: > > FLEncoder class>>on:globalEnvironment:do: > > DFSerializer(FLSerializer)>>serialize:on: > > > > > > ############################################################################################ > > ######################################### STACK#2 ########################################### > > ############################################################################################ > > Decompiler(Object)>>error: > > Decompiler>>decompileBlock: > > BlockClosure>>decompile > > BlockClosure>>printOn: > > BlockClosure(Object)>>printStringLimitedTo: in Block: [:s | self printOn: s] > > String class(SequenceableCollection class)>>streamContents:limitedTo: > > BlockClosure(Object)>>printStringLimitedTo: > > BlockClosure(Object)>>printString > > BlockClosure>>DoIt > > Compiler>>evaluate:in:to:notifying:ifFail:logged: > > SmalltalkEditor>>evaluateSelectionAndDo: in Block: [rcvr class evaluatorClass new... > > BlockClosure>>on:do: > > SmalltalkEditor>>evaluateSelectionAndDo: > > SmalltalkEditor>>evaluateSelection > > PluggableTextMorph>>doIt in Block: [textMorph editor evaluateSelection] > > PluggableTextMorph>>handleEdit: in Block: [result := editBlock value] > > TextMorphForEditView(TextMorph)>>handleEdit: > > PluggableTextMorph>>handleEdit: > > PluggableTextMorph>>doIt > > SmalltalkEditor class>>buildSmalltalkEditorKeymappingsOn: in Block: [:morph | morph doIt] > > BlockClosure>>cull: > > BlockClosure>>cull:cull: > > BlockClosure>>cull:cull:cull: > > KMCategoryTarget>>completeMatch:buffer: > > KMKeymap>>notifyCompleteMatchTo:buffer: in Block: [:l | l completeMatch: self buffer: aBuffer] > > Array(SequenceableCollection)>>do: > > KMKeymap>>notifyCompleteMatchTo:buffer: > > KMKeymap>>onMatchWith:notify:andDo: > > KMCategory>>onMatchWith:notify:andDo: in Block: [:entry | entry... > > Set>>do: > > > > > > > > _______________________________________________ > > Pharo-fuel mailing list > > Pharo-fuel(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-fuel > > _______________________________________________ > Pharo-fuel mailing list > Pharo-fuel(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-fuel > > > > -- > Mariano > http://marianopeck.wordpress.com > _______________________________________________ > Pharo-fuel mailing list > Pharo-fuel(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-fuel

May 23, 2013

Video: The Moose Roadmap

by Stephan Eggermont

Another video from the MooseDay2013 Tudor Girba showing the Moose roadmap http://www.youtube.com/watch?v=2JCDS3OVnGM Stephan

May 23, 2013

Re: [Pharo-dev] Latest vm on Ubuntu 8.04.4 LTS

by kilon

You are not old, this the reality of modern software 1% innovation / improvement, 99% annoyance . And its definitely not just you and me. -- View this message in context: http://forum.world.st/Pharo-dev-Latest-vm-on-Ubuntu-8-04-4-LTS-tp4689467p46… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

May 23, 2013

Re: [Pharo-dev] Halt subclass: #AssertionFailure

by ClÃ©ment Bera

Did you check the latest SUnit version before doing that ? I think it is not integrated yet in Pharo. 2013/5/23 Camillo Bruni <camillobruni(a)gmail.com> > > On 2013-05-23, at 16:37, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > > > On 23 May 2013, at 16:34, Camillo Bruni <camillobruni(a)gmail.com> wrote: > > > >> > >> On 2013-05-23, at 16:26, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> > >>> > >>> On 23 May 2013, at 15:59, Camillo Bruni <camillobruni(a)gmail.com> > wrote: > >>> > >>>> why? To me this does not make sense. I'd expect > >>>> > >>>> Error subclass: #AssertionFailure > >>> > >>> Yeah, I have asked myself the same question quite often. > >>> > >>> I often write self assert: <some condition> in production code, but > then an #on:do: handler specifying only Error won't catch the > AssertionFailure exceptions. > >> > >> exactly! I'm going to propose a fix, because I hate to write > Error,AssertionFailure :P > >> > >>> I would guess it has something to do with SUnit logic ? > >> > >> > >> Must be some strange leftover, since in interactive mode there is no > distinction between Halt and any other Error. > > > > But doesn't TestRunner react differently on AssertionError as opposed to > other Errors ? The former are called 'Failures', the latter 'Errors'... > > I just checked. Using Halt and AssertionFailures directly in a test does > mark the test as a failure, but it doesn't change anything on the existing > #assert: inside testcases directly. > > Before: > RBFormatterTests>>#testHalt > Halt > RBFormatterTests>>#testAssertionFailure > AssertionFailure > RBFormatterTests>>#testAssert TestFailure: Assertion > failed > > After: > RBFormatterTests>>#testHalt > Halt > RBFormatterTests>>#testAssertionFailure > AssertionFailure > RBFormatterTests>>#testAssert TestFailure: Assertion > failed > > The only difference is in UI mode, when there is an AssertionFailure the > test > wasn't immediately marked RED. IMO this is not correct, as a failing > assertion > anywhere outside the code is an Error. But that was the case before (on > the command line). > > So I would apply this change and maybe improve SUnit to deal with > AssertionFailures > from outside TestCases > -- ClÃ©ment BÃ©ra Mate Virtual Machine Engineer BÃ¢timent B 40, avenue Halley 59650 *Villeneuve d'Ascq*

May 23, 2013

Re: [Pharo-dev] Latest vm on Ubuntu 8.04.4 LTS

by phil＠highoctane.be

CentOS may be a better bet for those long term things. http://centos.org/modules/tinycontent/index.php?id=5 Or pure Debian http://en.wikipedia.org/wiki/Debian (Chart at the bottom) I am now using Debian for my own stuff FWIW. Phil On Thu, May 23, 2013 at 7:23 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 23 May 2013, at 19:15, Norbert Hartl <norbert(a)hartl.name> wrote: > > > Am 23.05.2013 um 18:41 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > > > >> BTW, 8.04 expired just 2 weeks ago, and Pharo 2.0 was released before > that ;-) > > > > The LTS support expired two weeks ago. LTS does mostly include security > fixes not kernel backports. So installing your 08.04 on a modern machine > might not work. And installing the newest virtual machine inside 08.04. > might not work either. You should stay with old stuff :) > > > > Norbert > > I feel old ;-) > > No seriously, it is really strange how these things evolve: one day you > install a production machine and then you are happy that it keeps on > running fine for months and months and then years and years, and then > suddenly you no longer dare to upgrade or reboot it. Especially for systems > that are required to run 24/7/365. > > Sven >

May 23, 2013

Re: [Pharo-dev] MC Filetree -- missing FiletreeURL ?

by Frank Shearar

On 23 May 2013 07:01, stephane ducasse <stephane.ducasse(a)free.fr> wrote: >> >> I would _love_ to be able to use Smalltalk at work. Until it can work >> properly with git, and people can use their own text editors (vim, >> emacs, sublime), and quite a few other bits and pieces, it's just a >> non-starter. > > it will happen. I'm sure :) > >> I _like_ Pharo, and I _like_ how it has energy and momentum, and a >> much nicer UI than the old Pharo 1.0 UI. I'm honestly quite jealous of >> the resources the community wields, not just because of INRIA's and >> the Consortium's money, but because there are loads of people actually >> around, who are prepared to knuckle down and do the gruntwork needed. >> Squeak is now a very small community. I'm rather proud of what we get >> done with what little we have. > > Just so that I understand. What are you trying to achieve? I want a minimal Smalltalk with decent modularity semantics. I want decent integration with the standard tools of the trade. I _don't_ want to require special unique snowflake tools to work with my code. Right now I'm breaking up the Squeak Trunk into pieces, unloading things as I go. I hope, at some stage, to end up with some fairly minimal thing that will still allow one to load the main things that Squeak's used for. Colin Putney's Environments work is the main thrust for 4.5, together with the usual cruft removal work. But I see your point about lack of vision, whether perceived or actual. That's something Squeak will have to work on. > Most of the pharo people are not payed for doing pharo. What we are building (and fighting for) is an > ecosystem in which smart guys can also find a job and it is becoming to happen. Mariano is full of work > and many others. Sean told me that he got several job offers. > > Pharo is not the end, it is the start. It is not like we would like it to be but everyday it gets closer to it. That's good to hear. I feel the same way about Squeak, although it's clearly a lot, er, *mossier* than Pharo. frank

May 23, 2013