July 2010 - Pharo-dev - lists.pharo.org

[Pharo-project] PharoCore 1.1 comments
by Miguel Enrique CobÃ¡ MartÃnez July 31, 2010

July 31, 2010

Hi all, some things I noticed in PharoCore 1.1 release: - This PharoCore-1.1.zip doesn't include a sources file. It was good to have it included in the zip as before. Can be included for every PharoCore release? - The page says that PharoV10.sources is for use with 1.0, 1.1 and 1.2. Shouldn't be better to have a different one for each release? (even if 1.1 is a copy of 1.0, the different name avoids doubts about numbering scheme): PharoCore-1.0.image PharoCore-1.0.changes PharoV10.sources PharoCore-1.1.image PharoCore-1.1.changes PharoV10.sources (???) ... PharoCore-1.7.image PharoCore-1.7.changes PharoV10.sources (bigger ???) Just a suggestion. ;) - SystemVersion current majorMinorVersion prints: PharoCore 1.0: 'PharoCore1.0' PharoCore 1.1: 'Pharo1.1' Maybe this should be in the script preparing the image so that correctly set the version string for PharoCore images and for Pharo images (or maybe already is there but wasn't executed?) Other than that, the new image is *very* fast! Cheers -- Miguel CobÃ¡ http://miguel.leugim.com.mx

4 3

[Pharo-project] Fwd: [squeak-dev] [ANN] DnsClient: More protocol fun
by StÃ©phane Ducasse July 31, 2010

July 31, 2010

Looks interesting :) > From: Andreas Raab <andreas.raab(a)gmx.de> > Date: July 27, 2010 9:24:16 AM GMT+02:00 > To: The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org> > Subject: [squeak-dev] [ANN] DnsClient: More protocol fun > Reply-To: The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org> > > Folks - > > I just finished another fun little protocol implementation. DnsClient is a client for DNS lookups of all sorts. Why implement the DNS protocol you ask? Well, because 1) it's fun, 2) it's educational, and 3) it's non-blocking. The latter is actually interesting, we've found that occasionally we get very long VM blocking due to synchronous name lookup performed in the Unix socket code. > > You can install DnsClient from Squeaksource: > > (Installer ss project: 'ar') > install: 'DnsClient-Core'; "all the code" > install: 'DnsClient-Tests'; "the tests" > install: 'DnsClient-Hacks'. "use DnsClient when present" > > DnsClient should work well but beware that on Windows it will currently use the deefault fallback name servers (Google DNS and OpenDNS) since I still need to implement the primitive to return the proper resolv.conf content (which is spread out in the Windows registry). Consequently, if you're trying look up local names or if you are behind a firewall, these addresses will fail until I've implemented the primitive proper. > > Cheers, > - Andreas >

1 0

[Pharo-project] Underscores in 1.1??
by Schwab,Wilhelm K July 31, 2010

July 31, 2010

Hello all, Is 1.1 able to handle underscores in method *and* class names? Is this really behind us now? Bill

3 4

[Pharo-project] Object>>doesNotUnderstand:
by Denis Kudriashov July 31, 2010

July 31, 2010

Hello, I found method doesNotUnderstand have very strange implementation Object>>doesNotUnderstand: aMessage | exception resumeValue | (exception := MessageNotUnderstood new) message: aMessage; receiver: self. resumeValue := exception signal. ^exception reachedDefaultHandler ifTrue: [aMessage sentTo: self] ifFalse: [resumeValue] When Error has no handlers #defaultAction is executed. For MessageNotUnderstood #defaultAction is UnhandledError signal. And for UnhandledError #defaultAction is opening debugger. If you change it to do nothing (^self) you get infinite loop on any MessageNotUnderstood signal. It is because "ifTrue" branch executed in doesNotUnderstood method and message resend to receiver. Why method implemented such way? Why it is differ from ProtoObject implementation. I think It's bug implementation. I found this problem when I try implement stuff to turn off openning debugger on unhandled error (and write it to log) UnhandledError>>defaultAction "The current computation is terminated. The cause of the error should be logged or reported to the user. If the program is operating in an interactive debugging environment the computation should be suspended and the debugger activated." ^ToolSet debugError: exception. ToolSet class>>debugError: anError "Handle an otherwise unhandled error" self default ifNil:[ | ctx | Smalltalk logError: anError description inContext: (ctx := anError signalerContext) to: 'PharoDebug.log'. self inform: (anError description, String cr, ctx shortStack). ^anError return]. ^self default debugError: anError I just implement subclass of StandartToolSet with empty method #debugError:. Then I do "ToolSet default: MyToolSet". And now unhandled errors raise infinit loop and never return. I fix that by: MyToolSet>>debugError: anError anError class = MessageNotUnderstand ifTrue: [anError reachedDefaultHandler: true]. I think this is hack. But it is work. No errors show to user.And all work good. What do you think? Best regards, Denis

