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

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

Jan. 12, 2011

mkobetic(a)gmail.com wrote: > 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. Hm, I'm getting the same result with PharoCore-1.2beta-12294 running on Cog VM. I simply copied the image into my one-click installation, hope that's correct way to do it. Makes me wonder if this is OS dependent problem. I'm running on Fedora 14 (x86_64).

2 1

Re: [Pharo-project] senders vs implementors
by Marcus Denker Jan. 12, 2011

Jan. 12, 2011

On Jan 12, 2011, at 3:25 PM, Tudor Girba wrote: > Hi, > > I think I encountered an error in allImplementorsOf:, but I am not quite sure and I wanted to run it by you first. > > If you evaluate > (self systemNavigation allSendersOf: #browse) anyOne sourceCode. > > you get the source as expected. > > > However, if you evaluate: > (self systemNavigation allImplementorsOf: #browse) anyOne sourceCode. > > you get an error. > > The last snippet used to work just fine in Pharo 1.1.1. > > > I consider it a bug. What do you think? Yes, this is a bug. (the whole MethodReference stuff is right now in the process of being re-designed...) One workound is to get the real method and ask it for the code: (self systemNavigation allImplementorsOf: #browse) anyOne compiledMethod getSource. arcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

2 1

[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