- Pharo-dev - lists.pharo.org

GSoC Week 3 update - Enhancing Pharo Command Line
by Rajula Vineet June 5, 2017

June 5, 2017

Hi all, It has been about three weeks, I started working on my GSoC project. The first task I am working on is the new implementation for Current Working Directory. I have written the new implementation. Currently, I am testing the new code. Will soon share the work here. Meanwhile, for the week three, I have written a blog post <https://vineetreddy.wordpress.com/2017/05/29/cross-platform-with-pharo/> on OSPlatfrom. Please do take a look and give your feedback. Thanks, Rajula -- View this message in context: http://forum.world.st/GSoC-Week-3-update-Enhancing-Pharo-Command-Line-tp494… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

2 1

Esteban's ChangeLog week of 29 May 2017
by estebanlm＠gmail.com June 5, 2017

June 5, 2017

Hello! This is my weekly ChangeLog, from 29 May 2017 to 4 June 2017. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=29/5/2017&to=4/6/2017 ChangeLog ========= 1 June 2017: ------------ * ... and now I fixed the problem with real files/symlinks in distribution, it will be fixed in next build. Turns out it was a problem with the cache of travis for opensmalltalk-vm :) * Problem in Athens 64bits was with font treatment: Someone was using an +uint+ instead a +void *+ to pass a pointer. Of course, this was working fine on 32bits (because sizeof is the same) but is completely wrong on 64bits. Anyway, I found it and fixed it on [case: 20099](https://pharo.fogbugz.com/f/cases/20099) * Yesterday after we ask for final testing we spotted two new blocking issues for release: * Athens was not working on 64bits * Distribution packaging were duplicating files insted copying symlink So, I deferred the release (once again) to next tuesday. 31 May 2017: ------------ * I promoted new stables for [PharoVM](http://files.pharo.org/get-files/60) . This should fix the black-screen problem on mac and the problem of fast-typing also on mac (but latest still needs some test) 30 May 2017: ------------ * I checked a couple of issues on [iceberg](https://github.com/pharo-vcs/iceberg). Still warming up but I got to solve at least [one issue](https://github.com/pharo-vcs/iceberg/issues/361), around correctly dealing with bad user.name and user.mail properties :) * I updated the scripts for creating platform distributions to build also 64bits versions, now you have also a distribution for 64bits on [mac](http://files.pharo.org/platform/Pharo6.0-64-mac.zip) and on [linux](http://files.pharo.org/platform/Pharo6.0-64-linux.zip). * Back from holidays, I just restored the CI building for Pharo to green :P Now, to do that release! cheers! Esteban

1 0

Abstract test classes are not managed well in SUnit
by Cyril Ferlicot D. June 5, 2017

June 5, 2017

Hi, Today I found a bug in SUnit. Sometimes when you have an abstract test class and you override it the tests will be inherit or not. If a subclass has other tests, the tests will not be inherited. If the subclass has no other tests, the tests will be inherited. Here is a little script showing the problem: TestCase subclass: #A slots: { } classVariables: { } category: 'TestProblem'. #A asClass subclass: #B slots: { } classVariables: { } category: 'TestProblem'. #B asClass subclass: #C slots: { } classVariables: { } category: 'TestProblem'. #A asClass class compile: 'isAbstract ^ self = A'. #A asClass compile: 'actualClass ^ self subclassResponsibility'. #A asClass compile: 'testTest self actualClass new'. #C asClass buildSuiteFromAllSelectors run. "1 run, 0 passes, 0 skipped, 0 expected failures, 0 failures, 1 errors, 0 unexpected passes" #C asClass compile: 'testAnotherTest self assert: true'. #C asClass buildSuiteFromAllSelectors run. "1 run, 1 passes, 0 skipped, 0 expected failures, 0 failures, 0 errors, 0 unexpected passes" In the last line I would expect 2 run cases. 1 pass and 1 error. I think this is important to correct because it weaken the strength of the tests. https://pharo.fogbugz.com/f/cases/20118/SUnit-does-not-manage-well-abstract… -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

7 12

Do we have better collections design library?
by Denis Kudriashov June 4, 2017

June 4, 2017

Hi. I just found that there is no WeakIdentityValueDictionary. But we have WeakValueDictionary, WeakKeyDictionary, WeakIdentityKeyDictionary. And to implement missing class I need to copy overrides from IdentityDictionary. And weak key dictionaries are implemented same way by duplicating code. And generally identity collections are not much different from equal collections but they still duplicate a lot of code with little difference: #hash or #identityHash, #= or #==. So I am wondering do we have alternative implementation with proper design? There are wishes to replace streams by XSteams. What about collections? Best regards, Denis

4 7

FFI does not work on Linux 64-bit
by Oleksandr Zaytsev June 4, 2017

June 4, 2017

Hello, Yesterday during the Pharo Sprint I was experiencing many problems with my 64-bit Pharo Image and Pharo Sprint App. For example, whenever I clicked "Open in FogBugz", "Discuss on Discord", or "Help" in a Sprint App, I got Error: Could not find accessor for variable named "command" As suggested on Discord, I tried this WebBrowser openOn: 'http://pharo.org' and received the same error Then, after I executed xdg-open 'http://pharo.org' in my Linux terminal, and it worked without an error, *Juraj Kubelka* assumed that *ffi does not work on Linux 64-bit* and told me that I should report this issue to *Torsten Bergmann*. Also, no method comments or class comments were visible in my image. And when I tried to write and save a comment, it just disappeared. These two problems may be related. OS: Ubuntu 16.04 LTS VM: 201705310241 (http://files.pharo.org/vm/pharo-spur64/) Image: Pharo64-60498 (http://files.pharo.org/image/60/latest-64.zip) Oleks

2 1

Pharo 6 "Changes"
by Sean P. DeNigris June 3, 2017

June 3, 2017

I randomly selected two packages (Athens-Morphic and Morphic-Core) and clicked the "Changes" button in the MC Browser against their canonical repos. The package went from being marked clean, to showing many changes. What do you make of that? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Pharo-6-Changes-tp4949165.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

2 2

Calypso feedback
by Stephane Ducasse June 3, 2017

June 3, 2017

Hi denis Now I decided to use Calypso all the time :) I do not know if this is the latest version but I loaded it today from the catalog browser. - When I do sender/implementors of and I get multiple pane in the message browser and I want to close one pane using command-W I close the editor but not the pane Stef [image: Inline image 1]

3 5

State of Pharo 6 64-bit ?
by Sven Van Caekenberghe June 2, 2017

June 2, 2017

Hi, I am wondering a bit about the state of Pharo 6 64-bit. On one hand the current RC seems to work really well on macOS (for me), it is stable and clean. Is the goal to ship this variant as a real finished version ? If so, I think must make it pass as much unit tests as possible. I filed a couple of issues related to that: https://pharo.fogbugz.com/f/cases/20102/SmallInteger-digitAt-not-ready-for-… https://pharo.fogbugz.com/f/cases/20108/CompiledMethod-isAbstract-fails-on-… https://pharo.fogbugz.com/f/cases/20111/Some-Collection-tests-fail-on-64-bi… https://pharo.fogbugz.com/f/cases/20110/AllocationTest-testOutOfMemorySigna… The first one has a fix. Fixes must be done carefully, since the same image must be able to run on both 32 and 64 bit. I also noticed that a couple of Compiler tests are failing. Now, obviously the compiler works good enough since it can load code, so this is probably also something minor/weird/unexpected. About 51 tests fail (in MethodMapTests, OCBytecodeHGeneratorTest and OCNewCompilerWithChangesFunctionalTests). Should I create an issue ? Sven

3 3

DebugSession: no exception raised when stepping out of the execution?
by tdupriez＠ens-paris-saclay.fr June 2, 2017

June 2, 2017

Hi, I'm working with DebugSession to see if I can implement something that would step into an execution until a given expression evaluates to a different value than the value it had at the beginning to quickly localise the precise point where an invariant is broken. But it appears that if the expression always evaluate to the same value, then the VM freezes. I simplified my program to just stepInto a debugSession indefinitely, and it makes the VM freeze, while I would rather expect an exception to be raised (something like "ReachedEndOfExecution"). Here is my example code. Beware, running it will freeze the VM. | program process context debugSession | program := [1+2]. process := program newProcess. context := process suspendedContext. debugSession := process newDebugSessionNamed: 'StepIntoForever' startedAt: context. [ true ] whileTrue: [ debugSession stepInto ]. Is there a way to have an exception be raised when a stepInto message is sent to a debugSession whose execution is finished, instead of just freezing the VM? Thomas

5 6

Minor glitch in source code diff tool
by Sven Van Caekenberghe June 2, 2017

June 2, 2017

It seems there is a minor glitch in the source code diff tool: The first difference is marked (coloured) OK, each next one is one character position more off. This is in the latest 6.0 RC image. Should I create an issue ? Sven

2 2