- Pharo-dev - lists.pharo.org

Little challenge
by ducasse Jan. 10, 2020

Jan. 10, 2020

Hi I would like know how many instances of Color are instantiated by a theme. I would like to know how many times the same color is created. Iâm creating a theme using a dictionary instead of stupidly returning color. May be like that I can use an LRUCache to see the number of hits. I will see if I can instrument Color new. We really need tools that help us measuring things. Any other ideas? S.

6 10

[Pharo 8.0] Build #1102: 2854-Pharo-7-Saving-the-settings-breaks-local-directory
by ci-pharo-ci-jenkins2＠inria.fr Jan. 10, 2020

Jan. 10, 2020

There is a new Pharo build available! The status of the build #1102 was: SUCCESS. The Pull Request #5431 was integrated: "2854-Pharo-7-Saving-the-settings-breaks-local-directory" Pull request url: https://github.com/pharo-project/pharo/pull/5431 Issue Url: https://github.com/pharo-project/pharo/issues/2854 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

BaselineOfZincHTTPComponents>>baseline:
by Alistair Grant Jan. 10, 2020

Jan. 10, 2020

Hi Sven, Following on from a discussion I started in Discord development... Loading Zinc SSO in Pharo 8 currently causes problems because the Zinc packages in core Pharo 8 are out of sync with your repository (specifically https://github.com/pharo-project/pharo/commit/45b7de2b6c901112be04230faba48… caused problems for me). I was able to resolve the issue by modifying BaselineOfZincHTTPComponents>>baseline: to remove all references to the packages that are now part of core Pharo 8: BaselineOfZincHTTPComponents>>baseline: spec <baseline> spec for: #common do: [ spec baseline: 'NeoJSON' with: [ spec repository: 'github://svenvc/NeoJSON:v17/repository' ]. spec baseline: 'XMLParser' with: [ spec repository: 'github://feenkcom/XMLParser:v0.6.1/src' ]. spec baseline: 'XMLWriter' with: [ spec repository: 'github://feenkcom/XMLWriter:v0.6.0/src' ]. "spec project: 'XML Support' with: [ spec className: 'ConfigurationOfXMLSupport'; repository: 'http://www.squeaksource.com/MetacelloRepository' ]." spec package: 'Zinc-AWS'; package: 'Zinc-REST' with: [ spec requires: #('NeoJSON') ]; package: 'Zinc-WebSocket-Core'; package: 'Zinc-WebSocket-Tests' with: [ spec requires: 'Zinc-WebSocket-Core' ]; package: 'Zinc-SSO-OAuth1-Core' with: [ spec requires: #('NeoJSON') ]; package: 'Zinc-SSO-OAuth2-Core' with: [ spec requires: #('NeoJSON') ]; package: 'Zinc-SSO-OpenID-Core'; package: 'Zinc-SSO-Demo' with: [ spec requires: #('Zinc-SSO-OAuth1-Core' 'Zinc-SSO-OAuth2-Core' 'Zinc-SSO-OpenID-Core') ]; package: 'Zinc-SSO-OAuth1-Tests' with: [ spec requires: #('Zinc-SSO-OAuth1-Core') ]; package: 'Zinc-SSO-OpenID-Tests' with: [ spec requires: #('Zinc-SSO-OpenID-Core') ]; package: 'Zinc-WebDAV'; package: 'Zinc-WWS-Server'; package: 'Zinc-WWS-Client'. spec group: 'AWS' with: #('Zinc-AWS'); group: 'WebDAV' with: #('Zinc-WebDAV'); group: 'WebSocket' with: #('Zinc-WebSocket-Core' 'Zinc-WebSocket-Tests'); group: 'SSO-OAuth1' with: #('Zinc-SSO-OAuth1-Core' 'Zinc-SSO-OAuth1-Tests'); group: 'SSO-OAuth2' with: #('Zinc-SSO-OAuth2-Core'); group: 'SSO-OpenID' with: #('Zinc-SSO-OpenID-Core' 'Zinc-SSO-OpenID-Tests'); group: 'SSO-Demo' with: #('Zinc-SSO-OAuth1-Core' 'Zinc-SSO-OAuth2-Core' 'Zinc-SSO-OpenID-Core'); group: 'SSO' with: #('SSO-OAuth1' 'SSO-OAuth2' 'SSO-OpenID' 'SSO-Demo' 'Zinc-SSO-Demo'); group: 'WWS' with: #('Zinc-WWS-Server' 'Zinc-WWS-Client'); group: 'REST' with: #('Zinc-REST') ] This isn't directly usable by you since it replaces 'XML Support' with XMLParser and XMLWriter and it would break Pharo 7. But if we modified it to put in checks for Pharo 7 vs Pharo 8 it would somewhat future proof the code against changes made in core Pharo 8. What do you think? Thanks, Alistair

3 7

[ANN] Sysmel, another experimental low-level language implemented in Pharo
by Ronie Salgado Jan. 10, 2020

Jan. 10, 2020

Hi All, I am finally announcing an initial release of my new experimental low-level programming language which I am calling Sysmel (For SYStem MEtaprogramming Language). GitHub Page: https://github.com/ronsaldo/sysmel Short native game demo: https://www.youtube.com/watch?v=tRoPMbPvqH0 Sysmel is designed to be a flexible language, and a flexible compiler front-end. The support for garbage collection in Sysmel is an optional feature by design, and the support for dynamic objects and dynamic message lookup it is also optional. If garbage collection is disabled, the code written in Sysmel is mostly equivalent to C/C++ code (only single inheritance is supported for now), but with a hybrid syntax between Smalltalk and C++. For the final code generation I am using my custom SSA intermediate representation (the same one that I used in Lowtalk, and in) which it is currently tested with the following two backends: - LLVM textual IR backend. This is used for generating native object files by reusing the LLVM infrastructure. This backend also supports emitting DWARF debugging information so the resulting programs can be debugged with gdb. - Spir-V backend, for generating shaders for Vulkan and executing them in the GPU. One of the objectives of Sysmel is to support the full Smalltalk object model without a VM and with real multi-threading support. So far message lookup is already implemented, but there is still many basic primitives missing, and the implementation of a proper GC that allows implementing #allInstances and #become: . As a quick workaround, currently only the Boehm conservative GC is supported for having an initially working environment. In the near future, Woden Engine will adopt Sysmel at least as its shading language for programming the GPU. In a farther future, a higher performance version of the Woden Engine will be made by using Sysmel, mostly because it seems to be much easier to support real multi-threading in Sysmel by making a completely new system. I am also re-implementing my previous experiment for converting Pharo block closures into shaders by reusing the Sysmel intermediate level AST, and its type inference machinery. The current version of this new Block -> to Shader infrastructure can only perform basic Map and Reduce operations with blocks that do not define local variables (they will be supported in a future version) in linear arrays. Best regards, Ronie

4 4

[Mm10s] 2020-01-06
by tesonep＠gmail.com Jan. 9, 2020

Jan. 9, 2020

Hello, last week was a short one but some things have been done: - [VM] Porting the GC fix to Pharo 7 / 8 VM - [VM] Building for the different Platforms - [VM] Signing for OSX - [VM] The versions will be available today to start testing it before promoting them to stable. - [Pharo8] Fixing Issues before the release - [VM Dev] Starting to work in improving tests in JIT and GC. -- Pablo Tesone. tesonep(a)gmail.com

6 8

Stand fosdem 2020
by Santiago Bragagnolo Jan. 9, 2020

Jan. 9, 2020

Hi all, we got a stand position for the Sunday 2 February in fosdem. This week I am going to be organising all the goodies slides etc . I would like as well to know if any of the companies working with photo is interested in being shown , and if you have goodies or any mean of helping to share do not hesitate in contacting me. I'll try to get some good photos from the place for sharing later :) Santiago

2 2

[Pharo 9.0] Build #3: 5450-Add-executable-comments-in-SequenceableCollection---sorting-shuffling-split-protocol
by ci-pharo-ci-jenkins2＠inria.fr Jan. 9, 2020

Jan. 9, 2020

There is a new Pharo build available! The status of the build #3 was: FAILURE. The Pull Request #5461 was integrated: "5450-Add-executable-comments-in-SequenceableCollection---sorting-shuffling-split-protocol" Pull request url: https://github.com/pharo-project/pharo/pull/5461 Issue Url: https://github.com/pharo-project/pharo/issues/5450 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Smalltalk job offers at Barcelona
by ducasse Jan. 8, 2020

Jan. 8, 2020

Hello Pharoers Please distribute aroundâ¦. Lifeware is looking for smart people and Smalltalkers for positions at Barcelona. If you are interested please contact Massimo Arnoldi <massimo.arnoldi(a)lifeware.ch> S.

1 0

[Pharo 9.0] Build #2: 5441--typo-in-HashedCollection--comment
by ci-pharo-ci-jenkins2＠inria.fr Jan. 7, 2020

Jan. 7, 2020

There is a new Pharo build available! The status of the build #2 was: SUCCESS. The Pull Request #5442 was integrated: "5441--typo-in-HashedCollection--comment" Pull request url: https://github.com/pharo-project/pharo/pull/5442 Issue Url: https://github.com/pharo-project/pharo/issues/5441 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

pharo compiler on scientific notation
by Nicolas Anquetil Jan. 6, 2020

Jan. 6, 2020

In pharo 7, inspecting: 1.0e3333 gives: "Reading a number failed -> " it works for: 1.0e333 (only three "3") is that the expected behaviour ? nicolas -- Nicolas Anquetil RMod team -- Inria Lille

3 6