4 9

[Pharo-project] [ANN] Magma 1.1r2
by Chris Muller July 31, 2010

July 31, 2010

I am pleased to announce a new release of Magma containing my updates since 1.1r1: - All underscore assignments have now been updated to ANSI assignments. - When opening the server, a file called "_open" is created in the repository directory, to indicate the repository is open. The file is deleted when the repository is closed gracefully. This is intended to help protect from accidentally letting two OS processes open the same repository files. - Resurrected MagmaDictionary! It is just like a Dictionary except that it inherits the properties of Magma's LargeCollections, such as size and concurrency. - Added Collection>>#asMagmaArray and MagmaArray>>#add:. - Added check for an additional way to run Squeak in headless mode: the "-vm-display-null" option. - Added MagmaSessionRequest class>>#signalNewReadStrategy: so that domains may signal new ReadStrategies to any listening sessions. - Added MagmaLocalLocation>>#findSession, a convenient counterpart to #newSession that first checks there is already a session open on that location and, if so, use that one. Otherwise, create and answer a new one. - Support for persistent, simple BlockClosures (e.g., with only references to arguments, not "self", any instVars or globals). - Choose automatically between an appropriate MaDictionary subclass, depending on whether the new Weak-Finalization mechanism from Igor is supported. - Several other minor fixes. The following represent the 1.1r2 configuration, in load-dependent order: "Magma client" { 'Collections-BTree-lr.73.mcz'. 'Ma exception handling-cmm.36.mcz'. 'Ma base additions-cmm.174.mcz'. 'MaFixedWidthReport-cmm.7.mcz'. 'Ma Statistics-cmm.24.mcz'. 'Ma files additions-cmm.13.mcz'. 'Ma contextual search-cmm.34.mcz'. 'Ma special collections-cmm.114.mcz'. 'WriteBarrier-cmm.28.mcz'. 'Ma Squeak domain-cmm.34.mcz'. 'Ma proxy support-cmm.42.mcz'. 'Ma traverse object graphs-cmm.31.mcz'. 'Ma object serialization-cmm.234.mcz'. 'Ma client server-cmm.215.mcz'. 'Magma client-cmm.490.mcz' } "for Magma server add" , {'Magma server-cmm.406.mcz'. } "for Magma tester add" , { 'Ma Armored Code-cmm.148.mcz'. 'Ma special collections tester-cmm.14.mcz'. 'Ma object serialization tester-cmm.32.mcz'. 'Magma tester-cmm.367.mcz' } These package versions are available in the "MagmaTester" project of squeaksource.com. - Chris

4 8

Re: [Pharo-project] [Pharo-users] Recent Messages Browser
by Mariano Martinez Peck July 31, 2010

July 31, 2010

On Fri, Jul 30, 2010 at 2:47 AM, Benjamin Van Ryseghem < benjamin.vanryseghem(a)gmail.com> wrote: > Hi everybody, > > > I've rewrited a recent messages browser based on MorphTreeMorph. > > Hi, this is very good idea! > If you can test it and tell me what's do you think about, it will be cool > (I'm a new Smalltalker ^^) > > welcome! > You can download code here : > > Gofer new > squeaksource: 'PharoTaskForces'; > package: 'RecentSubmissions'; > load. > > > To launch it, just click on the World >> Tools >> Recent Messages. > > You can set it up in the Setting Menu >> Code browsing >> Recent Message. > > > Ok...I did it. A few remarks: 1) RecentMessageList >> initialize you do SmalltalkImage current addToStartUpList: self class. but should be SmalltalkImage addToStartUpList: self class. (at least in Pharo 1.1) 2) What is the idea of the Recent Messages? To see the recent MODIFIED methods ? isn't it? If true, maybe would be good to 2.1) directly show the diff with the previous version 2.2) Have a button to see the versions of that method 3) Once you press any button, like collapse all or similar, they become blue and neve grey again 4) When is the list of recen messages clean ? how do you know the recen messages? you store that information somewhere? when is that cleaned? Thank you very much and continue with the good work! Maybe once we can include it by defult in Pharo. Cheers Mariano > > Thank you > > > > Ben > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > >

2 1

[Pharo-project] there are still references to PluggableButtonMorphPlus
by Mariano Martinez Peck July 31, 2010

July 31, 2010

