March 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 2063 in pharo: NumberTest
by pharo＠googlecode.com April 7, 2011

April 7, 2011

Comment #5 on issue 2063 by nicolas....(a)gmail.com: NumberTest http://code.google.com/p/pharo/issues/detail?id=2063 In squeak I have added an ExtendedNumberParser invoked by #readFrom: For Smalltalk syntax, I have #readSmalltalkSyntaxFrom: (or something like that). The later is used by Parser.

1 1

Re: [Pharo-project] Issue 2454 in pharo: decompiler fix
by pharo＠googlecode.com April 7, 2011

April 7, 2011

Comment #3 on issue 2454 by marcus.denker: decompiler fix http://code.google.com/p/pharo/issues/detail?id=2454 Next action: - take the code here and make a .cs or Slice out of it

1 4

Re: [Pharo-project] Issue 2374 in pharo: Dragging a .image in a Windows VM raises an error
by pharo＠googlecode.com April 7, 2011

April 7, 2011

Comment #5 on issue 2374 by DougEdmu...(a)gmail.com: Dragging a .image in a Windows VM raises an error http://code.google.com/p/pharo/issues/detail?id=2374 This works in XP. I no longer get the "Error:invalid utf8 input detected" 1. Delete the last two lines from pharo.ini ImageFile=Contents\Resources\pharo.image WindowTitle=Pharo Development 2. Set up a filetype association for .image files to pharo.exe (this allows double-clicking to open the image). Now when you click on pharo.exe (or a shortcut to it), it will ask you to select an image file. The first time, it needs some help finding the directory where they are located; the next time, it remembers that location. By deleting the WindowsTitle= line from the pharo.ini file, the title bar shows the name of the image file that you have opened.

1 1

Re: [Pharo-project] Issue 2254 in pharo: sorted and sorted: should be moved to TSortable
by pharo＠googlecode.com April 7, 2011

April 7, 2011

Updates: Status: FixProposed Labels: Milestone-1.3 Comment #3 on issue 2254 by marcus.d...(a)gmail.com: sorted and sorted: should be moved to TSortable http://code.google.com/p/pharo/issues/detail?id=2254 (No comment was entered for this change.)

1 1

Re: [Pharo-project] Issue 1907 in pharo: Set with nil
by pharo＠googlecode.com April 7, 2011

April 7, 2011

Updates: Cc: -niko.schwarz -oscar.nierstrasz Labels: Milestone-1.3 Comment #21 on issue 1907 by stephane.ducasse: Set with nil http://code.google.com/p/pharo/issues/detail?id=1907 (No comment was entered for this change.)

1 2

[Pharo-project] Issue 3831 in pharo: 1.2 full image workspace has description on how to load O2
by pharo＠googlecode.com April 5, 2011

April 5, 2011

Status: Accepted Owner: marcus.d...(a)gmail.com Labels: Milestone-1.2-DevImage New issue 3831 by marcus.d...(a)gmail.com: 1.2 full image workspace has description on how to load O2 http://code.google.com/p/pharo/issues/detail?id=3831 ... but O2 does not work in 1.2 So we should remove the description.

1 6

[Pharo-project] Issue 3345 in pharo: findBinary: from Cuis as integrated in Squeak
by pharo＠googlecode.com April 5, 2011

April 5, 2011

