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

[Pharo-project] [ANN] 10268 image released
by StÃ©phane Ducasse April 5, 2009

April 5, 2009

10268 image released on https://gforge.inria.fr/frs/admin/qrs.php?group_id=1299

1 0

[Pharo-project] [ANN] 10266 Merge tool SUnitGUI Setting Integration Enh
by StÃ©phane Ducasse April 5, 2009

April 5, 2009

Issue 710: Merge Tool diff fix Fixes for edge cases when handling conflicts. Fixes for original MC merge browser. SUnitGUI Improvement - do not offer to test coverage of kernel/collection/exception/sunit packages, that will only crash the system - do not consider methods with <ignoreForCoverage> annotation - improving the error messages - don t try show a list if all methods are covered - really save the history - do not wrap abstract methods, they won t be called anyway - update the history even after coverage is run Settings Integration enh - Code cleaning (less classes, more comments) Alain I could not load 45 so I load 39 for now. Stef

2 1

[Pharo-project] [ANN] 10268: 703 & 705 & 704 closed
by StÃ©phane Ducasse April 5, 2009

April 5, 2009

Issue 703: isMorphic left over Issue 705: closures: strange error in SyntaxError apparently it may happen that the category is nil I do not think that my cs fixes the origin of the problem but ok for now. Issue 704: closures: cleaning some block arg assignemt

1 0

Re: [Pharo-project] Unicode Problem (again) even with fix in 10266
by StÃ©phane Ducasse April 5, 2009

April 5, 2009

