- Pharo-dev - lists.pharo.org

[Pharo-project] [update 1.2] #12300
by StÃ©phane Ducasse Jan. 12, 2011

Jan. 12, 2011

12300 ----- - Issue 3535: I broke SpaceTally in Pharo 1.2

2 1

[Pharo-project] Default Theme (was [update 1.2] #12297)
by Torsten Bergmann Jan. 12, 2011

Jan. 12, 2011

>- 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

4 3

Re: [Pharo-project] Issue 2897 in pharo: Compiler visitor fixes
by pharo＠googlecode.com Jan. 12, 2011

Jan. 12, 2011

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.)

1 1

Re: [Pharo-project] Xtreams up to date
by mkobetic＠gmail.com Jan. 12, 2011

Jan. 12, 2011

"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

1 0

Re: [Pharo-project] Issue 2897 in pharo: Compiler fixes from eliot
by pharo＠googlecode.com Jan. 12, 2011

Jan. 12, 2011

Comment #1 on issue 2897 by siguctua: Compiler fixes from eliot http://code.google.com/p/pharo/issues/detail?id=2897 Here the changeset Attachments: Compiler-eem.172.1.cs 10.7 KB

1 1

[Pharo-project] Issue 3533 in pharo: add Dictionary>>at:ifAbsentPutValue:
by pharo＠googlecode.com Jan. 12, 2011

Jan. 12, 2011

Status: Accepted Owner: stephane.ducasse Labels: Milestone-1.3 New issue 3533 by stephane.ducasse: add Dictionary>>at:ifAbsentPutValue: http://code.google.com/p/pharo/issues/detail?id=3533 Igor suggests to add this method in dictionary to avoid to use block closure when not necessary. Here the block has to be passed and executed. When you know the value you want to put this is extra work. at: key ifAbsentPut: aBlock "Return the value at the given key. If key is not included in the receiver store the result of evaluating aBlock as new value." ^ self at: key ifAbsent: [self at: key put: aBlock value]

1 1

Re: [Pharo-project] Xtreams up to date
by mkobetic＠gmail.com Jan. 12, 2011

Jan. 12, 2011

mkobetic(a)gmail.com wrote: > Hm, that is odd. Maybe I need to try a fresh load and see. I normally get a single failure in one of the socket tests which we haven't tracked down yet. Can you give me a bit more about the kind of errors and failures you see. Does it look like stuff is completely missing ? Maybe I messed up the publishing after the various class moves that I did recently. No, fresh load into one-click 1.1.1 works for me. I guess I need to try different versions.

1 0

[Pharo-project] Xtreams up to date
by Torsten Bergmann Jan. 12, 2011

Jan. 12, 2011

Used your Gofer script in Pharo-core 1.2 and Pharo-dev 1.1., but after loading I run the tests with many errors and failures... Is it Squeak only? (which I doubt since the loading script uses Gofer instead of Installer and Gofer is Pharo while Installer is Squeak). Would be nice if we could have a working ConfigurationOfXtream in http://squeaksource.com/MetacelloRepository so it is easy accessible and working packages are versioned together using Metacello. Thx T. -- NEU: FreePhone - kostenlos mobil telefonieren und surfen! Jetzt informieren: http://www.gmx.net/de/go/freephone

3 2

Re: [Pharo-project] Xtreams up to date
by mkobetic＠gmail.com Jan. 12, 2011

Jan. 12, 2011

"Torsten Bergmann"<astares(a)gmx.de> wrote: > Used your Gofer script in Pharo-core 1.2 and Pharo-dev 1.1., > but after loading I run the tests with many errors and failures... Hm, that is odd. Maybe I need to try a fresh load and see. I normally get a single failure in one of the socket tests which we haven't tracked down yet. Can you give me a bit more about the kind of errors and failures you see. Does it look like stuff is completely missing ? Maybe I messed up the publishing after the various class moves that I did recently. > Is it Squeak only? (which I doubt since the loading script uses > Gofer instead of Installer and Gofer is Pharo while Installer is > Squeak). I'm currently using Pharo OneClick image version 1.1.1 directly from the download page. Currently I'm running using the old VM as Cog once crashed on me and I lost a lot of changes. But both VMs seem to run the tests OK. > Would be nice if we could have a working ConfigurationOfXtream in http://squeaksource.com/MetacelloRepository so it is easy accessible and working packages are versioned together using Metacello. Yes, I probably need to do that as well. So far I was a bit discouraged mostly by my ignorance. I'm not up to speed on metacello yet, there don't seem to be any tools pre-loaded in the one click image, and I don't know what should one load to get some. I was able to figure out how to use ConfigurationOfFFI but in the end I ended up running the class side load method by hand. The other issue I had was that it seems a metacello configuration requires a bit of maintenance, it seems like you have to manually update the versions when you publish something new. That may be less of a problem now after the updates are done. The Gofer expression seemed a lot easier, and I hoped sufficient for now. Anyway, unless someone beats me to it I'll see what I can do about creating a configuration. Martin

1 0

[Pharo-project] Issue 3525 in pharo: Compiler>>parserClass is broken and does not querying the class for providing the parser class
by pharo＠googlecode.com Jan. 12, 2011

Jan. 12, 2011

Status: Accepted Owner: siguctua New issue 3525 by siguctua: Compiler>>parserClass is broken and does not querying the class for providing the parser class http://code.google.com/p/pharo/issues/detail?id=3525 In the following: Compiler>>parserClass ^parser ifNil: [self class parserClass] ifNotNil: [parser class] 'self class' should actually be 'class parserClass' So, any class could override the default parser by own. In that way a default parser class is answered by Behavior, not by Compiler. A Compiler class>>parserClass is useless. But even more than that, due to initializing 'parser' ivar in Compiler>>new, it never gets to that code, and evaluating 'parser class' So, a class can't specify a custom parser class to compiler.

5 17