I am in PharoCore 12066 and there are still references to PluggableButtonMorphPlus, which doesn't exist anymore: 1) MorphicToolBuilder >> buttonClass ^ PluggableButtonMorphPlus is it ok to change it to buttonClass ^ PluggableButtonMorph ? 2) UITheme >> newButtonIn: aThemedMorph for: aModel getState: stateSel action: actionSel arguments: args getEnabled: enabledSel getLabel: labelSel help: helpText |b| b := PluggableButtonMorphPlus on: aModel getState: stateSel action: actionSel label: labelSel. .... is it ok to change it to |b| b := PluggableButtonMorph on: aModel getState: stateSel action: actionSel label: labelSel. ? 3) MorphicToolBuilderTests >> expectedFailures "Polymorph override of PluggableButtonMorphPlus>>update: makes color not being updated anymore in respond to sending #changed:. Was this an intentional change and this test is obsolete?" ^ #(testGetButtonColor) I don't know how this one should be. But it should be updated, at least the class name. Thanks Mariano

3 2

[Pharo-project] PluggableThemedOverflowPanelMorph(Object)>>doesNotUnderstand: #statusColor
by Mariano Martinez Peck July 31, 2010

July 31, 2010

Just try open a TestRunner. You will get a DNU and that won't let you even debug the error. Pharo core version: PharoCore-1.2-12061 I attach PharoDebug.log PluggableThemedOverflowPanelMorph(Object)>>doesNotUnderstand: #statusColor Issue: http://code.google.com/p/pharo/issues/detail?id=2717 Cheers Mariano

3 4

[Pharo-project] what about deprecating deprecated: ?
by Mariano Martinez Peck July 31, 2010

July 31, 2010

Hi folks. Yes, I know it sounds weird...but just read We said (don't remember when) that when we deprecate a method, we give a whole release time so that eternal packages can fix they senders. And then in the next release we remove it. For example, in Pharo 1.1 we deprecate the methodX. Then, in Pharo 1.2, we should remove it, together with the rest of methods depreacted in Pharo 1.1. How to detect the methods deprecated in Pharo 1.1? You need to take a 1.1 image and look there. But to solve this, and other problems, we have not only deprecate: but also deprecated: anExplanationString on: date in: version This is muuuch better and we can even then automate code so that it automatically removes the deprecation of a previous image. You can browse and see where each method was deprecated. It would be cool if everybody uses that method instead of deprecated. And thus, it would be cool to deprecate deprecated: hahahahaha what do you think? cheers mariano

2 1

Re: [Pharo-project] Books for summer (was: Time Machine)
by laurent laffont July 31, 2010

July 31, 2010

On Sat, Jul 24, 2010 at 10:59 AM, Patrick Barroca <patrick.barroca(a)gmail.com > wrote: > I've ordered "Why programs fail" by Andreas Zeller. > It will be my summer holidays book ;) > So I'll borrow it once read :) I've ordered "Your Brain at Work: Strategies for Overcoming Distraction, Regaining Focus, and Working Smarter All Day Long" - David Rock "The 10-day MBA: A Step-by-Step Guide to Mastering the Skills Taught in Top Business Schools" - Steven Silbiger (recommended in "Passionate Programmer" by Chad Fowler). And you dear Pharoers, what will you read this summer regarding your computing/business activity ? Laurent > > On Thu, Jul 22, 2010 at 11:52 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: > > http://www.st.cs.uni-saarland.de/dd/ > > you can get some papers but also the slides that go with the book > > Stef > > > > On Jul 22, 2010, at 11:36 PM, laurent laffont wrote: > > > >> > >> On Thu, Jul 22, 2010 at 11:34 PM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > >> did you read delta debugging from andreas Zeller? > >> > >> No. Where ? > >> > >> Laurent > >> > >> > >> > >> Stef > >> > >> On Jul 22, 2010, at 11:11 PM, laurent laffont wrote: > >> > >> > Hi, > >> > > >> > From a discussion I had with Kent Beck about Continuous Testing / > Autotest (see > http://pharocasts.blogspot.com/2010/07/live-testing-with-autotest.html ), > I would like to add a kind of Time Machine for Smalltalk code in Autotest. > >> > > >> > When a test fails, what I really want to know is why. Sometimes a test > fails and I don't know why. So I have to go through a debugging session > which distracts me from what I've been coding. > >> > > >> > So an idea is to diff backtrace before and after the test fails: > >> > - revert to last green > >> > - replay the test and save the trace > >> > - forward to current test and run (test fails) > >> > - compare execution paths in order to see the consequence of last > change > >> > > >> > How would you do this ? Where should I look for materials which can > help me coding this ? > >> > > >> > Cheers, > >> > > >> > Laurent Laffont > >> > > >> > http://pharocasts.blogspot.com/ > >> > http://magaloma.blogspot.com/ > >> > _______________________________________________ > >> > Pharo-project mailing list > >> > Pharo-project(a)lists.gforge.inria.fr > >> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >> > >> > >> _______________________________________________ > >> Pharo-project mailing list > >> Pharo-project(a)lists.gforge.inria.fr > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >> > >> _______________________________________________ > >> Pharo-project mailing list > >> Pharo-project(a)lists.gforge.inria.fr > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > -- > Patrick Barroca > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

4 5