I fixed it apparently the previous fix was not intergated correclty On Apr 5, 2009, at 2:39 PM, StÃ©phane Ducasse wrote: > I cannot release the fixes I was integrating > > UTF8DecomposedTextConverter>>nextFromStream: aStream > > | char resultChar | > char := super nextFromStream: aStream. > (CombinedChar isCompositionCharacter: char charCode) > ifFalse: [^char]. > combinedChar > ifNil: [ > combinedChar := CombinedChar new. > combinedChar simpleAdd: char] > ifNotNil: [ > [combinedChar simpleAdd: char] > whileFalse: [char := super nextFromStream: aStream]. > resultChar := combinedChar combined. > combinedChar := CombinedChar new. > combinedChar simpleAdd: char. > ^resultChar] > > char charCode -> DNU > char is nil. > > Stef > > From: ddd > To: Pharo-project(a)lists.gforge.inria.fr > Subject: [BUG]UndefinedObject(Object)>>doesNotUnderstand: #charCode > > here insert explanation of what you were doing, suspect changes you've > made and so forth. > > 5 April 2009 2:39:03 pm > > VM: Mac OS - a SmalltalkImage > Image: Pharo0.1 [Latest update: #10266] > > SecurityManager state: > Restricted: false > FileAccess: true > SocketAccess: true > Working Dir /Users/ducasse/Workspace/FirstCircle/ActiveResearch/Pharo/ > Pharo > Trusted Dir /foobar/tooBar/forSqueak/bogus > Untrusted Dir /Users/ducasse/Library/Preferences/Squeak/Internet/My > Squeak > > UndefinedObject(Object)>>doesNotUnderstand: #charCode > Receiver: nil > Arguments and temporary variables: > aMessage: charCode > exception: MessageNotUnderstood: UndefinedObject>>charCode > resumeValue: nil > Receiver's instance variables: > nil > > UTF8DecomposedTextConverter>>nextFromStream: > Receiver: an UTF8DecomposedTextConverter > Arguments and temporary variables: > <<error during printing> > Receiver's instance variables: > combinedChar: nil > > MultiByteBinaryOrTextStream>>next > Receiver: <<error during printing>> > Arguments and temporary variables: > n: nil > Receiver's instance variables: > collection: ' > position: 1 > readLimit: 1 > writeLimit: 6 > isBinary: true > converter: an UTF8DecomposedTextConverter > > MultiByteBinaryOrTextStream>>upToEnd > Receiver: <<error during printing>> > Arguments and temporary variables: > newStream: a WriteStream #[32] > element: 32 > newCollection: #[32 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 > 0 0 0 0 0 0...etc... > Receiver's instance variables: > collection: ' > position: 1 > readLimit: 1 > writeLimit: 6 > isBinary: true > converter: an UTF8DecomposedTextConverter > > > --- The full stack --- > UndefinedObject(Object)>>doesNotUnderstand: #charCode > UTF8DecomposedTextConverter>>nextFromStream: > MultiByteBinaryOrTextStream>>next > MultiByteBinaryOrTextStream>>upToEnd > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > MultiByteBinaryOrTextStream>>contents > [] in > ByteString(String)>>encodeForHTTPWithTextEncoding:conditionBlock: > ByteString(SequenceableCollection)>>do: > ByteString(String)>>encodeForHTTPWithTextEncoding:conditionBlock: > ByteString(String)>>encodeForHTTP > MCHttpRepository>>urlForFileNamed: > MCHttpRepository>>writeStreamForFileNamed:replace:do: > MCHttpRepository(MCFileBasedRepository)>>writeStreamForFileNamed:do: > MCHttpRepository(MCFileBasedRepository)>>basicStoreVersion: > MCHttpRepository(MCRepository)>>storeVersion: > [] in ScriptLoader>>copyPackagesFromWaitingFolderToHomeRepository > OrderedCollection>>do: > ScriptLoader>>copyPackagesFromWaitingFolderToHomeRepository > ScriptLoader>>publishChanges > ScriptLoader class>>DoIt > Compiler>>evaluate:in:to:notifying:ifFail:logged: > [] in TextMorphEditor(ParagraphEditor)>>evaluateSelection > BlockClosure>>on:do: > TextMorphEditor(ParagraphEditor)>>evaluateSelection > TextMorphEditor(ParagraphEditor)>>doIt > [] in TextMorphEditor(ParagraphEditor)>>doIt: > TextMorphEditor(ParagraphEditor)>>terminateAndInitializeAround: > TextMorphEditor(ParagraphEditor)>>doIt: > TextMorphEditor(ParagraphEditor)>>dispatchOnKeyEvent:with: > TextMorphEditor>>dispatchOnKeyEvent:with: > TextMorphEditor(ParagraphEditor)>>keystroke: > TextMorphEditor>>keystroke: > [] in TextMorphForEditView(TextMorph)>>keyStroke: > TextMorphForEditView(TextMorph)>>handleInteraction: > TextMorphForEditView>>handleInteraction: > TextMorphForEditView(TextMorph)>>keyStroke: > TextMorphForEditView>>keyStroke: > TextMorphForEditView(TextMorph)>>handleKeystroke: > KeyboardEvent>>sentTo: > TextMorphForEditView(Morph)>>handleEvent: > TextMorphForEditView(Morph)>>handleFocusEvent: > [] in HandMorph>>sendFocusEvent:to:clear: > [] in PasteUpMorph>>becomeActiveDuring: > BlockClosure>>on:do: > PasteUpMorph>>becomeActiveDuring: > HandMorph>>sendFocusEvent:to:clear: > HandMorph>>sendEvent:focus:clear: > HandMorph>>sendKeyboardEvent: > HandMorph>>handleEvent: > HandMorph>>processEvents > [] in WorldState>>doOneCycleNowFor: > Array(SequenceableCollection)>>do: > WorldState>>handsDo: > WorldState>>doOneCycleNowFor: > WorldState>>doOneCycleFor: > PasteUpMorph>>doOneCycle > [] in Project class>>spawnNewProcess > [] in BlockClosure>>newProcess > > > _______________________________________________ > 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] 715: No parser class for closure-compiled methods
by Damien Cassou April 5, 2009

April 5, 2009

http://code.google.com/p/pharo/issues/detail?id=715 -- Damien Cassou http://damiencassou.seasidehosting.st

1 0

[Pharo-project] [ANN] 10264 more closure fixes 685 & 10265 unicode
by StÃ©phane Ducasse April 5, 2009

April 5, 2009

Issue 685: Closure fixes TmpVariableNode closure from lukas MethodsFromBlockContext from adrian Issue 706: problem with unicode 10262

1 0

Re: [Pharo-project] old debugger bugs and the Closure changes
by Dale Henrichs April 5, 2009

April 5, 2009

