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

[Pharo 8.0] Build #608: Repackage PositionableStream class >> with:do:
by ci-pharo-ci-jenkins2＠inria.fr Aug. 9, 2019

Aug. 9, 2019

There is a new Pharo build available! The status of the build #608 was: SUCCESS. The Pull Request #4247 was integrated: "Repackage PositionableStream class >> with:do: " Pull request url: https://github.com/pharo-project/pharo/pull/4247 Issue Url: https://github.com/pharo-project/pharo/issues/PositionableStream_class_with… Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #607: Exposing icon from the worldState with a form as argument.
by ci-pharo-ci-jenkins2＠inria.fr Aug. 9, 2019

Aug. 9, 2019

There is a new Pharo build available! The status of the build #607 was: FAILURE. The Pull Request #4249 was integrated: "Exposing icon from the worldState with a form as argument." Pull request url: https://github.com/pharo-project/pharo/pull/4249 Issue Url: https://github.com/pharo-project/pharo/issues/fix/icontests Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #606: Repackage PositionableStream class >> with:do:
by ci-pharo-ci-jenkins2＠inria.fr Aug. 9, 2019

Aug. 9, 2019

There is a new Pharo build available! The status of the build #606 was: FAILURE. The Pull Request #4247 was integrated: "Repackage PositionableStream class >> with:do: " Pull request url: https://github.com/pharo-project/pharo/pull/4247 Issue Url: https://github.com/pharo-project/pharo/issues/PositionableStream_class_with… Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #605: Cleaning class names, comments, method formatting of Spec2-PolyWidgets
by ci-pharo-ci-jenkins2＠inria.fr Aug. 9, 2019

Aug. 9, 2019

There is a new Pharo build available! The status of the build #605 was: FAILURE. The Pull Request #4257 was integrated: "Cleaning class names, comments, method formatting of Spec2-PolyWidgets" Pull request url: https://github.com/pharo-project/pharo/pull/4257 Issue Url: https://github.com/pharo-project/pharo/issues/4250 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Call for Papers, The Programming Journal, Volume 4, Issue 3
by Fabio Niephaus Aug. 8, 2019

Aug. 8, 2019

======================================================================== The Programming Journal The Art, Science, and Engineering of Programming Call for Papers for Volume 4, Issue 3 http://programming-journal.org/cfp/ Follow us on Twitter: @programmingconf ======================================================================== The Art, Science, and Engineering of Programming was created with the goal of placing the wonderful art of programming on the map of scholarly works. Many academic journals and conferences exist that publish research related to programming, starting with programming languages, software engineering, and expanding to the whole Computer Science field. Yet, many of us feel that, as the field of Computer Science expanded, programming, in itself, has been neglected to a secondary role not worthy of scholarly attention. That is a serious gap, as much of the progress in Computer Science lies on the basis of computer programs, the people who write them, and the concepts and tools available to them to express computational tasks. The Art, Science, and Engineering of Programming aims at closing this gap by focusing primarily on programming: the art itself (programming styles, pearls, models, languages), the emerging science of understanding what works and what doesnât work in general and in specific contexts, as well as more established engineering and mathematical perspectives. We solicit papers describing work from one of the following perspectives: Art: knowledge and technical skills acquired through practice and personal experiences. Examples include libraries, frameworks, languages, APIs, programming models and styles, programming pearls, and essays about programming. Science (Theoretical): knowledge and technical skills acquired through mathematical formalisms. Examples include formal programming models and proofs. Science (Empirical): knowledge and technical skills acquired through experiments and systematic observations. Examples include user studies and programming-related data mining. Engineering: knowledge and technical skills acquired through designing and building large systems and through calculated application of principles in building those systems. Examples include measurements of artifactsâ properties, development processes and tools, and quality assurance methods. Independent of the type of work, the journal accepts submissions covering several areas of expertise, including but not limited to: - General-purpose programming - Data mining and machine learning programming, and for programming - Database programming - Distributed systems programming - Graphics and GPU programming - Interpreters, virtual machines, and compilers - Metaprogramming and reflection - Model-based development - Modularity and separation of concerns - Parallel and multi-core programming - Program verification - Programming education - Programming environments - Security programming - Social coding - Testing and debugging - User interface programming - Visual and live programming All details, including the selection process are described on http://programming-journal.org/cfp/ Details on the submission processed are available at http://programming-journal.org/submission/ Authors of accepted papers will be invited to present at the <Programming>â20 conference in Porto, Portugal from March 23-26: https://2020.programming-conference.org/ ## Upcoming Deadlines We solicit submissions for the following upcoming deadlines: Submission: October 1 First notification: December 1 Revised submission: January 1 Final notification: January 7 Camera-ready: January 15 ## Standing Review Committee Volume 4 Christophe Scholliers, Ghent University Coen De Roover, Vrije Universiteit Brussel Craig Anslow, Victoria University of Wellington, New Zealand Didier Verna, EPITA / LRDE, France Diego Garbervetsky, University of Buenos Aires Edd Barrett, King's College London Erik Ernst, Google Felienne Hermans, Leiden University Francisco Sant'Anna, Rio de Janeiro State University Friedrich Steimann, University of Hagen Gordana Rakic, University of Novi Sad Guido Salvaneschi, TU Darmstadt Hidehiko Masuhara, Tokyo Institute of Technology Jeremy Gibbons, University of Oxford Jonathan Edwards, US Jun Kato, AIST, Japan Luke Church, University of Cambridge Matthew Flatt, University of Utah Michael L. Van De Vanter, Cal Poly San Luis Obispo NicolÃ¡s Cardozo, Universidad de los Andes, Colombia Stephen Kell, University of Kent ## Editors Stefan Marr (Editor Volume 4), University of Kent Cristina V. Lopes (Editor-in-Chief), University of California, Irvine

