September 2017 - Pharo-dev - lists.pharo.org

Class side method is missing in obsolete class after the class is removed from system
by NicolÃ¡s Papagna Maldonado Sept. 25, 2017

Sept. 25, 2017

Im writing some tests that needs to create classes dynamically. During the tearDown phase, i remove these classes using #removeFromSystem. I noticed that running these tests became more and more slower as i kept adding more tests. Using "Run Profiled" from Test Runner, i found out ChangesLog>>#logClassRemoved: was responsible of about 43% of the execution time: logClassRemoved: annoucement annoucement classRemoved acceptsLoggingOfCompilation ifTrue: [ self logChange: 'Smalltalk globals removeClassNamed: #', annoucement classRemoved name ]. Based on that, i overrided #acceptsLoggingOfCompilation on the new classes to avoid these changes being written down to disk (the classes are disposable after all), but ChangeSet kept doing it. I confirmed this by inspecting annoucement classRemoved acceptsLoggingOfCompilation which returns true, ignoring the overriding implementation i provided. #acceptsLoggingOfCompilation overriding implementation seems to be lost during the #removeFromSystem call. Specifically, during Behavior>>#obsolete, which is called during Class>>#obsolete "Change the receiver and all of its subclasses to an obsolete class." self == Object ifTrue: [^self error: 'Object is NOT obsolete']. self setName: 'AnObsolete' , self name. Object class instSize + 1 to: self classSide instSize do: [:i | self instVarAt: i put: nil]. "Store nil over class instVars." self classPool: nil. self sharedPools: nil. self hasClassSide ifTrue: [ self theMetaClass obsolete]. <======= HERE self propertyAt: #obsolete put: true. super obsolete. When i checked Behavior>>#obsolete, i found out the method dictionary is emptied, losing my implementation of #acceptsLoggingOfCompilation Behavior>>obsolete "Invalidate and recycle local methods, e.g., zap the method dictionary if can be done safely." self canZapMethodDictionary ifTrue: [self methodDict: self emptyMethodDictionary]. <======= HERE self hasTraitComposition ifTrue: [ self traitComposition traits do: [:each | each removeUser: self]] I don't know if this is by design or not, but it seems that the class that gets announced when removed, is not exactly the same as the original. Any thoughts/recommendations? -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

2 2

[Pharo 7.0-dev] Build #154: 20470 run headless without writable changes file
by ci-pharo-ci-jenkins2＠inria.fr Sept. 25, 2017

Sept. 25, 2017

There is a new Pharo build available! The status of the build #154 was: SUCCESS. The Pull Request #315 was integrated: "20470 run headless without writable changes file" Pull request url: https://github.com/pharo-project/pharo/pull/315 Issue Url: https://pharo.fogbugz.com/f/cases/20470 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #153: 204607-Rename-package-Collections-DoubleLinkedListTests-into-Collections-DoubleLinkedList-Tests
by ci-pharo-ci-jenkins2＠inria.fr Sept. 25, 2017

Sept. 25, 2017

There is a new Pharo build available! The status of the build #153 was: SUCCESS. The Pull Request #313 was integrated: "204607-Rename-package-Collections-DoubleLinkedListTests-into-Collections-DoubleLinkedList-Tests" Pull request url: https://github.com/pharo-project/pharo/pull/313 Issue Url: https://pharo.fogbugz.com/f/cases/204607 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Calypso question
by Stephane Ducasse Sept. 25, 2017

Sept. 25, 2017

Hi denis I'm doing a pass on the architecture of calypso chapter :) as a way to force me to understand it better. Now I do not understand why the following does not work. | env classScope | env := ClySystemNavigationEnvironment currentImage. classScope := env selectScope: ClyClassScope of: {Point. Collection}. classScope allClasses another question packageScope query: (ClyMessageSenders of: #(do: x)) It is returning all the senders of do: and the senders of x or returning all the sender of do: and x Stef

3 13

[Pharo 7.0-dev] Build #152: 20449-System-SupportTests-package-should-be-renamed-to-System-Support-Tests
by ci-pharo-ci-jenkins2＠inria.fr Sept. 25, 2017

Sept. 25, 2017

