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

Re: [Pharo-project] where to report vm crashes? (while running Moose tests)
by Stephan Eggermont March 14, 2013

March 14, 2013

>It would be good to have a parallel job, but the problem is that you will >get a message saying that the VM is too old for the Pharo 2.0 image. I started the latest MOOSE image on Eliots latest VM on mac. It still has the 'old vm' warning. Adding a monticello repository (directory) doesn't work. Tests are still running Stephan

8 28

[Pharo-project] fogbugz feature requests
by Camillo Bruni March 14, 2013

March 14, 2013

Apparently fogbugz has their own nice stackexchange instance (I still wanted that for pharo). And there is a nice feature request to list related bugs if you report one, something I have been missing for a while at the google issue tracker. And something I ran into a couple of times myself by not searching for other bugs first. so vote up! http://fogbugz.stackexchange.com/questions/5318/feature-request-discourage-…

1 0

[Pharo-project] WhatsUp from: 2013-03-11 until: 2013-03-24
by seaside＠rmod.lille.inria.fr March 14, 2013

March 14, 2013

Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! ### Here's what I've been up to since the last WhatsUp: - $HEROIC_ACHIEVEMENTS_OR_DISMAL_FAILURES_OR_SIMPLE_BORING_NECESSARY_TASKS ### What's next, until 2013-03-24 (*): - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION (*) we'll be expecting results by then ;)

9 12

Re: [Pharo-project] Debugger-driven development (was Re: WhatsUp from: 2013-03-11 until: 2013-03-24)
by Stephan Eggermont March 14, 2013

March 14, 2013

Frank wrote: >I'd love to hear more about your presentation. I've been thinking how >to run a kind've live-coding demonstration at work, showing how a >Smalltalk debugger is so clearly superior to what other folk have. It is inspired by Jason Ayers' session at SPA and XPDays Benelux. It will be a short session, as there will be 2 other presentations on non-intuitive subjects. Devnology has a diverse public with mostly java and c# developers. Agilists in those environments are likely to advocate writing a test instead of using a debugger, and are often unaware of the incremental development possibilities offered by the smalltalk debugger. >(Squeak trunk now lets you create methods not just on an MNU but also >where people have things like "self subclassResponsibility", "self >notYetImplemented" or "self shouldBeImplemented" flags such that you >can debug-edit-and-continue.) Yes, I saw your blog post yesterday. Cool. That's definitely something I would like to show. I haven't given much thought yet to which debugger I want to use. I'm tempted to use the GTDebugger and modify it during the session (to add your new extensions perhaps) but that is something I have to try and time first. It might be too much magic. Stephan

3 3

[Pharo-project] Fuel 1.8 -> 1.9 migration (was: Re: please test 2.0)
by Martin Dias March 14, 2013

March 14, 2013

Hi Yanni, Could you migrate all your objects to the new format? Best regards, Martin On Fri, Mar 1, 2013 at 10:49 PM, Yanni Chiu <yanni(a)rogers.com> wrote: > > > On 01/03/13 1:54 PM, Martin Dias wrote: >> >> I'm sorry but AFAIK you won't be able to materialize in 1.8.x the files >> you serialized with 1.8. Maybe Max has some trick to do it? > > > I got an exception: > > FLBadVersion: Materialization error. Unexpected stream version 18 where > it should be 182. > > I disabled the version check, and things loaded fine. But, I've yet to find > a saved file with a Date or DateAndTime instance. > > >

2 1

[Pharo-project] [update 2.0] #20591
by Marcus Denker March 14, 2013

March 14, 2013

20591 ----- 10014 World menu > System > Switch User serves no purpose https://pharo.fogbugz.com/f/cases/10014/World-menu-System-Switch-User-serve… 10004 SmalltalkImage current reportCPUandRAM > DNU https://pharo.fogbugz.com/f/cases/10004/SmalltalkImage-current-reportCPUand… Diff information: http://ss3.gemstone.com/ss/Pharo20/Tools-MarcusDenker.1059.diff http://ss3.gemstone.com/ss/Pharo20/KeyChain-MarcusDenker.30.diff

