June 2013 - Pharo-dev - lists.pharo.org

SmalltalkHub misleading stats?
by Mariano Martinez Peck June 7, 2013

June 7, 2013

Hi guys. In my own instance of shub that I am running, the number of "packages uploaded" shown in the home of smalltalkhub looked like 10k, while I only have around 10 packages. In public smalltalkhub it says 60997. So I wonder....what they actually are? can they actually be package VERSIONS uploaded and not just packages? Thanks! -- Mariano http://marianopeck.wordpress.com

4 3

[update 3.0] #30184
by Marcus Denker June 7, 2013

June 7, 2013

30184 ----- 10857 Add new public API to old compiler https://pharo.fogbugz.com/f/cases/10857 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Compiler-MarcusDenker.477.diff

2 1

Please review Cases 10785 and 10314
by Sean P. DeNigris June 7, 2013

June 7, 2013

10785 Auto-complete protocol renaming https://pharo.fogbugz.com/f/cases/10785/Auto-complete-protocol-renaming 10314 Debugger: create better argument names https://pharo.fogbugz.com/f/cases/10314/Debugger-create-better-argument-nam… ----- Cheers, Sean -- View this message in context: http://forum.world.st/Please-review-Cases-10785-and-10314-tp4691989.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

3 2

I cannot merge 10828 and 10830 because the system does not find
by StÃ©phane Ducasse June 7, 2013

June 7, 2013

> From: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Subject: I cannot merge 10828 and 10830 because the system does not find > Date: June 7, 2013 11:49:47 AM GMT+02:00 > To: Esteban Lorenzano <estebanlm(a)gmail.com> > > Morphic-Base-EstebanLorenzano.3 > I do not understand why especially since the file is in main. > > Stef

3 3

Re: [Pharo-dev] Necessity of TDD with Smalltalk
by Stephan Eggermont June 7, 2013

June 7, 2013

Paul wrote: >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? Test-driven development works well when you have some idea of where you want to go. If you don't know yet what your first test could look like, the powerful debugging environment of Smalltalk allows you to do some fast experiments. Then you might want to switch to TDD, as there are two ideas in TDD that are not covered by having a good debugging environment: - don't write more code than you have tests for, so the design is really driven by the tests - the tests provide insurance that you'll notice when something breaks. Writing and re-writing tests is what helps you get to a simple design. Tests need refactoring and DRY just as much as other code. Stephan

7 11

30181 Kernel package Dirty
by Sean P. DeNigris June 7, 2013

June 7, 2013

1. Download a fresh 30181 2. In MC Browser, view "Changes" on Kernel The package will show a handful of changes and be marked dirty ----- Cheers, Sean -- View this message in context: http://forum.world.st/30181-Kernel-package-Dirty-tp4692004.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

3 3

[update 3.0] #30183
by Marcus Denker June 7, 2013

June 7, 2013

30183 ----- 10813 Update Opal to latest version in image https://pharo.fogbugz.com/f/cases/10813 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/OpalCompiler-Tests-MarcusDenk… http://smalltalkhub.com/mc/Pharo/Pharo30/main/OpalCompiler-Core-MarcusDenke…

1 0

Class comments... we want them but, ... hard to convince the system at this point in time
by phil＠highoctane.be June 7, 2013

June 7, 2013

https://pharo.fogbugz.com/default.asp?10861 Still, this happens when doing a mcz load. Wondering... Phil

1 0

June 7, 2013

30182 ----- 10115 MCClassTraitDefinition DNU printDefinitionOn: https://pharo.fogbugz.com/f/cases/10115 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Monticello-StephaneDucasse.80…

1 0

Problem with setting class comments
by Mariano Martinez Peck June 7, 2013

June 7, 2013

Hi guys. I think I found a problem with class comments. The default method #classComment: in TClassAndTraitDescription does the following: classComment: aString "Store the comment, aString or Text or RemoteString, associated with the class we are orgainzing. Empty string gets stored only if had a non-empty one before." ^ self classComment: aString stamp: '<historical>' Why it puts a '<historical>' stamp instead of say "Author changeStamp" ? Nautilus uses this message. So as a consequence, when you edit and save a class comment with Nautilus, to get a <historical> stamp.... I am using Pharo 2.0. Bug? -- Mariano http://marianopeck.wordpress.com

3 3