Status: FixedWaitingToBePharoed Owner: stephane.ducasse Labels: Milestone-1.3 Difficulty-Easy New issue 3345 by stephane.ducasse: findBinary: from Cuis as integrated in Squeak http://code.google.com/p/pharo/issues/detail?id=3345 It would be nice to have a look at that and write some tests Levente Uzonyi uploaded a new version of Collections to project The Trunk: http://source.squeak.org/trunk/Collections-ul.408.mcz ==================== Summary ==================== Name: Collections-ul.408 Author: ul Time: 17 November 2010, 12:25:59.364 pm UUID: 1520a654-9c34-734d-ae16-a600d1a2b948 Ancestors: Collections-ul.407 - findBinary* enhancements from Cuis. =============== Diff against Collections-ul.407 =============== Item was changed: ----- Method: SequenceableCollection>>findBinary: (in category 'enumerating') ----- findBinary: aBlock "Search for an element in the receiver using binary search. The argument aBlock is a one-element block returning 0 - if the element is the one searched for <0 - if the search should continue in the first half >0 - if the search should continue in the second half If no matching element is found, raise an error. Examples: + #(1 3 5 7 11 15 23) findBinary: [ :arg | 11 - arg ] - #(1 3 5 7 11 15 23) findBinary:[:arg| 11 - arg] " + ^self findBinary: aBlock do: [ :found | found ] ifNone: [ self errorNotFound: aBlock ]! - ^self findBinary: aBlock ifNone: [self errorNotFound: aBlock]! Item was added: + ----- Method: SequenceableCollection>>findBinary:do:ifNone: (in category 'enumerating') ----- + findBinary: aBlock do: actionBlock ifNone: exceptionBlock + "Search for an element in the receiver using binary search. + The argument aBlock is a one-element block returning + 0 - if the element is the one searched for + <0 - if the search should continue in the first half + >0 - if the search should continue in the second half + If found, evaluate actionBlock with the found element as argument + If no matching element is found, evaluate exceptionBlock, + with the 'bounding' elements (or nil) as optional arguments. + Examples: + #(1 3 5 7 11 15 23) + findBinary: [ :arg | 11 - arg ] + do: [ :found | found ] + ifNone: [ :a :b | ('between: ', {a. b} printString) ] + #(1 3 5 7 11 15 23) + findBinary: [ :arg | 12 - arg ] + do: [ :found | found ] + ifNone: [ :a :b | ('between: ', {a. b} printString) ] + #(1 3 5 7 11 15 23) + findBinary: [ :arg | 0.5 - arg ] + do: [ :found | found ] + ifNone: [ :a :b | ('between: ', {a. b} printString) ] + #(1 3 5 7 11 15 23) + findBinary: [ :arg | 25 - arg ] + do: [ :found | found ] + ifNone: [ :a :b | ('between: ',{a. b} printString) ] + " + ^self + findBinaryIndex: aBlock + do: [ :foundIndex | actionBlock value: (self at: foundIndex) ] + ifNone: [ :prevIndex :nextIndex | + exceptionBlock + cull: (prevIndex > 0 ifTrue: [ self at: prevIndex ]) + cull: (nextIndex <= self size ifTrue: [ self at: nextIndex ]) ]! Item was changed: ----- Method: SequenceableCollection>>findBinary:ifNone: (in category 'enumerating') ----- findBinary: aBlock ifNone: exceptionBlock "Search for an element in the receiver using binary search. The argument aBlock is a one-element block returning 0 - if the element is the one searched for <0 - if the search should continue in the first half >0 - if the search should continue in the second half + If no matching element is found, evaluate exceptionBlock, + with the 'bounding' elements (or nil) as optional arguments." + + ^self findBinary: aBlock do: [ :found | found ] ifNone: exceptionBlock! - If no matching element is found, evaluate exceptionBlock." - | index low high test item | - low := 1. - high := self size. - [index := high + low // 2. - low > high] whileFalse:[ - test := aBlock value: (item := self at: index). - test = 0 - ifTrue:[^item] - ifFalse:[test > 0 - ifTrue: [low := index + 1] - ifFalse: [high := index - 1]]]. - ^exceptionBlock value! Item was changed: ----- Method: SequenceableCollection>>findBinaryIndex: (in category 'enumerating') ----- findBinaryIndex: aBlock "Search for an element in the receiver using binary search. The argument aBlock is a one-element block returning 0 - if the element is the one searched for <0 - if the search should continue in the first half >0 - if the search should continue in the second half If no matching element is found, raise an error. Examples: + #(1 3 5 7 11 15 23) findBinaryIndex: [ :arg | 11 - arg ] - #(1 3 5 7 11 15 23) findBinaryIndex:[:arg| 11 - arg] " + ^self findBinaryIndex: aBlock do: [ :found | found ] ifNone: [ self errorNotFound: aBlock]! - ^self findBinaryIndex: aBlock ifNone: [self errorNotFound: aBlock]! Item was added: + ----- Method: SequenceableCollection>>findBinaryIndex:do:ifNone: (in category 'enumerating') ----- + findBinaryIndex: aBlock do: actionBlock ifNone: exceptionBlock + "Search for an element in the receiver using binary search. + The argument aBlock is a one-element block returning + 0 - if the element is the one searched for + <0 - if the search should continue in the first half + >0 - if the search should continue in the second half + If found, evaluate actionBlock with the index as argument + If no matching element is found, evaluate exceptionBlock, + with the indexes of the 'bounding' elements as optional + arguments. Warning: Might give invalid indexes, see + examples below. + Examples: + #(1 3 5 7 11 15 23) + findBinaryIndex: [ :arg | 11 - arg ] + do: [ :found | found ] + ifNone: [ :a :b | ('between: ', {a. b} printString)] + #(1 3 5 7 11 15 23) + findBinaryIndex: [ :arg | 12 - arg ] + do: [ :found | found ] + ifNone: [ :a :b | ('between: ', {a. b} printString) ] + #(1 3 5 7 11 15 23) d + findBinaryIndex: [ :arg | 0.5 - arg ] + do: [ :found | found ] + ifNone: [ :a :b | ('between: ', {a. b} printString) ] + #(1 3 5 7 11 15 23) + findBinaryIndex: [ :arg | 25 - arg ] + do: [ :found | found ] + ifNone: [ :a :b | ('between: ',{a. b} printString) ] + " + | index low high | + low := 1. + high := self size. + [ + index := high + low // 2. + low > high ] whileFalse: [ + | test | + test := aBlock value: (self at: index). + test = 0 + ifTrue: [ ^actionBlock value: index ] + ifFalse: [ test > 0 + ifTrue: [ low := index + 1 ] + ifFalse: [ high := index - 1 ] ] ]. + ^exceptionBlock cull: high cull: low! Item was changed: ----- Method: SequenceableCollection>>findBinaryIndex:ifNone: (in category 'enumerating') ----- findBinaryIndex: aBlock ifNone: exceptionBlock "Search for an element in the receiver using binary search. The argument aBlock is a one-element block returning 0 - if the element is the one searched for <0 - if the search should continue in the first half >0 - if the search should continue in the second half + If no matching element is found, evaluate exceptionBlock, + with the indexes of the 'bounding' elements as optional + arguments. Warning: Might give invalid indexes." + + ^self findBinaryIndex: aBlock do: [ :found | found ] ifNone: exceptionBlock! - If no matching element is found, evaluate exceptionBlock." - | index low high test | - low := 1. - high := self size. - [index := high + low // 2. - low > high] whileFalse:[ - test := aBlock value: (self at: index). - test = 0 - ifTrue:[^index] - ifFalse:[test > 0 - ifTrue: [low := index + 1] - ifFalse: [high := index - 1]]]. - ^exceptionBlock value!