1 0

[Pharo-project] rpackage transition
by Tudor Girba March 14, 2013

March 14, 2013

Hi, When we started with RPackage there was a debate as to the strategy regarding the mapping. I advocated 1-to-1 mapping of categories to RPackage, and it seems this is what we now have. The detailed plan looked as follow: --- Stage 1: Get RPackage in the image and pretend that it acts like a smart cache for categories. Everything is expressed in terms of categories and mirrored in RPackages. Tools can now be built on top of RPackage. At this stage, no modification is needed and the new tools will work next to the old ones. Stage 2: Leave the logic of Monticello loading as it is now (n-to-1 Categoeies-to-MonticelloPackage), but modify Monticello publishing to rely on 1-to-1 RPackage-to-MonticelloPackage. This will basically force people to start changing the configurations. Stage 3: Change the Monticello loading to only allow 1-to-1 RPackage-to-MonticelloPackage. At this point, we can safely remove the Categories. --- Now we passed Stage 1 which is great. At this point, everyone can work like before, but are encouraged to create explicit Monticello packages out of categories. Next, I would like to propose that for Pharo 3.0 we go for Stage 2 and modify slightly Monticello publishing. Cheers, Doru -- www.tudorgirba.com "Quality cannot be an afterthought."

4 6

[Pharo-project] Pharo Download Page needs update
by Stefan Marr March 14, 2013

March 14, 2013

Hi: Was just trying to download the latest image via [1]. However, the linked latest.zip does not contain the new .sources file. And it looks like it hasn't been part of the zip. So, would be good if the download page could link to it. Meanwhile, I took it from the all-in-one. Thanks Stefan [1] http://www.pharo-project.org/pharo-download/beta-2-0 -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525

2 1

[Pharo-project] Fwd: Pharo and scaled decimals
by Marcus Denker March 14, 2013

March 14, 2013

I added this as issue 10016 to the new tracker. Begin forwarded message: > From: David Gorisek <david.gorisek(a)e-racuni.com> > Subject: Re: Pharo and scaled decimals >> >> Hello all, >> >> I am testing Pharo and I have noticed that the Pharo compiler does not treat ScaledDecimals the same way they are treated in other Smalltalk dialects (e.g. VW, VAST, Dolphin, STX, etc.). >> >> For example the following is a valid code representing an instance of ScaledDecimal/FixedPoint in all other dialect. >> >> 1.0s + 2.0s >> >> In Phare the code above wont compile, it has to be written as: >> >> 1.0s1 + 2.0s1 >> >> So I have made the following quick change to make Pharo compatible with other Smalltalk dialects. Maybe this change could be included in the next version of Pharo? >> >> SqNumberParser>>#readScale >> "read the scale if any (stored in instVar). >> Answer true if found, answer false if none. >> If scale letter is not followed by a digit, this is not considered as an error. >> Scales are always read in base 10, though i do not see why..." >> >> scale := 0. >> sourceStream atEnd >> ifTrue: [ ^ false ]. >> (sourceStream peekFor: $s) >> ifFalse: [ ^ false ]. >> scale := self nextUnsignedIntegerOrNilBase: 10. >> scale >> ifNil: [ >> scale := 0. >> (sourceStream peek ifNil: [false] ifNotNil: [ :nextChar | nextChar isLetter]) >> ifTrue: [ >> sourceStream skip: -1. "ungobble the s" >> ^ false ] >> ifFalse: [ ^ true ] ]. >> ^ true >> >> >> >> > >

2 2

[Pharo-project] WhatsUp from: 2013-03-11 until: 2013-03-24
by seaside＠rmod.lille.inria.fr March 14, 2013

March 14, 2013

Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! ### Here's what I've been up to since the last WhatsUp: - $HEROIC_ACHIEVEMENTS_OR_DISMAL_FAILURES_OR_SIMPLE_BORING_NECESSARY_TASKS ### What's next, until 2013-03-24 (*): - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION (*) we'll be expecting results by then ;)

8 9