- Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #664: 21510-The-traits-definition-ignores-the-slots-for-stateful-traits
by ci-pharo-ci-jenkins2＠inria.fr March 7, 2018

March 7, 2018

There is a new Pharo build available! The status of the build #664 was: SUCCESS. The Pull Request #1038 was integrated: "21510-The-traits-definition-ignores-the-slots-for-stateful-traits" Pull request url: https://github.com/pharo-project/pharo/pull/1038 Issue Url: https://pharo.fogbugz.com/f/cases/21510 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

PharoDays?
by Stephane Ducasse March 7, 2018

March 7, 2018

Hi guys many people are asking when and where there will be PharoDays. And we do not know. We are looking for local organisers and else we do it at Lille. Now what would be a good date? What about 7-8 June? Stef

3 4

Esteban's ChangeLog week of 26 February 2018
by estebanlm＠gmail.com March 7, 2018

March 7, 2018

Hello! This is my weekly ChangeLog, from 26 February 2018 to 4 March 2018. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=26/2/2018&to=4/3/2018 ChangeLog ========= 2 March 2018: ------------- * I've been working on Iceberg UI. I have first versions of: * repositories browser * individual repository browser * individual repository management browser * commit window * push window * pull windows I'm not woking on fix a couple of problems on refreshing windows and defining how the pull will work (by default, it will trigger a merge of the changes your are pulling into your image). 1 March 2018: ------------- * I made a new backport for 6.1, [case: 21344](https://pharo.fogbugz.com/f/cases/21344) enjoy 28 February 2018: ----------------- * Well... I spent an stupid amount of time to figure out why the latest VM for macOS was not including libgit2. Turns out, there was a "deploy filter" problem (two problems, in fact), that was making that all pharo flavours were being uploaded to the file server and with same name so in fact, one flavour was being copied on top of the other. And "lowcode VM", for example, does not includes libgi2. So, now that's fixed. You can start using latest VM again (which is the one that is signed) ;) cheers! Esteban

3 3

[ANN] 64 bits support preview
by Mariano Martinez Peck March 7, 2018

March 7, 2018

Hi guys, Thanks for Guillermo Polito we now have 64 bits support for OSSubprocess. You can see the required changes in this PR [1]. I made a branch called `support64bits` so that you can help us test it even if CI said it was good [2]. If you do test it and come back to us with the results, please tell us which OS you used. To install from the branch: Metacello new configuration: 'OSSubprocess'; repository: 'github://marianopeck/OSSubprocess:support64bits/repository'; version: #stable; load. Roadmap: Current release is v0.2.5. So I will let that release for Pharo <= 5.0. I will make a new release with the Pharo 64 bits and call it v0.3. That release should be used for Pharo 6.x. Once v0.3 is out, I will make a new release v0.4 with some changes I wanted to do since a loooong time and its a small refactor to minimize OSSubprocess dependency on OSProcesses primitives (at VM side). This is thanks to Holger Freyther and Alistair Grant [3]. As that requires a new VM, then v0.4 should be used in Pharo >= 7.0. Cheers, [1] https://github.com/marianopeck/OSSubprocess/pull/30 [2] https://travis-ci.org/guillep/OSSubprocess/builds/349280174 [3] https://github.com/pharo-project/pharo-vm/pull/142 -- Mariano http://marianopeck.wordpress.com

3 2

[Pharo 7.0-dev] Build #663: 21489 Cleanup TReplacementSequencedTest
by ci-pharo-ci-jenkins2＠inria.fr March 7, 2018

March 7, 2018

There is a new Pharo build available! The status of the build #663 was: SUCCESS. The Pull Request #1022 was integrated: "21489 Cleanup TReplacementSequencedTest" Pull request url: https://github.com/pharo-project/pharo/pull/1022 Issue Url: https://pharo.fogbugz.com/f/cases/21489 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #662: 21489 Cleanup TReplacementSequencedTest
by ci-pharo-ci-jenkins2＠inria.fr March 7, 2018

March 7, 2018

There is a new Pharo build available! The status of the build #662 was: FAILURE. The Pull Request #1022 was integrated: "21489 Cleanup TReplacementSequencedTest" Pull request url: https://github.com/pharo-project/pharo/pull/1022 Issue Url: https://pharo.fogbugz.com/f/cases/21489 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #661: 21327-Integrate-the-new-version-of-Modular-Stateful-Traits
by ci-pharo-ci-jenkins2＠inria.fr March 7, 2018

March 7, 2018

There is a new Pharo build available! The status of the build #661 was: SUCCESS. The Pull Request #871 was integrated: "21327-Integrate-the-new-version-of-Modular-Stateful-Traits" Pull request url: https://github.com/pharo-project/pharo/pull/871 Issue Url: https://pharo.fogbugz.com/f/cases/21327 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #660: 21508-Integrate-Calypso-0103
by ci-pharo-ci-jenkins2＠inria.fr March 6, 2018

March 6, 2018

There is a new Pharo build available! The status of the build #660 was: SUCCESS. The Pull Request #1037 was integrated: "21508-Integrate-Calypso-0103" Pull request url: https://github.com/pharo-project/pharo/pull/1037 Issue Url: https://pharo.fogbugz.com/f/cases/21508 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Ann] Commander shortcuts in Settings Browser
by Denis Kudriashov March 6, 2018

March 6, 2018

Hi. With latest version of Commander and Calypso we will have all shortcuts explorable and configurable in Settings Browser: â Currently it uses command class name and class comment for presentation. We can improve it in future if necessary. In addition you can add single shortcut to your own application settings. For example: MyApp class>>appSettingsOn: aBuilder <systemsettings> ann := ClySpawnFullBrowserCommand classAnnotationAt: #browserShortcutActivation. (ann buildSettingNodeOn: aBuilder) label: 'My app shortcut'; description: 'This command opens browser' Shortcut settings are persisted as all other settings. Only redefined shortcuts are stored into the file. This version also allows to add commands into the world menu and world shortcuts. Just use CmdWorldMenuContext for command annotations: CmdOpenFamilyBookCommand class>>worldMenuActivation <classAnnotation> ^CmdContextMenuCommandActivation byRootGroupItemFor: CmdWorldMenuContext CmdOpenFamilyBookCommand class>>globalShortcutActivation <classAnnotation> ^CmdShortcutCommandActivation by: $o meta, $f meta for: CmdWorldMenuContext (CmdOpenFamilyBookCommand is a command from Commander-Examples package). Nice detail: all shortcuts are updated immediately when you modify annotations either from settings or programmatically from browser. Now pull request for Pharo 7 <https://github.com/pharo-project/pharo/pull/1037> is waiting integration. Soon it will be inside. Best regards, Denis

3 2

FFI Struct Argument Pass By Value Fails on Mac 64 bit
by Todd Blanchard March 6, 2018

March 6, 2018

I've been trying to track this down for a couple weeks now. I have concluded that structs passed by value to functions on the 64 bit VM are not properly populated. The struct's memory is all zero'd. I found this while trying to work with LibClang and found that functions that fetched code locations from code ranges always returned invalid zero'd locations. After spending some time with lldb I have traced the problem into the native code and found that the argument is not correct. I've carved out the wee bit of clang to reproduce this in a tiny library. The gist of it is below and the entire file is included. Basically the struct passed to the function clang_getRangeStart is zero'd memory regardless of the data I send from the image side. The build command I used on sierra is clang -shared -undefined dynamic_lookup -o microclang.dylib microclang.c I'm stuck. The FFI64 plugin is way beyond my comprehension. // microclang.c typedef struct { const void *ptr_data[2]; unsigned int_data; } CXSourceLocation; /** * \brief Identifies a half-open character range in the source code. * * Use clang_getRangeStart() and clang_getRangeEnd() to retrieve the * starting and end locations from a source range, respectively. */ typedef struct { const void *ptr_data[2]; unsigned begin_int_data; unsigned end_int_data; } CXSourceRange; const char* first = "first_pointer"; const char* second = "second_pointer"; // return a fake range with non zero data CXSourceRange clang_getArbitraryRange() { CXSourceRange range = {0}; range.ptr_data[0] = (void*)first; range.ptr_data[1] = (void*)second; range.begin_int_data = 17; range.end_int_data = 24; return range; } // Actual clang function - range is always zero'd here despite having values in the image CXSourceLocation clang_getRangeStart(CXSourceRange range) { // Special decoding for CXSourceLocations for CXLoadedDiagnostics. if ((uintptr_t)range.ptr_data[0] & 0x1) { CXSourceLocation Result = { { range.ptr_data[0], nullptr }, 0 }; return Result; } CXSourceLocation Result = { { range.ptr_data[0], range.ptr_data[1] }, range.begin_int_data }; return Result; }

4 13