- Pharo-dev - lists.pharo.org

[Pharo-project] New Pharo-dev based on 10279
by Damien Cassou April 18, 2009

April 18, 2009

http://pharo-project.org/download -- Damien Cassou http://damiencassou.seasidehosting.st

3 6

[Pharo-project] [ANN] closureAsText and literalsDo:
by StÃ©phane Ducasse April 18, 2009

April 18, 2009

:) Thanks hernan and nicolas Next the new event system and we should be able to really focus on going beta. Stef

1 0

[Pharo-project] New Pharo-dev based on 10277
by Damien Cassou April 17, 2009

April 17, 2009

http://pharo-project.org/download -- Damien Cassou http://damiencassou.seasidehosting.st

4 8

[Pharo-project] is it now possible to load script again
by StÃ©phane Ducasse April 17, 2009

April 17, 2009

Damien with the changes of mime types and others is it possible to load scripts? Stef

2 1

[Pharo-project] [ANN] 10279 closure fixes
by StÃ©phane Ducasse April 16, 2009

April 16, 2009

- Fix for http://code.google.com/p/pharo/issues/detail?id=726 add #sender method to BlockClosure - Add messages to BlockClosure to fix issue http://code.google.com/p/pharo/issues/detail?id=722 - Issue 746: missing package for Closure and friends - Work-around for issue http://code.google.com/p/pharo/issues/detail?id=739 We cannot run some Debugger tests profiled... ... because Debugger would reset Tally Timer class var. Work around is to put a Timer ifNotNil: protection... - fix closureParser invocation (should probably clean the rest) Thanks nicolas. :)

1 0

[Pharo-project] Unicode fonts and MultiCompositionScaner
by Andrey Larionov April 16, 2009

April 16, 2009

Investigating reasons of fail FontTest tests i found bug in MultiCompositionScaner (or it maybe some related class). Looks like what Character value: 257 had a special meaning in squeak. If not use StrikeFont everything is well, but if you choose FreeType font the doing something (Character value: 257) asString asTextMorph openInWorld creates an endles loop in composer. It founds character falls in crossedX method (this character is stopCondition) and then remove character from composition and starts again.

2 1

[Pharo-project] WeakArray class>>#finalizationProcess
by Markus Fritsche April 16, 2009

April 16, 2009

Hello, I just noticed that WeakArray class>>#finalizationProcess won't compile with the with the assignment to block args set to off. Is it okay to change that in the preferences or is the finalization process broken then? Kind regards, Markus

4 10

April 16, 2009

because after this is much more difficult for me to integrate For example now I have new event mixed with closure fixes.... This is simple to publish a slice you create it and add the dirty packages as dependent. Stef

4 4

[Pharo-project] The System Package
by Alexandre Bergel April 16, 2009

April 16, 2009

Dear All, It seems that the class category 'System' is registered as a package and each System-XXX category is both a package and a class category. As a consequence, System is a package that contains sub-packages, and 'System-Object Storage' is listed as a package. I suggest that package name should never contain a '-'. This require quite some discipline to not mess up the thing. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

3 4

April 16, 2009

Begin forwarded message: > From: Eliot Miranda <eliot.miranda(a)gmail.com> > Date: April 2, 2009 11:09:14 PM CEDT > To: Lukas Renggli <renggli(a)iam.unibe.ch> > Cc: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>, Marcus Denker <denker(a)iam.unibe.ch > >, Michael Rueger <m.rueger(a)acm.org>, Adrian Lienhard <alienhard(a)netstyle.ch > >, John McIntosh <johnmci(a)smalltalkconsulting.com> > Subject: Re: how can we sync > > > > On Thu, Mar 26, 2009 at 1:24 AM, Lukas Renggli > <renggli(a)iam.unibe.ch> wrote: > Something related ... > > In noticed that there are numerous places in the Pharo code that > cannot be re-compiled anymore, because they assign to block > parameters. There are two cases: > > 1. Things along the following example were a bug in the first place > anyway, and can be easily fixed: > > aCollection inject: 0 into: [ :s :e | s := s + e ] > > 2. Then there are also various places where code seems to nil temps > to avoid garbage collection issues, such as in > WeakArray>>#finalizationProcess. > > FinalizationDependents do: > [:weakDependent | > weakDependent ifNotNil: > [weakDependent finalizeValues. > "***Following statement is required to keep > weakDependent > from holding onto its value as garbage.***" > weakDependent := nil]] > > I think this is no longer necessary and can be fixed by simply > removing that assignment as well, however I wanted to get a > confirmation by Eliot before submitting a batch of fixes in various > places of Pharo. > > First of all there is a preference for backward-compatibility (see > preferences category compiler). Turn on > allowBlockArgumentAssignment and the old code can still be compiled > (and I believe wrks as it did (yuck)). > > The bootstrap enables this preference while it is bootstrapping and > then turns it off once done so that one is discouraged from > assigning to block arguments in new code. At least that's the > intent. But since we tend to load more code than we write I guedss > the intent isn't that helpful :) > > Second, yes you can get rid of a number of redundant assignments > that nil arguments to prevent retention. Find attached a change set > (Closure Usage Fixes) that includes a few from my image. These > either move temporaries local to a block inside the block (useful > for performance) or delete unnecessary assignments. But beware; > these changes should be compared carefully against the Pharo image > as they apply to the current state of the Qwaq code base which could > easily be incompatible. Best to compare carefully, so to this end... > > Third, I wrote a tool to automatically edit methods with method- > level temps that are only used at block level. There's a rather > stupid blog post on developing this. Stupid, because it tries to > illustrate programming in the debugger at the same time and I think > it ends up beng confused. Anyway, find the tool attached. > Unsupervised usage is "TempScopeEditor edit". There is an instance > side method editNoCompile that you can use to look at the output > without applying the change, but you'll have to rte tool support to > make this useful. I have a hack for side-by-side method comparisons > based on MethodReference if you want it but I suspect you have more > familiar tools to hand. > > Best regards > Eliot > > > > > > Cheers, > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > >

2 8