January 2009 - Pharo-dev - lists.pharo.org

[Pharo-project] [ANN] 10203
by Adrian Lienhard Jan. 8, 2009

Jan. 8, 2009

- Issue 363: fix some traits issues (introduced by changes in Metaclass and TestCase) - Traits conflict marker methods stored in wrong cache - Remove duplicated method in trait and class that uses it (in collection tests) - Issue 315: darker colors in diff dialog (thanks to Damien Pollet) - Issue 342: Removing beginning capital letter of instance variables (Alexandre Bergel) - Make MC always display dependencies of a version in its summary text - Issue: 101: fasterDayOfYear-brp.1 (Mantis 7156) - Issue 102: better testPrintShowingDecimalPlaces Adrian ___________________ http://www.adrian-lienhard.ch/

3 8

[Pharo-project] About self halt in removed trait methods
by StÃ©phane Ducasse Jan. 8, 2009

Jan. 8, 2009

When I define a class with a trait and remove it after I get all the trait methods locally defined with a self halt. Does anybody know from where such a behavior could come from? Stef

2 4

[Pharo-project] Fwd: [ANN] 10203
by StÃ©phane Ducasse Jan. 8, 2009

Jan. 8, 2009

apparently this could be linked with the faster fasterDayOfYear-brp.1 (Mantis 7156)? Thanks for reporting stef Begin forwarded message: > From: "Rob Rothwell" <r.j.rothwell(a)gmail.com> > Date: January 8, 2009 3:01:07 AM CEST > To: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> > Subject: Re: [Pharo-project] [ANN] 10203 > Reply-To: rjriv(a)sbcglobal.net > > Ok...I went back to pharo0.1-10185dev08.12.1 and re-tried > pharo0.1-10196dev08.12.3 again, and they both die the same terrible > death when loading this update. > > I think it is shortly after a "recompiling" stage, then it hits a > "Loading" stage for a very long time. Finally, the debugger at the > bottom of the screen that I've never explored pops up and it looks > like a "days:hours:minutes:seconds:nanos:" flashes by repeatedly. > The window goes away, and shortly thereafter, so does pharo. > > Oh...I am running on Windows with the following VM from the system > menu: > > Squeak 3.10.7 (release) from Aug 22 2008 > Compiler: gcc 2.95.2 19991024 (release) > > Rob > > > On Wed, Jan 7, 2009 at 3:58 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > > wrote: > send it here for now. > pharo-dev should be pharo :) > > > > On Jan 7, 2009, at 9:56 PM, Rob Rothwell wrote: > > Interesting! I'll test that some more and make sure it is > reproducible, and then where do I post pharo dev image problems? > It's not really a pharo thing... > > Rob > > On Wed, Jan 7, 2009 at 3:28 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > > wrote: > hi rob > > I got not problem with the core image. > > Stef > > > On Jan 7, 2009, at 8:43 PM, Rob Rothwell wrote: > > Has anyone successfully loaded this from the System Update... menu > item? > > Whether starting from my own image, or a fresh dev08.12.3 image, it > eventully goes into debug mode at the bottom of the screen, and if > left on it's own, eventually just shuts down... > > Rob > > On Wed, Jan 7, 2009 at 1:06 PM, Adrian Lienhard <adi(a)netstyle.ch> > wrote: > - Issue 363: fix some traits issues (introduced by changes in > Metaclass and TestCase) > - Traits conflict marker methods stored in wrong cache > - Remove duplicated method in trait and class that uses it (in > collection tests) > - Issue 315: darker colors in diff dialog (thanks to Damien Pollet) > - Issue 342: Removing beginning capital letter of instance variables > (Alexandre Bergel) > - Make MC always display dependencies of a version in its summary text > - Issue: 101: fasterDayOfYear-brp.1 (Mantis 7156) > - Issue 102: better testPrintShowingDecimalPlaces > > Adrian > ___________________ > http://www.adrian-lienhard.ch/ > > > _______________________________________________ > 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 > > > >

1 0

[Pharo-project] Collection extensions
by StÃ©phane Ducasse Jan. 7, 2009

Jan. 7, 2009

