- Pharo-dev - lists.pharo.org

fogbugz subcases
by Camillo Bruni June 10, 2013

June 10, 2013

I have seen different strategies on using subcases on fogbugz and to me only one way makes sense: Subcases are dependencies Only if all the subcases are finished you can resolve a parent case. I think that comes implicitly from the fact that you cannot have more than one parent. Additionally the typical use-case for me is that you have to split up a complex bug / task into manageable subparts. what do you think?

2 1

Re: [Pharo-dev] FogBugz (Case [Issue]10840) Collection - WeakSet>>#size utterly broken
by Camille Teruel June 10, 2013

June 10, 2013

On 7 juin 2013, at 11:19, Pharo Issue Tracker wrote: > A FogBugz case was edited by Stephane Ducasse. > > Case ID: 10840 > Title: WeakSet>>#size utterly broken > Status: Resolved (Fix Review Needed) > Category: Bug > Project: Collection > Area: Misc > Priority: 3 - Must Fix > Milestone: Pharo3.0: 30/03/2014 > Assigned To: Camille Teruel > > URL: https://pharo.fogbugz.com/f/cases/10840 > > Last message: > Please can you send a mail to the mailing-list so that we all discuss this problems. Hello everyone, WeakSet>>#size is broken as demonstrated by the following snippet: set := WeakSet new. set add: Object new. Smalltalk garbageCollect. set size. "answers 1 instead of 0" That is because a WeakSet has no mean to know when its items get garbage collected, and thus the tally cannot be updated. So we need to override #size in Weak, I propose: size | counter | counter := 0. self do: [ :e | counter := counter + 1 ]. ^ counter But that it rather inefficient for such a simple query. Any proposition? The bug entry is: https://pharo.fogbugz.com/f/cases/10840 > > > If you do not want to receive automatic notifications anymore, change your preferences in the Options screen. (https://pharo.fogbugz.com/default.asp?pg=pgPrefs)

5 8

[update 3.0] #30190
by StÃ©phane Ducasse June 10, 2013

June 10, 2013

30190 ----- 10779 - Parsing faulty method ends with incorrect ast. Thanks Gisela https://pharo.fogbugz.com/default.asp? 10801 - Use UTF8 encoding in MC snapshot source.st https://pharo.fogbugz.com/default.asp?10801 Thanks nicolas cellier and sven. Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/System-Installers-StephaneDuc… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Monticello-StephaneDucasse.81… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Compression-StephaneDucasse.1… http://smalltalkhub.com/mc/Pharo/Pharo30/main/AST-Tests-Core-StephaneDucass… http://smalltalkhub.com/mc/Pharo/Pharo30/main/AST-Core-StephaneDucasse.166.…

1 0

Necessity of TDD with Smalltalk
by Paul Davidowitz June 10, 2013

June 10, 2013

It seems to me that a big reason for developing via writing tests first (Test Driven Development) is that the tests serve as a debugging tool -- if a test breaks, then the last piece of (non-test) code that change is likely the culprit. But with the powerful debugging environment that comes with Smalltalk, I am wondering of the utility of TDD (TDD is big in the Ruby camp perhaps for a reason). After all, writing and re-writing the tests becomes quite a non-trivial chore (not to mention that the tests themselves could be buggy). So my question: Is it ok in Smalltalk to write tests afterwards? Is it even perhaps recommended? - Paul

7 11

[regression reporter]regression occurred
by no-reply＠ci.inria.fr June 10, 2013

June 10, 2013

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=ma… 2 regressions found. Tests.Monticello.MCMczInstallerTest.testInstallFromFile Tests.Monticello.MCMczInstallerTest.testInstallFromStream

1 0

[regression reporter]regression occurred
by no-reply＠ci.inria.fr June 10, 2013

June 10, 2013

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=li… 2 regressions found. Tests.Monticello.MCMczInstallerTest.testInstallFromFile Tests.Monticello.MCMczInstallerTest.testInstallFromStream

1 0

Slaves are back online
by StÃ©phane Ducasse June 10, 2013

June 10, 2013

Hi guys the CI service of Inria is back online and our slaves too (they are investigating the reasons of the problems). So we will be able to restart to work in a more relaxed way. for this week, we have some deadline for the ESUG workshop and we want to put athens in Pharo + the usual integration Stef

1 0

Re: [Pharo-dev] Tabs
by Stephan Eggermont June 9, 2013

June 9, 2013

Looks great, Ben! A feature request: Can we have more visual feedback on which panel belongs with which tab when multi-selecting? Stephan

2 1

Clickable web links inside class comments , possible ?
by dimitris chloupis June 9, 2013

June 9, 2013

As the titles says is it possible to have clickable web links inside the comment of a class so when I click it the default web browser pops open in the webpage , or am I asking too much ?

5 15

Re: [Pharo-dev] [Pharo-fuel] Corrupt BlockClosure
by Max Leske June 9, 2013

June 9, 2013

I still can't tell you how the closure become corrupted but I now know how to get rid of it. I'm also pretty sure that closures work fine (as you say) and that I probably mistook the same corrupt instance for different instances. Cheers, Max > How does that happen? It doesn't happen in normal use. I can see how Fuel > does it. I can't see how non-Fuel use would do it (other than deliberate > construction). A closure is created by evaluating the push-closure > bytecode in a specific method, and when this closure is created, it refers, > through its outer context to the method object containing the evaluated > push-closure bytecode. Since the closure's startpc is derived from the pc > of the push-closure bytecode, there is always a match. > > However, when Fuel serializes (IIRC) it serializes a *reference* to a > method in the form of a class-name,selector pair, and this approach can > obviously yield an invalid method. > > therefore I think it much more likely that what you;re seeing is a result > of a bug in Fuel than some systemic problem with closures.

1 0