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

I want to move the latest vm to stable... I need feedback !
by Esteban Lorenzano Jan. 24, 2017

Jan. 24, 2017

Hi guys, I want to move latest vm to stable (for Pharo 6.0, of course). And I have the idea there are still some blocking issuesâ¦ can you I have this issues in mind: No write right on Windows with the new VM <https://pharo.fogbugz.com/f/cases/19525/No-write-right-on-Windows-with-the-…> Freetype2 primitive failed [error 2][unknown file format] <https://pharo.fogbugz.com/f/cases/19315/Freetype2-primitive-failed-error-2-…> -> for this Iâm testing the solution pointed here: http://log.smallworks.eu/web/post/289 <http://log.smallworks.eu/web/post/289>, plus a fix Phil sent me. Image freezes on Linux if it was previously saved on Windows <https://pharo.fogbugz.com/f/cases/19272/Image-freezes-on-Linux-if-it-was-pr…> â¦ but also anything else that I might be missing. cheers, Esteban

7 15

Help: Implementing core classes for Redline Smalltalk ...
by James Ladd Jan. 24, 2017

Jan. 24, 2017

Hi Pharo People, Redline Smalltalk is a Smalltalk for the Java Virtual Machine. The compiler is 90% complete. Would anyone like to help implement the core runtime classes? No Java involved. If you would like to lend a hand please email object at redline.st - James. -- View this message in context: http://forum.world.st/Help-Implementing-core-classes-for-Redline-Smalltalk-… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

2 2

Collections and Kernel
by ClÃ©ment Bera Jan. 24, 2017

Jan. 24, 2017

Hi everyone, As I am working on an optimising JIT compiler for the Cog VM written in Smalltalk and partly running in the Smalltalk runtime, I am very careful about dependencies. I would like to limit the dependencies of the optimiser to the Kernel. The main problem I have is that there are no collections in the Pharo Kernel except MethodDictionary and DependentsArray. The optimiser depends on Array, ByteArray, OrderedCollection, Set and Dictionary which are not part of the Kernel. The second problem is that there are lots of things in the Kernel that the optimiser do not depend on even though everything is in the Kernel package, for example, the optimiser does not depend on anything related to Time/Chronology, on Numbers other than SmallIntegers or Protocol logic. This leads to questions. I know that with the bootstrap incoming, some people have answers to these questions, but I would like to the conversation happening on the mailing list so everyone can contribute. Question 1) Is there any plan to make a 'Kernel-Collection' package, which includes Array, ByteArray, OrderedCollection, Set and Dictionary, but not the rest of the collections ? Question 2) Is there any plan to split the Kernel (or maybe the Kernel and all its dependencies ?) into smaller pieces, for example 'KernelCore', which includes the existing Kernel *but* other Numbers than SmallIntegers, Protocol logic and Time Chronology, which could be moved to 'KernelExtended' or something like that ? I understand that those problems are not easy, but I would like to know if there is a generic plan so I can correctly decide on what dependencies I can have or not. Thanks, cheers,

4 4

Re: [Pharo-dev] AioPlugin not present
by Thierry Goubier Jan. 24, 2017

Jan. 24, 2017

