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

Re: [Pharo-project] Issue 3444 in pharo: Finder searchedTextList problem

by pharo＠googlecode.com

Updates: Labels: Milestone-1.2 Comment #1 on issue 3444 by marcus.denker: Finder searchedTextList problem http://code.google.com/p/pharo/issues/detail?id=3444 (No comment was entered for this change.)

Dec. 16, 2010

[Pharo-project] Issue 3444 in pharo: Finder searchedTextList problem

by pharo＠googlecode.com

Status: Fixed Owner: Benjamin.VanRyseghem.Pharo New issue 3444 by Benjamin.VanRyseghem.Pharo: Finder searchedTextList problem http://code.google.com/p/pharo/issues/detail?id=3444 There was some problems with the searchedTextList which added the same String several times, and which re-execute the querie if you open then close the list. Now it's fixed ^^ The fix is in the cs, in PharoInbox and in PharoTaskForces ^^ Attachments: FinderFix.1.cs 2.9 KB

Dec. 16, 2010

Re: [Pharo-project] Dynamic Arrays view index at execution

by Henrik Johansen

Den 16.12.2010 14:48, skrev flebber: > HI > > doing the pharo tutorial and I wanted to know how pharo viewed the dynamic > array at index 3(seems smalltalk starts at 1 not 0) > > >From the xample simple enough > { (2+3) . (6*6) . 'hello', ' Stef'} size. 3 > > from the strings example we found index by > > 'ProfStef' at: 1. $P > > so I thought { (2+3) . (6*6) . 'hello', ' Stef'} at 3. would let me know > what the array was evaluated to after execution but it doesn't. Is it > confused because it doesn't know whether I want the third array element or > the third character? > > Led me to wonder the correct way if doing this, so that I could evaluate > array 1 * 2. > > { (2+3) . (6*6) . 'hello', ' Stef'} at 1 * at 2. 180 > > > Cheers What do you mean? The dynamic array is created with three elements, 5 (2+3) at index 1, 36 (6*6) at index 2, and 'hello Stef' ('hello', ' Stef') at index 3. at: 3 thus returns the string. at 3 is invalid, as it is basically 2 method calls, array does not understand a message called #at, and #3 is an invalid selector anyways. For your second expression, writing ({ (2+3) . (6*6) . 'hello', ' Stef'} at: 1) * (at: 2) would not work, as you're missing the receiver for the second at: call. you'd need to do something like: array := { (2+3) . (6*6) . 'hello', ' Stef'}. (array at: 1) * (array at: 2). 180 Cheers, Henry

Dec. 16, 2010

Re: [Pharo-project] Dynamic Arrays view index at execution

by StÃ©phane Ducasse

I do not really understand your problem Now in Smalltalk #( ) is a literal array {} a dynamic the expressions put in the first are not evaluated while in the second yes. Stef On Dec 16, 2010, at 2:48 PM, flebber wrote: > > HI > > doing the pharo tutorial and I wanted to know how pharo viewed the dynamic > array at index 3(seems smalltalk starts at 1 not 0) > > From the xample simple enough > { (2+3) . (6*6) . 'hello', ' Stef'} size. 3 > > from the strings example we found index by > > 'ProfStef' at: 1. $P > > so I thought { (2+3) . (6*6) . 'hello', ' Stef'} at 3. would let me know > what the array was evaluated to after execution but it doesn't. Is it > confused because it doesn't know whether I want the third array element or > the third character? > > Led me to wonder the correct way if doing this, so that I could evaluate > array 1 * 2. > > { (2+3) . (6*6) . 'hello', ' Stef'} at 1 * at 2. 180 > > > Cheers > > -- > View this message in context: http://forum.world.st/Dynamic-Arrays-view-index-at-execution-tp3090891p3090… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Dec. 16, 2010

Re: [Pharo-project] Issue 3442 in pharo: Debugger Tests

by pharo＠googlecode.com

Updates: Summary: Debugger Tests Comment #1 on issue 3442 by stephane.ducasse: Debugger Tests http://code.google.com/p/pharo/issues/detail?id=3442 (No comment was entered for this change.)

Dec. 16, 2010

[Pharo-project] Dynamic Arrays view index at execution

by flebber

HI doing the pharo tutorial and I wanted to know how pharo viewed the dynamic array at index 3(seems smalltalk starts at 1 not 0) >From the xample simple enough { (2+3) . (6*6) . 'hello', ' Stef'} size. 3 from the strings example we found index by 'ProfStef' at: 1. $P so I thought { (2+3) . (6*6) . 'hello', ' Stef'} at 3. would let me know what the array was evaluated to after execution but it doesn't. Is it confused because it doesn't know whether I want the third array element or the third character? Led me to wonder the correct way if doing this, so that I could evaluate array 1 * 2. { (2+3) . (6*6) . 'hello', ' Stef'} at 1 * at 2. 180 Cheers -- View this message in context: http://forum.world.st/Dynamic-Arrays-view-index-at-execution-tp3090891p3090… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Dec. 16, 2010

Re: [Pharo-project] [Hudson] 1.2 build

by Marcus Denker

On Dec 16, 2010, at 1:37 PM, Marcus Denker wrote: > > On Dec 16, 2010, at 1:06 PM, laurent laffont wrote: > >> Thank you Marcus. >> >> Is it hard / possible to add test coverage ? >> > > problematic... when testing system level code, you soon run into meta-recursion (e.g. Array is used by the code used for doing > test coverage). (we should really fix reflection as a concept... but that's more research and not engineering... I should continue with that). > > So this would only make sense on a package by package case. But there it can make sense, yes. > > What I want to add before test coverage is code-critique style checking. > And Camillo suggested we should set up this nice system for Pharo: http://speed.pypy.org/ (but this requires fully automated build of the VM from the source repository) Toon and Camillo are using this for Pinoccio. Which reminds me that the paper is finally available online: http://scg.unibe.ch/scgbib?query=Verw10a&display=abstract Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Dec. 16, 2010

Re: [Pharo-project] Hudson: zip files of build artefacts...

by Marcus Denker

On Dec 16, 2010, at 1:54 PM, Guillermo Polito wrote: > Maybe my answer is too late, but It's still beta2. :P > > Maybe we can now use and use and use beta2, and fix bugs :). And then release a beta3. >From my side not to late... it loads the beta2 config. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Dec. 16, 2010

Re: [Pharo-project] Issue 3443 in pharo: Should remove Sophie Undo classes

by pharo＠googlecode.com

Updates: Cc: aplantec Comment #1 on issue 3443 by stephane.ducasse: Should remove Sophie Undo classes http://code.google.com/p/pharo/issues/detail?id=3443 (No comment was entered for this change.)

Dec. 16, 2010

[Pharo-project] Issue 3443 in pharo: Should remove Sophie Undo classes

by pharo＠googlecode.com

Status: Accepted Owner: stephane.ducasse Labels: Milestone-1.2 New issue 3443 by stephane.ducasse: Should remove Sophie Undo classes http://code.google.com/p/pharo/issues/detail?id=3443 Now that we have the new implementation for the undo we should remove the sophie classes.

Dec. 16, 2010