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

ifTrue ifFalse shortcuts
by Peter UhnÃ¡k Aug. 10, 2016

Aug. 10, 2016

Hi, was removal of ifTrue/ifFalse shortcuts on purpose, or by accident? https://pharo.fogbugz.com/f/cases/16125/Nautilus-doesn-t-recognize-the-cmd-… (maybe was caused by switch to Rubric?) Peter

16 36

[Pharo-project] Status of SmallPOS
by Stephan Eggermont Aug. 9, 2016

Aug. 9, 2016

I noticed the SmallPOS on ss3 is under MIT license. AFAIK, it was GPLv3. When did this relicensing happen? Stephan

4 8

Loading an image crashes the VM
by Jan KurÅ¡ July 31, 2016

July 31, 2016

Hi, I am trying to open an image I saved a few days ago and I am getting this message (the whole log is attached): stack page bytes 4096 available headroom 2788 minimum unused headroom 3020 (Segmentation fault) Anyone experiencing something similar? I am running the latest pharo5 VM on Linux. Cheers, Jan

10 13

Smalltalk Hub on Chrome
by Sean P. DeNigris June 28, 2016

June 28, 2016

I noticed sometimes sthub hangs forever on Chrome (Version 34.0.1847.116 on Mavericks), but if I open it alongside in Safari, it loads fine... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Smalltalk-Hub-on-Chrome-tp4755788.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

9 15

spotter: top search for senders and references
by Tudor Girba June 4, 2016

June 4, 2016

Hi, With the latest GT integration, we also integrated the search for senders and references from the first step. Here is a detailed explanation about it, including what we still want to do, how itâs done, and how to discover what else is around: http://www.humane-assessment.com/blog/spotting-senders-references-with-gtsp… Please let us know what you think. Cheers, Doru -- www.tudorgirba.com www.feenk.com "Problem solving efficiency grows with the abstractness level of problem understanding."

8 30

doing stupid things (image will become unusable)
by Nicolai Hess June 1, 2016

June 1, 2016

Object := nil you can evaluate that piece of code, but afterwards .... Opal checks for assignments to read only variables (method arguments for example) and signals an error if you try to modify those vars. But it does not check globals. Should all Globals (OCLiteralVariable with isGlobalVar == true) be read only ? or can we distinguish global vars and class bindings?

6 10

Re: [Pharo-dev] Epicea tests failure under Windows (WAS: RE: [ANN] We are in "code freeze" for Pharo 5)
by Blondeau Vincent May 15, 2016

May 15, 2016

Very strange bug indeed that happens on windows machines that crashes the VM. I succeeded to reduce the problem to an evaluation of a collectionâ¦ Can someone have the same issue under Windows or Mac? To reproduce : Copy paste the contents of the attached file in the playground and print it or do it It works on pre-spur vm. BTW, there is not crash.dmp, does it works with spur? Vincent De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de Marcus Denker EnvoyÃ© : vendredi 5 fÃ©vrier 2016 13:01 Ã : Pharo Development List Objet : Re: [Pharo-dev] Epicea tests failure under Windows (WAS: RE: [ANN] We are in "code freeze" for Pharo 5) On 05 Feb 2016, at 12:40, Marcus Denker <marcus.denker(a)inria.fr<mailto:marcus.denker@inria.fr>> wrote: I will try do integrate it nowâ¦ No, it still fails. https://ci.inria.fr/pharo/job/Pharo-5.0-Update-Step-2.1-Validation-M-Z/labe… The last test it executed seems to be this: running suite: Refactoring-Tests-Environment starting testcase: RBBrowserEnvironmentTest>>testAndEnvironment ... Very strange... Marcus ________________________________ Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

6 10

problem with slots on proxies
by Tudor Girba May 15, 2016

May 15, 2016

Hi, I am trying to play with some proxies that inherit from ProtoObject have slots. For example, I try to do this, but I get an error: ProtoObject subclass: #BBB instanceVariableNames: 'variable' classVariableNames: '' package: 'BBB'. BBB class allSlots first read: BBB new The problem is that the slot sends messages to its parent object, such as: IndexedSlot>>read: anObject ^ anObject instVarAt: index This is a problem because a similar scenario happens also when you open a debugger on a proxy that tries to communicate with a remote image. I think that instead of sending messages to the receiver, we should make the slot work with the mirror primitives. For example, we would rewrite the read: method like: IndexedSlot>>read: anObject ^ thisContext object: anObject instVarAt: index Do you agree? Can I open an issue for this? I think this is important. Cheers, Doru -- www.tudorgirba.com www.feenk.com "If you can't say why something is relevant, it probably isn't."

3 3

Some GT tool for this?
by Mariano Martinez Peck April 21, 2016

April 21, 2016

