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

[pharo-project/pharo-core]
by GitHub Jan. 30, 2017

Jan. 30, 2017

Branch: refs/tags/60363 Home: https://github.com/pharo-project/pharo-core

1 0

Esteban's ChangeLog week of 23 January 2017
by estebanlm＠gmail.com Jan. 30, 2017

Jan. 30, 2017

Hello! This is my weekly ChangeLog, from 23 January 2017 to 29 January 2017. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=23/1/2017&to=29/1/2017 ChangeLog ========= 27 January 2017: ---------------- * I worked a bit with [iceberg](https://github.com/npasserini/iceberg). Finally merged the branch +multi-remotes+ onto +0.4-dev+ just to realise immediately there is a [bug](https://github.com/npasserini/iceberg/issues/264) :( Anyway... this is at least partially solved so I will integrate it directly. * Fixed [case: 19592](https://pharo.fogbugz.com/f/cases/19592) (PharoVM shown as Squeak Cog VM on Windows task Manager). * I worked with Clement to figure out why +supportsWriteBarrier+ was answering +false+ in windows builds. Turns out it was a combined bug: First, a problem in the VM and double castings (weird, isn't?). This is already taken care by Clement. Second (and this is 'my' side of the problem), PharoVM builds needed to include a couple of flags I was not inclding: ---- MULTIPLEBYTECODESETS=true bytecodeTableInitializer=initializeBytecodeTableForSqueakV3PlusClosuresSistaV1Hybrid ---- with this two things fixed, now everything should be fine in Windows side. Curiously, even if the method was answering false, the 'write barrier' was actually working :) 26 January 2017: ---------------- * Spent some time verifying some issues with VM on Windows. * Why +SqueakSSL+ is not working? [case: 19605](https://pharo.fogbugz.com/f/cases/19605). This looks to be an invalid issue, since I cannot prove it (nor Torsten). * Why +Smalltalk vm supportsWriteBarrier+ answers +false+ ? This is weird, since my own builds (which are the same) answers correctly +true+ . Anyway, I will try triggering a new build, and hope for the best. * I submited a fix for [case: 19315](https://pharo.fogbugz.com/f/cases/19315). The patch contains both my workaround plus the fix suggested by Phil (in a slightly different way)... yeah, I know this is redundant but I want to be sure this damn bug is fixed for good :) 23 January 2017: ---------------- * I made a small iteration on the new mail service over this thingy... now I export the log in my own variation of the [AsciiDoc](http://asciidoctor.org/docs/what-is-asciidoc/#who-s-using-asciido… format. I choose to do it like this because format is more legible (and +Pillar+ already has one exporter to it :P) * I added +AioPlugin+ to all linux distros (they will be available in latest VM). As with SqueakSSL, I have no idea why it was missing :P cheers! Esteban

1 0

Regression in Nautilus in 60362
by stepharong Jan. 29, 2017

Jan. 29, 2017

Hi Pharo 6.0 Latest update: #60362 I get several DNU - when selecting a protocol from the list - when pressing the execute icon of an example instance https://pharo.fogbugz.com/f/cases/19622/runExamplarMethod-DNU I do not know what's happened. May be a wrong fix. -- Using Opera's mail client: http://www.opera.com/mail/

2 1

Nautilus Bug? Pressing "green play button" leads to an exception
by Volkert Jan. 29, 2017

Jan. 29, 2017

Looks like something is broken in the latest pharo build ... Starting an "example" (f.e. from AthensDemoMorph) with the "green play button" leads to an exception. Pharo 6.0 Latest update: #60362 BW, Volkert

2 2

About printing without having ""
by stepharong Jan. 29, 2017

Jan. 29, 2017

Hi this is nearly more than a year that I ask if we can have a way to NOT have "" when we print a result in the tool. What is the status? This %#$&^$&*(&)**&^$%#$&%*^&( popup BREAKS the flow when writing tests. I'm FED UP to have to remove the " at the beginning and end of my expression result. We got an long discussion and now how it is handled? I have the impression that the strategy here is to make sure that people believe that they are heard but do not care. Stef -- Using Opera's mail client: http://www.opera.com/mail/

8 12

AlreadyInPharo5
by Ben Coman Jan. 29, 2017

Jan. 29, 2017

Hi Pavel, Just curious about the AlreadyInPharo5 tag being added to Issues you are sorting. For issue 14800 "AthensCanvas clipRect oddity" for example I would guess its not in Pharo 5. https://pharo.fogbugz.com/f/cases/14800 cheers -ben

3 5

pharo by example 50
by Ben Coman Jan. 28, 2017

Jan. 28, 2017

Some feedback on the download page... http://files.pharo.org/books/updated-pharo-by-example/ The four uses of use of "50" there feels out of place, since I can't help reading it as "fifty" rather than the (I presume) intended "five-zero". Perhaps insert a dot, or drop the zero. cheers -ben

2 1

Slice dependent package log message
by Ben Coman Jan. 28, 2017

Jan. 28, 2017

This is a simple by slightly invasive idea I'd like to run past the community. Sometimes when I look at packages in Pharo/main and PharoInbox/main repositories, I wonder which Issues particular package versions belongs to. So I'd like to add an automatic reference to their log message back to the Slice. I think the following could be a nice way to do it... MCWorkingCopy>>newVersionWithName: nameString message: messageString in: aRepository | info deps depsMsgString | info := ancestry infoWithName: nameString message: messageString. ancestry := MCWorkingAncestry new addAncestor: info. self modified: true; modified: false. "*" depsMsgString := messageString, String cr, String cr, 'Required by ', nameString. "*" deps := self collectDependenciesWithMessage: depsMsgString in: aRepository. (self repositoryGroup includes: aRepository) ifFalse: [ self repositoryGroup addRepository: aRepository ]. ^ MCVersion package: package info: info snapshot: package snapshot dependencies: deps Your thoughts? Changed lines marked "*". cheers -ben

1 0

MetacelloLoaderPolicy
by Ben Coman Jan. 28, 2017

Jan. 28, 2017

Hi Dale, Just tracing through a Metacello load and I see MetacelloLoaderPolicy. This has no comment and its superclass is Object so its not clear what other loader policies there might be. Is there just that one? cheers -ben

1 0

MetacelloBaseConfiguration deprecation
by Ben Coman Jan. 28, 2017

Jan. 28, 2017

In ConfigurationOfDependencyAnalyser class >> DevelopmentSupport I read... "See the methods in the 'development support' category on the class-side of MetacelloBaseConfiguration. Decide what development support methods you would like to use and copy them the the class-side of your configuration." <apiDocumentation> but MetacelloBaseConfiguration is empty and in package Metacello-Core-Deprecated. So what is the replacement? cheers -ben

1 0