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

[Pharo 8.0] Build #241: 3239-CDNode-protocols-look-totally-broken
by ci-pharo-ci-jenkins2＠inria.fr April 26, 2019

April 26, 2019

There is a new Pharo build available! The status of the build #241 was: SUCCESS. The Pull Request #3249 was integrated: "3239-CDNode-protocols-look-totally-broken" Pull request url: https://github.com/pharo-project/pharo/pull/3249 Issue Url: https://github.com/pharo-project/pharo/issues/patch Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #240: 3241-install-probot-to-suggest-us-to-not-forget-reviews
by ci-pharo-ci-jenkins2＠inria.fr April 26, 2019

April 26, 2019

There is a new Pharo build available! The status of the build #240 was: SUCCESS. The Pull Request #3248 was integrated: "3241-install-probot-to-suggest-us-to-not-forget-reviews" Pull request url: https://github.com/pharo-project/pharo/pull/3248 Issue Url: https://github.com/pharo-project/pharo/issues/3241 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #239: 2590-We-can-get-two-times-the-mouseEntermouseLeave-event-when-subscribing-to-the-eventHandler-of-a-Morph
by ci-pharo-ci-jenkins2＠inria.fr April 26, 2019

April 26, 2019

There is a new Pharo build available! The status of the build #239 was: SUCCESS. The Pull Request #2724 was integrated: "2590-We-can-get-two-times-the-mouseEntermouseLeave-event-when-subscribing-to-the-eventHandler-of-a-Morph" Pull request url: https://github.com/pharo-project/pharo/pull/2724 Issue Url: https://github.com/pharo-project/pharo/issues/2590 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #238: 3217-copy-class-do-not-copy-class-side-instanceVariableNames
by ci-pharo-ci-jenkins2＠inria.fr April 26, 2019

April 26, 2019

There is a new Pharo build available! The status of the build #238 was: SUCCESS. The Pull Request #3230 was integrated: "3217-copy-class-do-not-copy-class-side-instanceVariableNames" Pull request url: https://github.com/pharo-project/pharo/pull/3230 Issue Url: https://github.com/pharo-project/pharo/issues/3217 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #237: newbutton2
by ci-pharo-ci-jenkins2＠inria.fr April 25, 2019

April 25, 2019

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

1 0

[Pharo 8.0] Build #236: Exporting MCZ from the BaselineOfMetacello
by ci-pharo-ci-jenkins2＠inria.fr April 25, 2019

April 25, 2019

There is a new Pharo build available! The status of the build #236 was: SUCCESS. The Pull Request #3215 was integrated: "Exporting MCZ from the BaselineOfMetacello" Pull request url: https://github.com/pharo-project/pharo/pull/3215 Issue Url: https://github.com/pharo-project/pharo/issues/exporting Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

ReadWriteStream>>on:
by Ben Coman April 25, 2019

April 25, 2019

I notice... rs := ReadStream on: #( 1 2 3 4 5 6 7 8 9). rs do: [ :x | self inform: x printString ]. ==> shows 10 notifications. but... rws := ReadWriteStream on: #( 1 2 3 4 5 6 7 8 9). rws do: [ :x | self inform: x printString ] ==> nothing it seems because "readLimit" instance variable of ReadWriteStream is zero. Comparing... ReadStream(PositionalStream)>>on: aCollection readLimit := aCollection size. ReadWriteStream(WriteStream)>>on: aCollection readLimit := 0. I wonder if ReadWriteStream should override #on: to set readLimit similar to ReadStream, but are there subtleties in the stream hierarchy I'm not aware of ? cheers -ben

1 0

Call for Papers, The Programming Journal, Volume 4, Issue 2
by Fabio Niephaus April 25, 2019

April 25, 2019

======================================================================== The Programming Journal The Art, Science, and Engineering of Programming Call for Papers for Volume 4, Issue 2 http://programming-journal.org/cfp/ Follow us @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: June 1 First notification: August 1 Revised submission: September 1 Final notification: September 7 Camera-ready: September 15 Weâll also solicit submissions for Issue 3, for full details, see: https://programming-journal.org/timeline/ ## 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, FernuniversitÃ¤t 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 #235: 3219-bad-argument-names
by ci-pharo-ci-jenkins2＠inria.fr April 25, 2019

April 25, 2019

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

1 0

[Pharo 8.0] Build #234: 3218-Clean-Refactoring-change-tests
by ci-pharo-ci-jenkins2＠inria.fr April 25, 2019

April 25, 2019

There is a new Pharo build available! The status of the build #234 was: SUCCESS. The Pull Request #3221 was integrated: "3218-Clean-Refactoring-change-tests" Pull request url: https://github.com/pharo-project/pharo/pull/3221 Issue Url: https://github.com/pharo-project/pharo/issues/3218 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0