1 1

Re: [Pharo-project] Remove #class as a Compiler optimization
by Marcus Denker April 5, 2011

April 5, 2011

On Mar 25, 2011, at 5:26 PM, Mariano Martinez Peck wrote: > Hi. I have to say that I hate that the compiler associates a special bytecode for #class and that the VM don't even send the message. I want to be able to overwrite #class in a proxy for example, or to debug it. > > I did some benchmarks disabling such optimization by doing: > > (ParseNode classVarNamed: 'StdSelectors') removeKey: #class ifAbsent: []. > Compiler recompileAll. > > And the difference is NOTHING in my tests (maybe I am doing something wrong). > > With Standard VM and #class optimization > > [SystemNavigation default allObjectsDo: [:each | each class]] timeToRun -> aprox 50 miliseconds > What is the constant over head of doing just the iteration? [SystemNavigation default allObjectsDo: [:each | ]] timeToRun > > What do you think? I am for... for the JIT is is a monomorphic send to a primitive, so the IC will be very effective and should take care that the lookup is actually almost never done. (and the lookup is the only thing the #class bytecode saves, as the target method is a primitive). Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

5 8

April 4, 2011

Hi guys Since this is interesting for all of us I prefer to publicly discuss it. From: Fernando Olivero <fernando.olivero(a)usi.ch> > Date: March 31, 2011 8:40:26 AM GMT+02:00 > To: alain.plantec(a)free.fr, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Subject: Regarding SimpleMorphic > Reply-To: fernando.olivero(a)usi.ch > > Hi, i've been working on the necessary steps to ease the adoption of > SimpleMorphic. Excellent! > I found it really nice, and would like to code the new > version of Gaucho on top of it. I post here the conclusions roadmap, > maybe you are starting the same effort, so this is just to collect > feedback or let you know! We want to join forces. I would love to have key widgets: list, tree ported and totally revised so that we do not have 20 of them but just two or four. > I always start from the Morphic in CUIS 3.1, and then go one by one > trying to port the relevant classes, honoring the intent behind Pharo > UI by, for example, adding in the UIManager uses whenever posible, > > Saludos, > Fernando Question: should we look in Cuis3.1 or Pharo1.3 SMx > %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% > CUIS > System > 1) Review Editor and friends: Separate hierarchy or try to merge with > the existing one in Pharo? Alain's great work on EditorState is > missing in CUIS. Yes I love the selection and highlights of Alain. > 2) import TextModel and hierarchy or maintain a separate hierarchy? > The changes in text model and subclasses seem to be good to have! > 3) (CUIS )DifferenceFinder vs (Pharo)TextDiffBuilder ? ( Seems that > DifferenceFinder has extra funcionality) No idea there. > 4) Transcript and TranscriptMorph. DONE ISSUE 3736 soon in Pharo1.3 > > %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% > CUIS3.1 into Pharo1.3 SimpleMorphic So what is the difference with the one we have. > 1) Make current implementation of SMx load in Pharo1.3. > DONE ISSUE 3878: Implementing enableTextChange > DONE ISSUE 3584: Cleanup removing DisplayText =>to remove > UIManager>>composeForm: > DONE ISSUE 3915: DiffMorph requests thru UIManager: so we don't have > to change senders such as ChangeList and VersionBrowser. Good. > 2) World, ActiveHand, ActiveEvent and ActiveWorld cleanup in Morphic. > To merge Morphic and SimpleMorphic handling of the global state, > centralizing the accessors in UIManager, by removing Globals. ALMOSTE > DONE ISSUE 3903 > 3) general up to date from CUIS 3.1: ALMOST DONE > 4) tools?: Revise the SMxBrowser and family, replace maybe with the > new TextModel>>openAsMorph: , etcâ¦ For the Browser we plan - to simply **Throw** away all the stringHolder and codeHolder classes and subclasses. Benjamin can show you Nautilus beta. - We will remove also ToolBuilder (as soon as we have a new version of the test runner) - We need a model for the debugger (we should check glamour people for that). So we will temporary keep stringHolde but compact it only for the debugger. > 5) Remove SMxTheWorldMenu and replace with MenuPragmaBuilder as in Pharo. Yes > 6) ? > > ++++++++++++++++++++++ > LOAD ORDER (uncomplete) > 3878 > 3584 > 3915 > 3736 > (PENDING) 3903 > ...

7 19

[Pharo-project] Last pending things for Pharo 1.2
by Mariano Martinez Peck April 4, 2011

April 4, 2011

So....here is the list of things I guess are pending: 1) "Release" all configurations included in Pharo (this is, ConfigurationOfPharo and all it dependencies). I mean, we should NOT use or depend on #development versions. 2) Update the one click image to use latest cog images and "pharo prepared vms". There are some issues regarding this... 3) Write down all the things/summary done in Pharo 1.2 5) Update SystemVersion current -->> Pharo1.2rc2 of 27 January 2011 update 12340 6) Condense sources? condense changes? #cleanUpForRelease Cheers Mariano

5 10