Hi Davide, I do use OSProcess in some cases; last time, I just rewrote that part to emit a notification (and not raise a popup). Regards, Thierry Le 22/01/2017 Ã 15:50, Davide Varvello via Pharo-dev a Ã©crit : > Hi Thierry, > > I need it for the OSProcess. When my code calls OSProcess the warning > (http://imgur.com/a/9jhMy) appears. > > It happens only once. If I close the warning window It does not happen > again, but of course if I restart the image it appears once again, so I have > to find a way to include it or another workaround > > Cheers > Davide

4 9

AST node replacement API
by Yuriy Tymchuk Jan. 23, 2017

Jan. 23, 2017

Hi everyone, does anyone have a better knowledge about replacing nodes in AST? Because what I saw is that there are methods like replaceSourceWith: that can be sent to an AST node with another AST node as a parameter. But this is not enough to get a new source code. Because when you ask the AST for newSource it generates a new source by taking replacements into account, parses the new source, compares it with itself and in case the new parse tree is equal it returns the new source. So itâs not enough to just use replaceSourceWith: but you also have to replace the current node with a new one it AST. Now the question is: am I doing something wrong, or we have strange API because we need to replace both source and node, replacing only one of them does not workâ¦ Uko

4 5

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

Jan. 23, 2017

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

1 0

[pharo-project/pharo-core] 24542a: 60353
by GitHub Jan. 23, 2017

Jan. 23, 2017

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 24542ad3cedacbf19c06fec46ae34d8df5bbac84 https://github.com/pharo-project/pharo-core/commit/24542ad3cedacbf19c06fec4… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-01-23 (Mon, 23 Jan 2017) Changed paths: M BaselineOfIDE.package/BaselineOfIDE.class/instance/actions/additionalInitialization.st M BaselineOfIDE.package/BaselineOfIDE.class/instance/actions/postload_package_.st M BaselineOfIDE.package/BaselineOfIDE.class/instance/baseline/baseline_.st A BaselineOfIDE.package/BaselineOfIDE.class/instance/baseline/groups_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60352.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60353.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60352.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60353.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60353 19574 update BaselineOfIDE https://pharo.fogbugz.com/f/cases/19574 http://files.pharo.org/image/60/60353.zip

1 0

[REMINDER] Pharo TechTalk tomorrow Jan 24 16h UTC
by Esteban Lorenzano Jan. 23, 2017

Jan. 23, 2017

Hello all, This is a reminder for the next TechTalk who will be around Bloc/Brick. Alex, Glenn and/or Doru will be handling thisâ¦ so specific details will come from them, but I suppose it will be more or less like last time: youtube live for presentations, questions/conversation over discord. Links will be sent tomorrow. cheers, Esteban

1 0

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

Jan. 23, 2017

Hello! This is my weekly ChangeLog, from 16 January 2017 to 22 January 2017. You can see it in a better format by going here: http://log.smallworks.eu ChangeLog ========= 20 January 2017: ---------------- * I'm still fixing a couple of final failing tests on iceberg, multi-remotes branch. Problem is that there are still somethings to understand on the "command line backend" (we need to find a better name for this), and the #pushTo: method: if I do it as I think is correct, a couple of failing tests appear... but then, I need to reflect if this is a problem on the functionality or on the tests. 19 January 2017: ---------------- * I think I finally got the problem with FT2Plugin! Yesterday night talking in slack I realised that there was actually duplicated instances of FT2Handle hierarchy with exactly same handle (pointer address). This, of course, causes a double free when those instances are released... and that's the VM crash :) So I quickly sketched a workaround, that you can see here: FT2Handle>>pvtDestroyHandle "This should only be sent from the finalizer. It runs inside a mutex because in strange cases it can happen that this is executed twice, causing a primitiveFailed to be raised." self class destroyMutex critical: [ | handleToRelease | self isValid ifFalse: [ ^self ]. handleToRelease := self handle copy. self primDestroyHandle. "This is super-ugly, but it will prevent duplicated handles to be released" FT2Handle allSubInstancesDo: [ :each | (handleToRelease = each handle) ifTrue: [ each beNull ] ] ] and so far nobody who is testing it crashed! This can be important, but of course... now we need to realise why the duplicated instances are happening. * I spent some time preparing a new way to annoy people :) I prepared a way to send a digest mail about my activity (this stream) to pharo-dev list. I hope it will not be too much. 18 January 2017: ---------------- * ... and still some more work on iceberg, this time making some test pass on the command line backend (who is just a fallback, but well... we still need it around). * Still working on UFFI 64bits. Now I introduced a new hierarchy, FFIArchitecture for now with two children: * FFI_i386 * FFI_x86_64 the purpose is obvious: to allow UFFI to handle differences between different architectures (for example, long has to be parsed to FFIInt32 in i386 and to FFIInt64 in x86_64). 17 January 2017: ---------------- * I'm working on the UFFI support for 64bits. In general, it works fine, but there is a huge problem with structures. What's this problem? Well, let's take this simple structure as example: struct point { unsigned long x; unsigned long y; } Well, thing is in 32bits sizeof(struct point) = 8 while in 64bits sizeof(struct point) = 16, and of course this breaks our current implementation which would be something like this StructPoint>>x ^ handle unsignedLongAt: 1 StructPoint>>y ^ handle unsignedLongAt: 5 and of course, this is not correct for 64bits. My solution is quite simple, instead hardcoding the field offsets, I store those values into class variables that can be calculated each session (but just once). So, this structure would end looking like this: StructPoint>>x ^ handle unsignedLongAt: OFFSET_X StructPoint>>y ^ handle unsignedLongAt: OFFSET_Y this would solve the problem for most of the cases, but there is still the issue that emerges when complete implementation of the struct changes between platforms. I'm planning to implement a strategy pattern to solve this, but not yet (probably I will wait until having a concrete case). This seems to be working, but now I have other problems not related to UFFI: many people has implemented void * parameters of funtions as unsigned long (including me, time ago) which was correct in 32bits but it is not in 64bits. So now I need to review this implementations to see where a fix is needed. But this is not directly a problem of UFFI, I think. * I worked with Nico on fixing libgit2 backend tests for iceberg. Now (more thanks to Nico than me, heh), test for multi-remotes branch are passing for linux but still not for macOS (and forget it about Pharo 5.0). I suspect a problem with VM, I need to review if I can configure smalltalkci to work with latest vm instead stable. 15 January 2017: ---------------- * ... and now I restored the posix permissions to windows platform. Next latest VM will have this change, I hope that will end the problems with FilePlugin, but we'll see. * I just fixed a problem with FilePlugin on macOS: the problem was when determining if a symlink is also a directory: â/tmpâ asFileReference isDirectory was answering false, because it is a symlink and when trying to resolve the symlink to obtain the attributes, there was a cyclic condition that was transforming â/tmpâ into â/private/tmpâ and then back to â/tmpâ, and because of that the test for directory was failing. cheers! Esteban

6 6

[Pharo6] Issue tracker: Issues tagged Pharo6
by Marcus Denker Jan. 23, 2017

Jan. 23, 2017

Hi, To be able to release, we have to check which issues are real show-stoppers. As a first step, we will, this Friday, remove the Pharo6 Milestone tag from *all* issues that are priority âwould be niceâ or lower. https://pharo.fogbugz.com/f/filters/?fGlobal=true&ixFixFor=22&ixPerson=46&i… <https://pharo.fogbugz.com/f/filters/?fGlobal=true&ixFixFor=22&ixPerson=46&i…> These are 281 issues right now. It would be nice if everyone would look at the issues that they have been involved in an adjust priority of needed. Marcus

3 2