Hi all I published to the inbox some cool collection extension methods that we use all the time in Moose. flatCollect:, collectAsSet:, and groupedBy: http://code.google.com/p/pharo/issues/detail?id=432&colspec=ID%20Type%20Sta… I would like to have your feedback because we found them really useful in practice. Here are some examples: testFlatCollectArray "self debug: #testFlatCollectArray" self assert: ((#((1 2) (3 4) (5 3)) flatCollect: [ :each ]) = #(1 2 3 4 5 3)). self assert: ((#((1 2) (2 3) (1 3 4)) flatCollect: [:each]) = #(1 2 2 3 1 3 4)). self assert: ((#((1 2) (2 3) (1 3 4)) flatCollect: [:each| Set with: each]) = #(#(1 2) #(2 3) #(1 3 4))). testFlatCollectSet "self debug: #testFlatCollectSet" self assert: ((#((1 2) (1 2) (1 3 4)) asSet flatCollect: [:each]) = #(1 1 2 3 4) asSet). self assert: ((#() asSet flatCollect: [:each]) = #() asSet). self assert: ((#((1 2) () (1 3 4)) asSet flatCollect: [:each]) = #(1 1 2 3 4) asSet). self assert: ((#((1 2) #((99)) (1 3 4)) asSet flatCollect: [:each]) = #(1 1 2 3 4 (99)) asSet). self assert: ((#((1 2) #(()) (1 3 4)) asSet flatCollect: [:each]) = #(1 1 2 3 4 ()) asSet). testGroupedByArray "self debug: #testGroupedByArray" | res | res := #(1 2 3 4 5) groupedBy: [:each | each odd]. self assert: (res at: true) = #(1 3 5). self assert: (res at: false) = #(2 4) testGroupedBy "self debug: #testGroupedBy" | res | res := #(1 2 3 4 5) asOrderedCollection groupedBy: [:each | each odd]. self assert: (res at: true) = #(1 3 5) asOrderedCollection. self assert: (res at: false) = #(2 4) asOrderedCollection

10 19

[Pharo-project] DictionaryTest
by Alexandre Bergel Jan. 7, 2009

Jan. 7, 2009

Dear List, A new version of CollectionsTests is waiting in PharoInbox. Here is the comments: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= **This version includes the content of version 142** The most important methods in Dictionary are covered by DictionaryTest. Some implementation methods in Set are also covered by the testing class. One trait TDictionaryAddingTest has been added. More traits will be added soon. DictionaryTest coverageAsString ==> 'DictionaryTest covers 77% of Dictionary' -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

1 0

[Pharo-project] pharo is... ?
by Sean Allen Jan. 7, 2009

Jan. 7, 2009

I started using Squeak a few months ago, mostly in a time permitting fashion.. 2-3 weeks ago, I saw a Pharo related message come across that list and joined here to see what Pharo is. I'm still not entirely sure, so I'm asking... Pharo is... ? The little bit of marketing on the website makes it sound appealing and I'm sure if I had more experience with Squeak then downloading the one click and running it and poking around would have answered a ton of questions but, I don't have the Squeak background to have that be meaningful. Is there a document somewhere that says what Pharo is meant to be. What initial concrete changes from Squeak where done/are going to be done? I really need something as a jumping off point... Thanks for any pointers, Sean

3 7

Re: [Pharo-project] Next Issue ;-)
by Bill Schwab Jan. 6, 2009

Jan. 6, 2009