There is a new Pharo build available! The status of the build #152 was: SUCCESS. The Pull Request #312 was integrated: "20449-System-SupportTests-package-should-be-renamed-to-System-Support-Tests" Pull request url: https://github.com/pharo-project/pharo/pull/312 Issue Url: https://pharo.fogbugz.com/f/cases/20449 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Re: [Pharo-dev] XPath chapter...
by Nicolas Anquetil Sept. 25, 2017

Sept. 25, 2017

To make all this documentation (booklets) more easily availbale, we could create a link to them in pharo itself for example as a special method, instance variable, or pragma (although I hate pragmas) in the Manifest? nicolas On 24/09/2017 16:27, StÃ©phane Ducasse wrote: > Hi > I'm fully convinced that we can have the best language if we do not > let people find their way super easily to do what they want to do we > will fail. > Documentation is KEY and I feel a bit alone. > Since I always wanted to learn XPath I started to write a chapter on > XPath. I hope that I did not write too many mistakes. > Pull requests are welcome here > https://github.com/SquareBracketAssociates/Booklet-Scraping > I would love to have one booklet on SAX and DOM handling. > Stef -- Nicolas Anquetil -- MCF (HDR) Project-Team RMod

1 0

Esteban's ChangeLog week of 18 September 2017
by estebanlm＠gmail.com Sept. 25, 2017

Sept. 25, 2017

Hello! This is my weekly ChangeLog, from 18 September 2017 to 24 September 2017. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=18/9/2017&to=24/9/2017 ChangeLog ========= 22 September 2017: ------------------ * Yesterday I worked on a new version of [metacello](https://github.com/Metacello/metacello/tree/pharo-6.1_dev) for Pharo 7.0 that incorporates latest fixes and specially, adds support for [tonel](https://github.com/pharo-vcs/tonel). After some tries, it is ready to be loaded and older Pharo versions can update executing: ---- Metacello new baseline: 'Metacello'; repository: 'github://metacello/metacello:pharo-6.1_dev/repository'; onConflict: [:ex | ex allow]; get; load ---- (do not fear, even if is a 6.1 branch, it will load properly also on Pharo 3.0+) Now, I discovered a remaining problem, [https://github.com/Metacello/metacello/issues/460](https://github.com/Metac… (I will fix this today) but most of the time this will be painless. 20 September 2017: ------------------ * ... and today we make linux i386 and x86 [headless VM](https://github.com/estebanlm/opensmalltalk-vm/tree/add-minheadless-vm) to build and (aparently), work :) 19 September 2017: ------------------ * Today Ronie and I finished the [build of real headless VMs](https://github.com/estebanlm/opensmalltalk-vm/tree/add-minheadless-vm) for macOS (both i386 and x86) versions. Now, we stopped here because linux is more complicated (oh yes, at least once :P): since all configuration is made with autoconf and Ronie's' builds are made with CMake, now we need to adapt more than we wanted. Anyway, tomorrow we'll do another pass... or maybe we will start with Windows, to see if this time also there is easier ;) cheers! Esteban

1 0

catalog seems down?
by Stephane Ducasse Sept. 24, 2017

Sept. 24, 2017

3 3

I love configuration comments!!!
by Stephane Ducasse Sept. 23, 2017

Sept. 23, 2017

Loads the XMLParserHTML library and related packages: (ConfigurationOfXMLParserHTML project version: #stable) load: #('default') The loadable groups are: default - XMLParserHTML, XMLParser, and XMLWriter with tests. Core - XMLParserHTML and XMLParser without XMLWriter or tests. CoreWithWriting - XMLParserHTML, XMLParser, and XMLWriter without tests. TX monty this is so simple and efficient.

1 0

[Pharo 7.0-dev] Build #151: Revert "20442-open-the-welcome-window. case 20442"
by ci-pharo-ci-jenkins2＠inria.fr Sept. 22, 2017

Sept. 22, 2017

There is a new Pharo build available! The status of the build #151 was: SUCCESS. The Pull Request #310 was integrated: "Revert "20442-open-the-welcome-window. case 20442"" Pull request url: https://github.com/pharo-project/pharo/pull/310 Issue Url: https://pharo.fogbugz.com/f/cases/revert Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0