How many times have you tried to search a string as a comment of a commit in all the history? Myself: many many times. I know we need much better tools for that, store the history in a another way, provide a nicer API, etc etc. And I know there were topics about that. However, I would deeply appreciate a very short term solution for ease that. The model side is as simple as this: | packageName ancestry anscestors substring | packageName := 'MyPackageXX'. substring := 'whatever I want to search'. ancestry := (MCWorkingCopy allManagers detect: [:each | each packageName = packageName] ) ancestry. anscestors := ancestry withBreadthFirstAncestors select: [:each | each isKindOf: MCVersionInfo]. anscestors select: [ :each | each message includesSubstring: substring ] Do you think it's worth a simple UI tool? Custom inspector of MCAncestry? Cheers, -- Mariano http://marianopeck.wordpress.com

4 8

[Ann] New version of Ghost
by Denis Kudriashov April 4, 2016

April 4, 2016

Hello. I finished new version of Ghost: - DNU approach for basic proxies instead of #cannotInterpret: trick (trick used only for class proxies) - Abstract proxy classes uses Ghost name instead of Proxy: there are GHObjectGhost and GHClassGhost. - GHProxyHandler renamed to GHGhostBehaviour. Concrete ghosts should implement #ghostBehaviour instead of #proxyHandler. - GHGhostBehaviour should define #currentMetaLevel to specify set of messages which should not be intercepted. Such meta messages will be executed under ghost instance by subclass of GHMetaMessages. In previous version there was dictionary which maps meta message selector to implementation selector. It was not suitable. Now meta messages should be directly implemented on particular GHMetaMessages subclass and all it methods are considered meta. So GhostBehaviour should return instance of GHMetaLevel with meta messages implementation class: - GHMetaLevel with: GHEmptyMetaMessages "when all possible messages should intercepted" - GHMetaLevel with: GHStandartMetaMessages "when tools specific messages should not be intercepted" For example standard meta messages implements #inspect: GHStandartMetaMessages>>inspect "Create and schedule an Inspector in which the user can examine the receiver's variables." ^ Smalltalk tools inspector inspect: *ghost* - Traits for methods explicitly defined on ghosts: TMinimalProxy, TNotNilProxy, TIdentifiedProxy (with #=, #hash, #class). Concrete proxies can add this traits to itself independently from meta level. For example traits supply convenient methods to retrieve ghost information in polymorphic way with objects: - ghost isGhost - ghost ghostClass "returns actual class of receiver" - ghost ghostPrintString "returns string which represents ghost from meta level point of view" This traits are suitable and they provide some kind of optimisation for proxies (methods from traits are executed directly instead of complex meta messages mechanizm). But maybe they are superfluous. For example they can't be reused for class proxies which substitute real object classes (to intercept all instance messages). - GHClassGhost able to replace class of real objects. It implements cannotInterpret: trick to intercept all instance messages. Subclasses should define two behaviours: #ghostBehaviour (as any other ghost) and #instancesBehaviour which will process instance messages. In previous version it was different message to same #ghostBehaviour. - New kind of proxies: - GHObjectVirus. It is special kind of GHClassProxy. It infects real object to intercept it messages. From meta level infected object looks like healthy object which means that meta messages are executed by infected object itself. As class virus looks like real victim class. So in case when virus is created with standard meta level tools will not differ him from health object. There are special messages which allow ask object about viruses: - infectedObject isInfectedByVirus - infectedObject virus - infectedObject recoverFromVirus - GHLearningObject. It is suitable proxy which retrieves all unknown methods from teacher class. Thank's Stephan for this idea. This kind of proxy allows me easily find required set of messages to support inspectors and debuggers. You can create instance of learning object by: GHLearningObject withTeacher: Object. And any operation with it will fill studiedMessages dictionary. In my case I opened GTInspector on it and got all messages which was needed for him. - Ghosts works correctly with latest Pharo 5 tools (basic inspector, GTInspector, SpecDebugger, GTDebugger). Required methods for tools are extracted to 'Ghost-GTSupport' package. - Repackaging: - Ghost-ObjectProxies. It contains all core classes and abstract GHObjectGhost which is based on DNU - Ghost-ClassProxies. It contains code for proxy which can substitute class of real object. GHClassGhost implements cannotInterpret: trick to intercept all instance messages. And it implement support for debugging such methods. - Ghost-LearningObject - Ghost-ObjectVirus - Ghost-GTSupport - test packages - All code moved to Pharo repository http://smalltalkhub.com/#!/~Pharo/Ghost (in includes packages from CAR repo too) You can load new version by: Gofer it smalltalkhubUser: 'Pharo' project: 'Ghost'; configurationOf: 'Ghost'; loadStable I use it now in Seamless and Mocketry.

6 25