I saw some similar goofiness at one point, but do not recall whether it was related to cryptography. I am interested in it and the SSL classes. I managed to install same at one point, but it is no longer clear how I did it. Mining the change log of the most recent image where it works (I have one) and/or searching my email exchanges with Ron might help. The idea being to figure out when it worked and then look for special instructions that I might have followed. Gary, it would be nice to have your mutex fix in Pharo. One of the first things I would hope to get working on Pharo is very multi-process oriented, and a reliable #adddeferredUIMessage: would be most helpful. Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029 >>> gazzaguru2(a)btinternet.com 01/06/09 7:22 AM >>> That is normally a symptom of something updating the World morphs in a non-UI process. Morphs should only be changed from the UI process otherwise all kind of inconsistencies can happen. WorldState addDeferredUIMessage: can be used top safely perform actions but, for some applications, finer control is needed. We have developed Squeak applications that are of necessity multi-process driven and were forced to modify WorldState to allow (mutex based) synchronisation with the event loop, thus avoiding the issues. Regards, Gary. ----- Original Message ----- From: "Brian Brown" <brian(a)ablelinktech.com> To: "An open mailing list to discuss any topics related to an open-sourceSmalltalk" <Pharo-project(a)lists.gforge.inria.fr> Sent: Monday, January 05, 2009 10:26 PM Subject: [Pharo-project] Next Issue ;-) > I'm trying to load cryptography 1.1 from the Universe browser. > Everything seems to go well, and the dialog completes and exits. > Immediately following that, whenever the mouse moves over any morphs, > you get the below traceback. the ivars leftMorphs, enteredMorphs, and > overMorphs are all nil, but are being treated as collections... > > > UndefinedObject(Object)>>doesNotUnderstand: #includes: > MouseOverHandler>>noticeMouseOver:event: > HandMorph>>noticeMouseOver:event: > OBTextMorphWithShout(Morph)>>handleMouseOver: > MouseEvent>>sentTo: > OBTextMorphWithShout(Morph)>>handleEvent: > MorphicEventDispatcher>>dispatchDefault:with: > MorphicEventDispatcher>>dispatchEvent:with: > OBTextMorphWithShout(Morph)>>processEvent:using: > MorphicEventDispatcher>>dispatchDefault:with: > MorphicEventDispatcher>>dispatchEvent:with: > TransformMorph(Morph)>>processEvent:using: > MorphicEventDispatcher>>dispatchDefault:with: > MorphicEventDispatcher>>dispatchEvent:with: > OBPluggableTextMorphWithShout(Morph)>>processEvent:using: > MorphicEventDispatcher>>dispatchDefault:with: > MorphicEventDispatcher>>dispatchEvent:with: > OBGroupingMorph(Morph)>>processEvent:using: > MorphicEventDispatcher>>dispatchDefault:with: > MorphicEventDispatcher>>dispatchEvent:with: > SystemWindow(Morph)>>processEvent:using: > MorphicEventDispatcher>>dispatchDefault:with: > MorphicEventDispatcher>>dispatchEvent:with: > PasteUpMorph(Morph)>>processEvent:using: > PasteUpMorph>>processEvent:using: > PasteUpMorph(Morph)>>processEvent: > HandMorph>>sendEvent:focus:clear: > HandMorph>>sendMouseEvent: > HandMorph>>handleEvent: > MouseOverHandler>>processMouseOver: > HandMorph>>handleEvent: > HandMorph>>processEvents > [] in WorldState>>doOneCycleNowFor: {[:h | ActiveHand := h. h > processEvents. ActiveHand := nil]} > Array(SequenceableCollection)>>do: > WorldState>>handsDo: > WorldState>>doOneCycleNowFor: > WorldState>>doOneCycleFor: > PasteUpMorph>>doOneCycle > [] in Project class>>spawnNewProcess {[[World doOneCycle. Processor > yield. false] whileFalse. nil]} > [] in BlockContext>>newProcess {[self value. Processor > terminateActive]} > > > > _______________________________________________ > 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

1 0

Re: [Pharo-project] Underscores question
by Bill Schwab Jan. 6, 2009

Jan. 6, 2009

