August 2018 - Pharo-dev - lists.pharo.org

Is Jenkins OK?

by Alistair Grant

I have a PR that has been running for over 13 hours... https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen… (if there's something I can do about this myself instead of annoying the list, please let me know) Thanks, Alistair

Aug. 14, 2018

Re: [Pharo-dev] Minheadless trial

by Ben Coman

Hi Ronie, Esteban, Could you do a quick review of my CMakeLists.txt change for any obvious blunder. This may be my last post on this thread for a short while. On 8 August 2018 at 21:39, Ben Coman <btc(a)openinworld.com> wrote: > > Well thats enough for one post! > Success running a MSVC compiled Spur Stack "minheadless" VM. > > Next I'll try... option(COG_JIT "Cog JIT" ON) > I did that, and then... "CMakeLists.txt > Cache(x64-Debug only) > Delete cache folder..." "CMake > Build All" then started "x64-Debug" , "pharo.exe minImage+eval" and a console window opens that reports... "linking callsite to invalid address" Well I'm not sure how ready is the Windows 64bit JIT is, so lets try with 32bit JIT. In VS selecting "x86-Debug" , "pharo.exe minImage+eval" and "Cmake > Build All" reports... "Severity Code Description Project File Line Suppression State Error C1189 #error: As yet no Cogit implementation appears to exist for your platform. C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\ IDE\CMakeLists.txt C:\#Repos\OpenSmalltalk\opensmalltalk-vm\spur64src\vm\ cogit.c In the CMake variables SourceFolderName=spur64src because.. VM_64BITS=TRUE which is set here... if(SQUEAK_PLATFORM_X86_64) if(BUILD_I386_VERSION) set(SQUEAK_PLATFORM_X86_32 True) set(SQUEAK_PLATFORM_X86_64 False) else() set(VM_64BITS TRUE) set(SourceFolderName "${SourceFolderName}64") if(WIN32) set(FFI_VARIANT_X64_WIN64 True) else() set(FFI_VARIANT_X64_SYSV True) endif() set(VM_TARGET_CPU "x86_64") endif() else() set(VM_64BITS False) endif() which I'm not clear how that logic works, since it seems BUILD_I386_VERSION doesn't prevent VM_64BITS=True Rearranging like... if(BUILD_I386_VERSION) set(SQUEAK_PLATFORM_X86_32 True) set(SQUEAK_PLATFORM_X86_64 False) set(VM_64BITS False) else() endif() if(SQUEAK_PLATFORM_X86_64) set(VM_64BITS TRUE) set(SourceFolderName "${SourceFolderName}64") if(WIN32) set(FFI_VARIANT_X64_WIN64 True) else() set(FFI_VARIANT_X64_SYSV True) endif() set(VM_TARGET_CPU "x86_64") else() endif() then adding -DBUILD_I386_VERSION in "CmakeSettings.json" like this... "CMakeLists.txt > Change Cmake Settings" { "name": "x86-Debug", "generator": "Ninja", "configurationType": "Debug", "inheritEnvironments": [ "msvc_x86" ], "buildRoot": "${env.USERPROFILE}\\CMakeBuilds\\${workspaceHash}\ \build\\${name}", "installRoot": "${env.USERPROFILE}\\ CMakeBuilds\\${workspaceHash}\\install\\${name}", "cmakeCommandArgs": "-DBUILD_I386_VERSION=ON", "buildCommandArgs": "-v", "ctestCommandArgs": "" }, then refreshing... "CMakeLists.txt > Cache(x64-Debug only) > Delete cache folder..." "CMake > Build All" leaves these values in the Cmake variables... VM_64BITS=False SourceFolderName=spursrc and the build completes successfully. I'm leaving it there for the moment. Actually the above sat in unchanged in draft for a week since I've had to shift my attention to something else. Modifications to date here... https://github.com/bencoman/opensmalltalk-vm/tree/MinimalisticHeadless-x64-… Next would be to catch up to Esteban's branch... https://github.com/estebanlm/opensmalltalk-vm/tree/add-minheadless-vm cheers -ben

Aug. 14, 2018

Mustache bug?

by StÃ©phane Ducasse

Hi In pillar we needed variable lookup with Mustache so we used a https://github.com/Ducasse/Containers-PropertyEnvironment <https://github.com/Ducasse/Containers-PropertyEnvironment> instead of a simple dictionary. Notice that https://github.com/Ducasse/Containers-PropertyEnvironment <https://github.com/Ducasse/Containers-PropertyEnvironment> has 100% test coverage. Stef -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr http://www.synectique.eu / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

Aug. 13, 2018

A new rule to implement in Pharo ?

by Lionel Akue

Hello, Do you have a rule you would like to get implement in Pharo? I am reading about Renraku and I would like to exercise. Thanks, Lionel

Aug. 13, 2018

CfP: Next Generation Programming Paradigms and Systems (NGPS at SAC 2019)

by Nick Papoylias

------------------------------------------------------------------------------- Next Generation Programming Paradigms and Systems (NGPS 2019) Track of the 34th ACM/SIGAPP Symposium On Applied Computing Limassol, Cyprus https://ngps2019.github.io/ ------------------------------------------------------------------------------- AIMS AND TOPICS The complexity of modern software systems is continuously growing together with the communication capabilities and computational power of pervasive technology, embodied by a wide range of interacting heterogeneous smart devices. This new scenario is posing serious challenges to software development, which hardly keeps pace with this technological evolution. Sophisticated frameworks exposed through application programming interfaces, or directly integrated with mainstream programming languages provide partial solutions to support big data streaming and complex analytic; dynamic, autonomous, and collective coordination and adaptation capabilities; emergent behavior in cooperating systems; Internet of Things (IoT) systems development and maintenance; and employment of cloud platforms and parallel architectures, in particular heterogeneous ones. This calls for new abstractions, features, middlewares and tools able to reduce the time, effort, and cost of designing and developing the next generation software systems, improving performance, and ensuring reliability and security. To this aim, NGPS is seeking to advance the state-of-the-art and the state-of-the-practice of computational models and paradigms, formal techniques and software methods for easing software development and verification, and improving efficiency of complex modern systems. The specific topics of interest for the NGPS track include, but are not limited to, the following: - Integration of computational paradigms - Runtime verification and monitoring - Platforms for the Cloud - IoT systems - Secure and dependable software - Formal models and verification - Testing and debugging - System evaluation - Design, implementation and optimization of high-level programming languages - Middleware platforms - Scenarios, case studies and experience reports on innovative applications - High-level parallel programming - Distributed systems and concurrency - Development tools - Coordination models, specification, and technologies - Multi-agent systems, mobile agents, intelligent agents, and agent-based simulations - Models, frameworks and tools for Collective Adaptive Systems - Internet, Web, and pervasive computing systems - Self-organizing, self-adaptive, context-aware and nature-inspired systems - Security, trust and privacy management SUBMISSIONS Prospective papers should be submitted to the track in pdf format using the START submission system for regular and SRC papers available through the SAC 2019 home page. Submission of the same paper to multiple tracks is not allowed; all papers should represent original and previously unpublished works that are currently not under review in any conference or journal. Both basic and applied research papers are welcome. SAC 2019 will use double-blind reviewing; to facilitate this, author name(s) and institution(s) must be omitted, and references to authorsâ own related work should be in the third person. The format of the paper must adhere to the sig-alternate style. Full papers are limited to 8 pages, in camera-ready format, included in the registration fee. Authors have the option to include up to two (2) extra pages at additional fee of US$80 per page. Papers accepted as posters are limited to 3 pages, in camera-ready format, included in the registration fee. Authors have the option to include only one (1) extra page at additional fee of US$80. SRC abstracts are limited to 4 pages, in camera-ready format, included in the registration fee. No extra pages are allowed. Accepted papers will be published by ACM in the annual conference proceedings. Accepted posters will be published as extended abstracts in the same proceedings. Papers that fall short the above requirements are subjected to rejection. All papers must be submitted by September 10, 2018. For more information please visit the SAC 2019 home page. Paper registration is required, allowing the inclusion of the paper/poster in the conference proceedings. An author or a proxy attending SAC MUST present the paper: This is a requirement for the paper/poster to be included in the ACM/IEEE digital library. No-show of scheduled papers and posters will result in excluding them from the ACM/IEEE digital library. DEADLINES Sept 10, 2018 Submission of regular papers and SRC research abstracts Nov 10, 2018 Notification of paper acceptance/rejection Nov 10, 2018 Notification of SRC acceptance/rejection Nov 25, 2018 Camera-ready copies of accepted papers/SRC Dec 10, 2018 Author registration due date April 8-12, 2019 ACM SAC Conference TRACK CO-CHAIRS Davide Ancona, DIBRIS, University of Genova, IT Frederic Loulergue, SICCS, Northern Arizona University, USA Danilo Pianini, DISI, University of Bologna, IT Mirko Viroli, DISI, University of Bologna, IT PROGRAM COMMITTEE (to be completed) Mohamad Al Hajj Hassan, Huawei, DE Lorenzo Bettini, DISIA, University of Florence, IT HÃ©lÃ¨ne Coullon, IMT Atlantique, Inria, FR Ferruccio Damiani, DI, University of Torino, IT Simon Dobson, CS, University of St Andrews, UK Kento Emoto, IPL-Lab, Kyushu Institute of Technology, JP Erik Ernst, Google Inc., USA Lukas Esterle, ALICE, Aston University, UK FrÃ©dÃ©ric Gava, LACL, UniversitÃ© Paris-Est CrÃ©teil, FR Robert Hirschfeld, HPI, University of Potsdam, DE Jaakko JÃ¤rvi, II, University of Bergen, NO Einar Broch Johnsen, UiO, University of Oslo, NO Khaled Hamidouche AMD Research, USA Geoff Hamilton, School of Computing, Dublin City University, IE Hideya Iwasaki, The University of Electro-Communications, JP Doug Lea, CS, University of New York at Oswego Michele Loreti, DI, University of Camerino, IT Alberto Lluch Lafuente, DTU COMPUTE, Technical University of Denmark, DK Hidehiko Masuhara, PRG, Tokyo Institute of Technology, JP Virginia Niculescu, CS, Babes-Bolyai University of Cluj-Napoca, RO Nick Papoulias, University of La Rochelle, UMR LIENSs, CNRS, FR AntÃ³nio Ravara, DI FCT, New University of Lisbon, PT Barbara Re, SST, University of Camerino, IT Sophie Robert, LIFO, University of OrlÃ©ans Stefan Rudolph, OC, Augsburg University, DE Maurice ter Beek, FMT-ISTI, CNR, IT Martin Wirsing, SoSy-Lab, LMU Munich, D

Aug. 13, 2018

Esteban's ChangeLog week of 6 August 2018

by estebanlm＠gmail.com

Hello! This is my weekly ChangeLog, from 6 August 2018 to 12 August 2018. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=6/8/2018&to=12/8/2018 ChangeLog ========= 7 August 2018: -------------- * I've been working on a new ODBC driver for Pharo, made on UFFI and Garage. Sadly, I cannot take the existing older ODBC driver as base because it was depending too much on old FFI structure. Also, it didn't have any test or example so it was hard to take as inspiration (too many differences to tacle). Anyway, the new ODBC driver will come soon(tm), in the mean time I needed to fix some issues on UnifiedFFI: * [case: 22287](https://pharo.fogbugz.com/f/cases/22287) * [case: 22300](https://pharo.fogbugz.com/f/cases/22300) This fixes some missing/incorrect parts on UFFI: first one adds a special handling for +size_t+ types (needed because they behave differently in different platforms/architectures). And the second fixes a problem when returning +enum+ values. cheers! Esteban

Aug. 13, 2018

Re: [Pharo-dev] Fwd: [Ann.] Pharo-HDFS API

by Sean P. DeNigris

Matteo Marra-2 wrote > I would like to shareâ¦ a library to access the Hadoop Distributed File > System (HDFS). Cool! Thanks :) ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Aug. 11, 2018

Fwd: [Ann.] Pharo-HDFS API

by Matteo Marra

Hello, I would like to share one of my projects that I am working on in my PhD. Since I am working on Big Data I wrote a library to access the Hadoop Distributed File System (HDFS). We implemented it as a FileSystem in Pharo, using the webHDFS API of HDFS to access the files. With this API you can browse the distributed file system and create/modify/delete directories and files. Here is the git repository: https://gitlab.soft.vub.ac.be/Marra/pharo-hdfs Documentation is in the readme. Ciao, Matteo

Aug. 10, 2018

[Pharo 7.0-dev] Build #1167: 22304-vmtarget-pharo-not-found-during-bootstrap

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1167 was: SUCCESS. The Pull Request #1678 was integrated: "22304-vmtarget-pharo-not-found-during-bootstrap" Pull request url: https://github.com/pharo-project/pharo/pull/1678 Issue Url: https://pharo.fogbugz.com/f/cases/22304 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 10, 2018

Re: [Pharo-dev] debugger "Step Out"

by Tim Mackinnon

When âstep-throughâ was added, that was a lifesaver as we have many block iterations. Step out would also be a few less clicks than run to curser ... so it sounds complimentary. Tim Sent from my iPhone > On 10 Aug 2018, at 04:12, Ben Coman <btc(a)openinworld.com> wrote: > > A very quick note because its hardly important so I know I'll forget it. > > Using MSVC recently and jumping back in the Pharo debugger > I had a moment when I missing their "Step Out" debugger feature. > > Probably less important in Pharo where we tend to have shorter methods, > and you can always select up the stack and "Step Over", > but while I was in-the-flow "Step Out" was what the thing I wanted. > > Anyway, just sharing the thought. > > cheers -ben

Aug. 10, 2018