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

Re: [Pharo-project] Issue 2897 in pharo: Compiler visitor fixes

by pharo＠googlecode.com

Updates: Summary: Compiler visitor fixes Comment #3 on issue 2897 by stephane.ducasse: Compiler visitor fixes http://code.google.com/p/pharo/issues/detail?id=2897 (No comment was entered for this change.)

Jan. 12, 2011

Re: [Pharo-project] Xtreams up to date

by mkobetic＠gmail.com

"Henrik Sperre Johansen"<henrik.s.johansen(a)veloxit.no> wrote: > Can't just load the CoreTests and have all tests pass though, due to > the isAbstract implementation in XTReadingWritingTest. > Maybe XTReadingWritingTest, XTInfiniteReadingWritingTests and > XTFiniteReadingWritingTests should be moved to the Terminals-Tests package? I could go both ways on this one. They are in CoreTests because the tests themselves test core functionality, but you can't run any of those without the Terminals, so I can see the argument your way too. I wonder though if the move buys us much. There won't be much left in CoreTests if we move the tests that need terminals, it will be basically just the buffer tests. So running the CoreTests without the rest won't tell you much about the state of the port. Thanks for the additional details on the test failures. Cheers! Martin

Jan. 12, 2011

Re: [Pharo-project] [SPAM] Default Theme (was [update 1.2] #12297)

by Sven Van Caekenberghe

On 12 Jan 2011, at 16:41, Torsten Bergmann wrote: >> - Glamourous setting as default. > > Arrghhh ... how ugly. I like the Watery2 theme > more and would like to keep it as default. > Any chance we can put it back ... should we > vote? > > It is also used in various screenshots and > screencasts and has given Pharo already a visual > identity. > > So why switch to Glamourous as default? > > Thx > T. de gustibus et coloribus non est disputandum this cannot be settled I guess. Sven

Jan. 12, 2011

Re: [Pharo-project] [update 1.2] #12297

by Sven Van Caekenberghe

On 12 Jan 2011, at 16:30, StÃ©phane Ducasse wrote: > - Glamourous setting as default. Yes! Maybe a bit dull, but clean and professional, my favorite! Sven

Jan. 12, 2011

Re: [Pharo-project] Default Theme (was [update 1.2] #12297)

by Mariano Martinez Peck

On Wed, Jan 12, 2011 at 4:41 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > >- Glamourous setting as default. > > Arrghhh ... how ugly. I like the Watery2 theme > more and would like to keep it as default. > Any chance we can put it back ... should we > vote? > > It is also used in various screenshots and > screencasts and has given Pharo already a visual > identity. > > So why switch to Glamourous as default? > +1 This is a radical change and I don't agree. > > Thx > T. > -- > Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir > belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de > >

Jan. 12, 2011

[Pharo-project] Default Theme (was [update 1.2] #12297)

by Torsten Bergmann

>- Glamourous setting as default. Arrghhh ... how ugly. I like the Watery2 theme more and would like to keep it as default. Any chance we can put it back ... should we vote? It is also used in various screenshots and screencasts and has given Pharo already a visual identity. So why switch to Glamourous as default? Thx T. -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de

Jan. 12, 2011

Re: [Pharo-project] Issue 2897 in pharo: Compiler fixes from eliot

by pharo＠googlecode.com

Updates: Status: Fixed Comment #2 on issue 2897 by stephane.ducasse: Compiler fixes from eliot http://code.google.com/p/pharo/issues/detail?id=2897 (No comment was entered for this change.)

Jan. 12, 2011

[Pharo-project] [update 1.2] #12297

by StÃ©phane Ducasse

12297 ----- - Issue 3525: Compiler>>parserClass is broken and does not querying the class for providing the parser class. Thanks Igor Stasenko. - Glamourous setting as default.

Jan. 12, 2011

Re: [Pharo-project] Issue 2454 in pharo: decompiler fix

by pharo＠googlecode.com

Updates: Status: Accepted Labels: -Milestone-1.2 Milestone-1.3 Comment #6 on issue 2454 by stephane.ducasse: decompiler fix http://code.google.com/p/pharo/issues/detail?id=2454 In 12295 we tested with igor and without the fix in pharo we get the same as in Squeak: test | one two | two := 2. ^{[one := 1]. [ [one + two] value]} is decompiled into test | two one | two := 2. ^ {[one := 1]. [[one + two] value]}

Jan. 12, 2011

Re: [Pharo-project] Issue 2454 in pharo: decompiler fix

by pharo＠googlecode.com

Updates: Status: Fixed Comment #5 on issue 2454 by stephane.ducasse: decompiler fix http://code.google.com/p/pharo/issues/detail?id=2454 (No comment was entered for this change.)

Jan. 12, 2011