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

Re: [Pharo-project] About long tests.

by Lukas Renggli

Btw, I am running the Pharo tests in my builds now too: http://hudson.lukas-renggli.ch/job/Pharo/lastCompletedBuild/testReport/(roo… Click on duration twice to see the tests sorted by run-time. I feel a bit bad that the slowest test case is one that I wrote. I'll see if I can speed that up some more. Lukas On 15 March 2010 20:56, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > Hi jorge > > did you publish the cleans for the tests you did during the sprint? > > Thanks Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli http://www.lukas-renggli.ch

March 16, 2010

[Pharo-project] Virtual Desktops in Polymorph

by Torsten Bergmann

Hi, one thing I really miss in the Pharo UI comparing to Squeak is an equivalent to "Projects". Hey - not that I want the "Projects" and related code back but I would like to see something along the lines of "virtual desktops" allowing you to switch between different desktops/Worlds in Polymorph using a simple keystroke. Dont know if others miss that too or hard that would be. Any comments? Thx Torsten -- GMX DSL: Internet, Telefon und Entertainment fÃ¼r nur 19,99 EUR/mtl.! http://portal.gmx.net/de/go/dsl02

March 16, 2010

[Pharo-project] A challenge for us

by StÃ©phane Ducasse

Hi I would like to initiative a task (monthly) for us. I would like to get really good tests coverage for some of the core classes. For example Date, Time, Duration, DateAndTime. This is really important in the long term to get sure that we identify bugs as soon as they appear. It would be really good if we could get team up and fix that together. Does anybody want to help? I started to fix some bugs there and write more tests in the process of fixing tests. Stef

March 16, 2010

[Pharo-project] SocketSteam: Switching ascii/binary modes

by Igor Stasenko

Hello, it looks like its unsafe to switch between ascii/binary mode in SocketStream, because it resets buffers upon switch: binary "Tell the SocketStream to send data as ByteArrays instead of Strings. Default is ascii." binary := true. self resetBuffers The dynamic mode switching is useful: for instance i want to read HTTP headers first, which is preferable to do in ascii mode, but its contents may be binary , which obviously preferable to read in binary mode, to avoid extra conversions. Since SocketStream caching the data it reads, then instead of resetting the buffers it should convert them and avoid losing the data. What you think is an appropriate solution to this? -- Best regards, Igor Stasenko AKA sig.

March 16, 2010

[Pharo-project] [enh] Cleaning of and test for MessageTally

by Alexandre Bergel

Waiting in PharoInbox. This fix has been developed in a 11271. SLICE-MessageTallyCleaningAndTest-Alexandre_Bergel.1 This slices comprises an update for two packages, Tools and ToolsTest. The new version of Tools clean MessageTally. A user of MessageTally may now decide whether he wants to close the tally. Although it is convenient to close it (in order to not keep a reference of the compiled method and the class), this behavior is not always wished. Especially when test have to be written! The user has now the option to not open the result window. ToolsTest contains few and simple tests. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 16, 2010

Re: [Pharo-project] [ANN] ConfigurationOfMagma for Magma 1.0r44

by Scott Gibson

Thanks Miguel! Scott On Mar 15, 2010, at 4:38 PM, Miguel Enrique CobÃ¡ Martinez wrote: > I'm pleased to announce that the ConfigurationOfMagma now includes > support to load version 1.0r44 of Magma. > > In a Pharo or PharoCore 10515 RC3 image evaluate: > > Gofer it > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfMagma'; > load. > > In Squeak, using Monticello browser add package > > ConfigurationOfMagma > > from repository > > http://www.squeaksource.com/MetacelloRepository > > Then in Pharo and Squeak, evaluate in a workspace > > for getting Magma Client: > > (ConfigurationOfMagma project latestVersion) load: 'Client' > > for getting Magma Server: > > (ConfigurationOfMagma project latestVersion) load: 'Server' > > for getting Magma Tester: > > (ConfigurationOfMagma project latestVersion) load: 'Tester' > > Then if you want, run the test suite. Evaluate in a workspace: > > MagmaTestCase allowWriteBarrier: false. > MagmaTestCase fullSuite maDebug. > > > Cheers > -- > Miguel CobÃ¡ > http://miguel.leugim.com.mx > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Scott Gibson

March 16, 2010

Re: [Pharo-project] Case statement and lazy comparison in Pharo

by Henrik Sperre Johansen