1 0

[Pharo 8.0] Build #604: Fix allocation tests
by ci-pharo-ci-jenkins2＠inria.fr Aug. 8, 2019

Aug. 8, 2019

There is a new Pharo build available! The status of the build #604 was: SUCCESS. The Pull Request #4230 was integrated: "Fix allocation tests" Pull request url: https://github.com/pharo-project/pharo/pull/4230 Issue Url: https://github.com/pharo-project/pharo/issues/fix/allocationTests Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #603: Fix word layouts and friends
by ci-pharo-ci-jenkins2＠inria.fr Aug. 8, 2019

Aug. 8, 2019

There is a new Pharo build available! The status of the build #603 was: SUCCESS. The Pull Request #4243 was integrated: "Fix word layouts and friends" Pull request url: https://github.com/pharo-project/pharo/pull/4243 Issue Url: https://github.com/pharo-project/pharo/issues/fix/wordlayouts Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #601: 4214-Code-Completion-DNU-on-visitAssignmentNode
by ci-pharo-ci-jenkins2＠inria.fr Aug. 6, 2019

Aug. 6, 2019

There is a new Pharo build available! The status of the build #601 was: FAILURE. The Pull Request #4215 was integrated: "4214-Code-Completion-DNU-on-visitAssignmentNode" Pull request url: https://github.com/pharo-project/pharo/pull/4215 Issue Url: https://github.com/pharo-project/pharo/issues/4214 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Iceberg and package renamings
by Torsten Bergmann Aug. 6, 2019

Aug. 6, 2019

Hi, usually when contributing I download a fresh Pharo 8 image (built by CI) using either Launcher or ZeroConf and use the Iceberg "repair" functionality to connect to / checkout the existing local clone of the repo with the Pharo 8 branch. This way I usually easily come easily to the "up to date" state and can start own modifications. But this time I used an older Pharo 8 image. So I pulled from upstream, pushed to my origin (forked git repo) and updated an already existing image also using the "repair" functionality. The changes where assembled and loaded. This way I also got into the "up to date" state for this image. But as one of the last changes done was a package renaming of "ReleaseTest" into "Release-Tests" this was reflected on the "src" folder on disk but not in the image itself. So unfortunately - the git repo was already having a "Release-Tests" folder in synch with the upstream - the local "up to date" image stayed with the old "ReleaseTests" package name as it was updated and not freshly bootstrapped from Baselines and with this out of synch. See attached screenshot. So I guess Iceberg's updating can not yet properly handle package renamings, maybe this is a known bug / not yet implemented feature - or something that is not easy to fix due to the renaming. Is this known? Could it be handled in the future? Just want to mention this as this could be a source of further problems when contributors update their image instead of using a new CI built one as they may hit such a renamed package. Bye T.

1 0

[Pharo 8.0] Build #600: Remove-shadow-variables
by ci-pharo-ci-jenkins2＠inria.fr Aug. 6, 2019

Aug. 6, 2019

There is a new Pharo build available! The status of the build #600 was: FAILURE. The Pull Request #4193 was integrated: "Remove-shadow-variables" Pull request url: https://github.com/pharo-project/pharo/pull/4193 Issue Url: https://github.com/pharo-project/pharo/issues/Remove Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0