StÃ©phane, What image did the changes come from? Presumably there are also changes that have been made to the pharo image that are not compatible with the new code ... I've 'fixed' the obvious problems in the changes that were in the install changeSet, but that didn't fix the 'step into' problem... In order to straighten things out, it may be necessary to review code on both sides.. Dale ----- "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> wrote: | ok probably because we could not check all the code unfortunately. | So changes between 3.9 and pharo may have been supplanted by the | closure changes. | | On Apr 4, 2009, at 6:39 PM, Dale Henrichs wrote: | | > I've started taking a look at the problem reported by Michael | Roberts. | > | > I got slightly different misbehavior using the 10259- | > ClosureBootstrap download on linux than reported by Michael, but in | | > checking things out I discovered that the code in the Debugger for | | > the *Core* downloads is different from the *dev* downloads. | > | > For example the source for Debugger>>selectedMessageName in the | > *Core* image (10259-ClosureBootstrap) is: | > selectedMessageName | > "Answer the message selector of the currently selected context. | > If the method is unbound we can still usefully answer its old | > selector." | > | > | selector | | > selector := self selectedContext methodSelector. | > ^(selector ~~ self selectedContext method selector | > and: [selector beginsWith: 'DoIt']) | > ifTrue: [self selectedContext method selector] | > ifFalse: [selector] | > | > and I get a DNU for #methodSelector. On the other hand in the *dev* | | > image (pharo0.1-10259dev09.03.3) the source is: | > selectedMessageName | > "Answer the message selector of the currently selected context." | > | > ^self selectedContext selector | > | > When I looked at the Pharo0.1Core-10259 image, the source is | > identical to the pharo0.1-10259dev09.03.3, so the Closure changeset | | > is apparently introducing some 'unwanted' changes to the Debugger | > (and perhaps elsewhere?). | > | > Dale | > | > _______________________________________________ | > Pharo-project mailing list | > Pharo-project(a)lists.gforge.inria.fr | > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project | >

2 1

[Pharo-project] old debugger bugs and the Closure changes
by Dale Henrichs April 4, 2009

April 4, 2009

I've started taking a look at the problem reported by Michael Roberts. I got slightly different misbehavior using the 10259-ClosureBootstrap download on linux than reported by Michael, but in checking things out I discovered that the code in the Debugger for the *Core* downloads is different from the *dev* downloads. For example the source for Debugger>>selectedMessageName in the *Core* image (10259-ClosureBootstrap) is: selectedMessageName "Answer the message selector of the currently selected context. If the method is unbound we can still usefully answer its old selector." | selector | selector := self selectedContext methodSelector. ^(selector ~~ self selectedContext method selector and: [selector beginsWith: 'DoIt']) ifTrue: [self selectedContext method selector] ifFalse: [selector] and I get a DNU for #methodSelector. On the other hand in the *dev* image (pharo0.1-10259dev09.03.3) the source is: selectedMessageName "Answer the message selector of the currently selected context." ^self selectedContext selector When I looked at the Pharo0.1Core-10259 image, the source is identical to the pharo0.1-10259dev09.03.3, so the Closure changeset is apparently introducing some 'unwanted' changes to the Debugger (and perhaps elsewhere?). Dale

3 2

[Pharo-project] Added PackageInfo class>>existPackageNamed:
by Alexandre Bergel April 4, 2009

April 4, 2009

Waiting in PharoInbox Name: PackageInfo-Alexandre_Bergel.19 Author: Alexandre.Bergel Time: 4 April 2009, 9:30:16 am UUID: cf56dd7d-c21b-4176-a2d6-874d4544a21a Ancestors: PackageInfo- stephane_ducasse.18 Issue #712 -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

1 0

[Pharo-project] SUnit History
by Lukas Renggli April 4, 2009

April 4, 2009

I have a few questions to the authors of the SUnit History feature: 1. I noticed is that all the results are stored in a dictionary of TestResult mapping the classes to their last result. When I delete tests, these obsolete classes remain references from the dictionary and thus never get garbage collected. Why not save the history in a class-instance variable of the TestCase itself? That would even make the code much simpler. 2. Why to store the history of test results in nested dictionaries, sets and arrays? We have a nice TestResult object that remembers exactly the same information and additionally allows to do all kinds of queryies like #hasFailures, hasPassed, ... I see that there is one problem here: the current implementation of TestResult remembers the test case instances, and thus would reference potentially a lot of unnecessary state. Maybe TestResult should only remember the method references of the tests, instead of the test cases? I guess that would solve other problems people regularly report with SUnit as well. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

4 6