On 15.03.2010 22:49, nullPointer wrote: > Well, perhaps is a theme worked in another times but... is possible for Pharo > have a basic Case or elseIf statement? I know is easy create you own > structure control, but not is more useful have a "standard" for everybody? > IÂ´m tired of write code like that... > > (self currentRow == sortedRows last and: [ self > currentCell isNil ]) ifTrue: > [ > self navigationKey: event > ] > ifFalse: > [ > (self currentRow notNil and: [ self currentCell isNil ]) ifTrue: > [ > self setCurrentRowToNext. > ] > ifFalse: > [ > (self currentRow notNil and: [ self currentCell notNil ]) ifTrue: > [ > self setCurrentCellToNext. > > self currentCell notNil ifTrue: > [ > self currentCell performKeyFocus: event inCellBounds: (self > pvtGetCellBounds: self currentCell). > ]. > ]. > ]. > ]. > > > Write code with that format is pathetical :( > > Is valid too have a "and" and "or" lazy? Exists a not lazy with #& and #| , > but could exists an #&& and #|| . Is more easy... > > value1 == value2 and:[<condition> ] and: [<condition>] ...... > > or > > value1 == value2&& <condition> && <condition> ......... ??? > > Well, perhaps is a stupid question but I miss a more complete way for write > code. If in Smalltalk is possible do easy that and include it in "core" why > not do it? > > Is a reasonable desire :) > > Regards > It's a lot clearer what the code does when you avoid repeating checks in deeper nested levels. Why not rewrite to the equivalent expression: self currentCell ifNil: [ self currentRow == sortedRows last ifTrue: [self navigationKey: event ] ifFalse: [self currentRow ifNotNil: [self setCurrentRowToNext]] ifNotNil: [ self currentRow ifNotNil: [ self setCurrentCellToNext. self currentCell performKeyFocus: event inCellBounds: (self pvtGetCellBounds: self currentCell)]] if sortedRows last cannot be nil, you could even write: self currentRow ifNil: [^self]. self currentCell ifNotNil: [ self setCurrentCellToNext. self currentCell performKeyFocus: event inCellBounds: (self pvtGetCellBounds: self currentCell)] ifNil: [ self currentRow == sortedRows last ifTrue: [self navigationKey: event] ifFalse: [self setCurrentRowToNext]] Cheers, Henry

March 15, 2010

Re: [Pharo-project] [ANN] ConfigurationOfMagma for Magma 1.0r44

by Miguel Enrique CobÃ¡ Martinez

Now if you want some old version of Magma you can install it too. For example, to install 1.0r43, evaluate (after installing ConfigurationOfMagma, of course) any of: (ConfigurationOfMagma project version: '1.0r43') load: 'Client'. (ConfigurationOfMagma project version: '1.0r43') load: 'Server'. (ConfigurationOfMagma project version: '1.0r43') load: 'Tester'. To install 1.0r44 (like the previous mail): (ConfigurationOfMagma project version: '1.0r44') load: 'Client'. (ConfigurationOfMagma project version: '1.0r44') load: 'Server'. (ConfigurationOfMagma project version: '1.0r44') load: 'Tester'. As currently 1.0r44 is the latest released version, this is the same that: ConfigurationOfMagma project latestVersion load: 'Client'. ConfigurationOfMagma project latestVersion load: 'Server'. ConfigurationOfMagma project latestVersion load: 'Tester'. Also, if you have an old version of ConfigurationOfMagma in your image, you can update it to the newest version (the one with 1.0r44 version in it) by evaluating: ConfigurationOfMagma project updateProject And then install the new version of Magma as stated before. Cheers -- Miguel CobÃ¡ http://miguel.leugim.com.mx

March 15, 2010

Re: [Pharo-project] Case statement and lazy comparison in Pharo

by Michael Roberts

I would try and reduce the number of branches first. you can use guard conditions to exit early. This is not necessarily exact below, but you hopefully get the idea... (self currentRow == sortedRows last and: [self currentCell isNil]) ifTrue: [^self navigationKey: event] self currentRow ifNil: [^self]. self currentCell ifNil: [^self setCurrentRowToNext] self setCurrentCellToNext. self currentCell ifNil: [^self]. self currentCell performKeyFocus: event inCellBounds: (self pvtGetCellBounds: self currentCell) A different approach entirely is to have an object(s) that represents the nil state for the row and cell. That way you are not checking constantly for it being nil, and perhaps you can dispatch some behaviour to it. cheers, Mike On Mon, Mar 15, 2010 at 9:49 PM, nullPointer <epicfan(a)gmail.com> wrote: > > Well, perhaps is a theme worked in another times but... is possible for Pharo > have a basic Case or elseIf statement? I know is easy create you own > structure control, but not is more useful have a "standard" for everybody? > IÂ´m tired of write code like that... > > Â Â Â Â Â Â Â Â Â Â Â Â (self currentRow == sortedRows last and: [ self > currentCell isNil ]) ifTrue: > Â Â Â Â Â Â Â Â Â Â Â Â [ > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â self navigationKey: event > Â Â Â Â Â Â Â Â Â Â Â Â ] > Â Â Â Â Â Â Â Â Â Â Â Â ifFalse: > Â Â Â Â Â Â Â Â Â Â Â Â [ > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â (self currentRow notNil and: [ self currentCell isNil ]) ifTrue: > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â [ > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â self setCurrentRowToNext. > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â ] > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â ifFalse: > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â [ > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â (self currentRow notNil and: [ self currentCell notNil ]) ifTrue: > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â [ > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â self setCurrentCellToNext. > > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â self currentCell notNil ifTrue: > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â [ > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â self currentCell performKeyFocus: event inCellBounds: (self > pvtGetCellBounds: self currentCell). > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â ]. > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â ]. > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â ]. > Â Â Â Â Â Â Â Â Â Â Â Â ]. > > > Write code with that format is pathetical :( > > Is valid too have a "and" and "or" lazy? Exists a not lazy with #& and #| Â , > but could exists an #&& and #|| Â . Is more easy... > > Â Â Â value1 == value2 and:[ <condition> ] and: [<condition>] ...... > > or > > Â Â value1 == value2 && <condition> && <condition> ......... ??? > > Well, perhaps is a stupid question but I miss a more complete way for write > code. If in Smalltalk is possible do easy that and include it in "core" why > not do it? > > Is a reasonable desire :) > > Regards > > > > > > > -- > View this message in context: http://n4.nabble.com/Case-statement-and-lazy-comparison-in-Pharo-tp1594080p… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 15, 2010

Re: [Pharo-project] Case statement and lazy comparison in Pharo

by Levente Uzonyi

On Mon, 15 Mar 2010, nullPointer wrote: > Well, perhaps is a theme worked in another times but... is possible for Pharo have a basic Case or elseIf statement? I know is easy create you own structure control, but not is more useful have a "standard" for everybody? IÂ´m tired of write code like that... (self currentRow == sortedRows last and: [ self currentCell isNil ]) ifTrue: [ self navigationKey: event ] ifFalse: [ (self currentRow notNil and: [ self currentCell isNil ]) ifTrue: [ self setCurrentRowToNext. ] ifFalse: [ (self currentRow notNil and: [ self currentCell notNil ]) ifTrue: [ self setCurrentCellToNext. self currentCell notNil ifTrue: [ self currentCell performKeyFocus: event inCellBounds: (self pvtGetCellBounds: self currentCell). ]. ]. ]. ]. You can save 2-3 lines/branch if you format your code with a better style: foo ifTrue: [ ... ] ifFalse: [ bar ifTrue: [ ... ] ifFalse: [ baz ... ] ] If you make this branch a separate method you can use returns making it even simpler: foo ifTrue: [ ^... ] bar ifTrue: [ ^... ] baz ifTrue: [ ^... ] ... And there's #caseOf:otherwise: for a case-like pseudostatemet. Note that this is inlined by the compiler. foobar caseOf: { [ ... ] -> [ ... ]. [ ... ] -> [ ... ]. ... } otherwise: [ ... ] > Write code with that format is pathetical :( Is valid too have a "and" and "or" lazy? Exists a not lazy with #& and #| , but could exists an #&& and #|| . Is more easy... value1 == value2 and:[ <condition> ] and: [<condition>] ...... or value1 == value2 && <condition> && <condition> ......... ??? #and: and #or: is short-circuit (lazy) by default. > Well, perhaps is a stupid question but I miss a more complete way for write code. If in Smalltalk is possible do easy that and include it in "core" why not do it? Soon I'll start collecting credits for promoting this book: http://stephane.ducasse.free.fr/FreeBooks/WithStyle/SmalltalkWithStyle.pdf :) Levente Is a reasonable desire :) Regards -- View this message in context: http://n4.nabble.com/Case-statement-and-lazy-comparison-in-Pharo-tp1594080p… Sent from the Pharo Smalltalk mailing list archive at Nabble.com. _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 15, 2010