Gwenael, This might be it. I thought there was a little more to it, but c_a call: b. and the interpretations (number list) might be what I was remembering; I thought it were a few other concrete examples. There are other parts of the thread that seem very familar. My own take is that the default should be to treat underscores as a letter, and to allow file-in of code with underscore assignment as an option. That helps with external interfacing, cross-dialect compatibility, and retains access to existing/older code. I do not like Burt's idea of a class method #allowUnderscores, because (I think??) it assumes _ will not appear in class names, which would be very helpful in mapping external names to classes. However, a global variable could work. However, I still see underscore assignment as something that should be supported only when filing in code that uses it. Sorry I didn't find more. Bill ============================ Gmane From: Bert Freudenberg <bert <at> impara.de> Subject: Underscores in Identifiers (was: Re: Random and unsolicited feedback on 3.9a) Newsgroups: gmane.comp.lang.smalltalk.squeak.general Date: 2005-11-19 10:58:23 GMT (3 years, 6 weeks, 6 days, 10 hours and 10 minutes ago) When dealing with low_level_code, I'd love to have underscores in identifiers - not even just method names, but for variables, too. This could probably be achieved simply by using a different type table with $_ being an #xLetter in Scanner (not sure about the SmaCC- based Compiler). However, I would also strongly suggest *not* to allow this as a standard. Apart from breaking old code file-ins, we would soon get tons of unreadable gibberish by C-trained newbies ;-) Instead, when filing in, the compiler would interpret underscores as assignment, just as it is now. *Only* if specifically enabled by the filed-in code would it be switched to allow underscores in identifiers. Same goes for normal development - *unless* a class answer true when asked #allowUnderscoresInIdentifiers, underscores are compiled as assignments. The file-out code would take that into account to generate the code snippet enabling underscores in identifiers needed for later file-in. How does that sound? - Bert - Am 19.11.2005 um 01:39 schrieb Andreas Raab: > Can we please consider the consequences of doing that (like > potentially breaking lots of code from fileIns) and how we are > going to deal with it *before* such a change gets included? I would > hate it to have another one of those situations where things break > for absolutely no good reason. > > Cheers, > - Andreas ============================ Gmane From: Andreas Raab <andreas.raab <at> gmx.de> Subject: Re: 3.9 underscore still there? Newsgroups: gmane.comp.lang.smalltalk.squeak.general Date: 2006-10-30 20:18:13 GMT (2 years, 9 weeks, 5 days, 6 hours and 46 minutes ago) Bill Schwab wrote: > My preference would be for ANSI compatibility. With that said, having > underscored in selectors, and even just all but the first slot, would do > almost everying I need. I doubt I use them in variable names, and if I > do, I could change it. If I were to move my production code to Squeak, > I would be editing a lot more than a few variable names. Most of uses > of underscores are matching the outside world, and that is not so > readily altered to suit my whim or Squeak's limitations. If all you want to do is to get your code going in Squeak, a fairly simple alternative is to subclass the current parser/compiler, apply Ian's patch and use those for loading your own classes. It ain't exactly a great solution but may be helpful in the short term. > If we can get > Ian's fix in the mainstream, it would be greatly appreciated. This is one of these situations where a little more thought is in order because there are both short-term and long-term implications. Consider an example like this: c_a call: b. Depending on the interpretation of underscore we have 3 possibilities: 1) Underscore means assignment: The above is a legal expression. 2) Underscore is a letter: The above is a legal, too. 3) Underscore is a letter in selectors except if first, and invalid for variable names: The above is illegal. So in two out of three interpretations the above is legal, only in the last one it is not. What troubles me here is that while it may be an okay solution in the short term to put the burden on the user of the underscore (e.g., basically saying "if you use underscores you need to understand where exactly you can use them and where not") the inconsistency and complexity inherent in the description that "underscores are treated as letters in selectors unless they are the first character and cannot be used in variable names" strikes me as a *very* poor choice in the long term. I'd rather do something where (based on some meta-annotations) the parser can decide whether to to treat underscores as assignments or as letters and possibly rewrite them on the fly. The essential idea being that legacy code (using underscore as assignments) can still be loaded into a later version. Cheers, - Andreas Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029

1 0

Jan. 6, 2009

> > From: stephane ducasse <stephane.ducasse(a)free.fr> > Date: January 6, 2009 3:24:29 PM CEST > To: Pharo Development <Pharo-project(a)lists.gforge.inria.fr> > Subject: [ANN] 10202 > > > - More test in DictionaryTest. The class Dictionary is now covered > at 66% > - Issue 433: TPureBehavior>>traits to get a collection of used traits. > - Issue 226: Resize comment pane in Monticello browser > - Issue 426: Code coverage > - Collection extension: groupedBy, flatCollect:, collectAsSet:, > should remove sixx as package > > Stef > > >

1 0

[Pharo-project] DictionaryTest
by Alexandre Bergel Jan. 6, 2009

Jan. 6, 2009

New tests on DictionaryTest. The method categories accesssing, adding, comparing, enumerating, printing, removing, and testing are covered. This represents a coreverage of 66% In PharoInbox. I am continuing the coverage... Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

4 12