July 2020 - Pharo-dev - lists.pharo.org

[Pharo 9.0] Build #539: Compiler-OCAbstractMethodScope-push-node-down

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

There is a new Pharo build available! The status of the build #539 was: FAILURE. The Pull Request #6942 was integrated: "Compiler-OCAbstractMethodScope-push-node-down" Pull request url: https://github.com/pharo-project/pharo/pull/6942 Issue Url: https://github.com/pharo-project/pharo/issues/Compiler Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 22, 2020

[Pharo 9.0] Build #538: ReImplementedNotSentRule-tellmeMore

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

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

July 22, 2020

[Pharo 9.0] Build #537: Variables-isReferenced-cleanup

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

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

July 22, 2020

[2nd CfP] MPLR 2020 - 17th International Conference on Managed Programming Languages & Runtimes

by Stefan Marr

======================================================================== Call for Papers MPLR 2020 - 17th International Conference on Managed Programming Languages & Runtimes November 4-6, 2020 in Manchester, United Kingdom https://mplr2020.cs.manchester.ac.uk/ Follow us @MPLR_Conf ======================================================================== The 17th International Conference on Managed Programming Languages & Runtimes (MPLR, formerly ManLang) is a premier forum for presenting and discussing novel results in all aspects of managed programming languages and runtime systems, which serve as building blocks for some of the most important computing systems in use, ranging from small-scale (embedded and real-time systems) to large-scale (cloud-computing and big-data platforms) and anything in between (desktop, mobile, IoT, and wearable applications). This year, MPLR will be held virtually. Registration and participation will be free. For up-to-date details, check out the conference website: https://mplr2020.cs.manchester.ac.uk/ and follow us on Twitter @MPLR_Conf. The areas of interest include but are not limited to: * Languages and Compilers - Managed languages (e.g., Java, Scala, JavaScript, Python, Ruby, C#, F#, Clojure, Groovy, Kotlin, R, Smalltalk, Racket, Rust, Go, etc.) - Domain-specific languages - Language design - Compilers and interpreters - Type systems and program logics - Language interoperability - Parallelism, distribution, and concurrency * Virtual Machines - Managed runtime systems (e.g., JVM, Android Runtime (ART), V8, LLVM, .NET CLR, RPython, GraalVM, etc.) - VM design and optimization - VMs for mobile and embedded devices - VMs for real-time applications - Memory management and garbage collection - Hardware/software co-design * Techniques, Tools, and Applications - Static and dynamic program analysis - Testing and debugging - Refactoring - Program understanding - Program synthesis - Security and privacy - Performance analysis and monitoring - Compiler and program verification Submission Categories --------------------- MPLR accepts four types of submissions: 1. Regular research papers describing novel contributions involving managed language platforms. Research papers will be evaluated based on their relevance, novelty, technical rigor, and contribution to the state-of-the-art. Format: up to 12 pages, excluding bibliography and appendix 2. Work-in-progress research papers describing promising new ideas, with perhaps less maturity than full Papers. Work-in-progress papers will be evaluated with an emphasis on novelty and the potential of the new ideas instead of technical rigor and experimental results. Format: up to 6 pages, excluding bibliography and appendix 3. Industry and tool papers presenting technical challenges and solutions for managed language platforms in the context of deployed applications and systems. Industry and tool papers will be evaluated on their relevance, usefulness, and results. Suitability for demonstration and availability will also be considered for tool papers. Format: up to 6 pages, excluding bibliography and appendix 4. Posters They will be evaluated similarly to work-in-progress papers. Posters can accompany any submission as a way to provide additional demonstration and discussion opportunities. Format: poster and 1-page abstract MPLR 2020 submissions must conform to the ACM Policy on Prior Publication and Simultaneous Submissions and to the SIGPLAN Republication Policy. See http://www.sigplan.org/Resources/Policies/Republication/ Author Instructions ------------------- Submissions need to use the ACM `acmart` format with the `sigconf` style: https://www.acm.org/publications/proceedings-template If you are using LaTeX, submissions need to use the 'acmart' document class with the 'sigconf' option. For reviewing, please include page numbers in your submission using the LaTeX command `\settopmatter{printfolios=true}`. The standard settings of a 9 point font size and the Libertine/Biolinum font family are to be kept. All submissions need to be in PDF format. MPLR uses single-blind reviewing, i.e., author names are generally included in submissions. Please also ensure that your submission is legible when printed on a black and white printer. In particular, please check that colors remain distinct and font sizes are legible. Submission Site: https://mplr2020.cs.manchester.ac.uk/submissions/ Important Dates --------------- Submission Deadline: 12 August 2020 Author Notification: 14 September 2020 Camera Ready: 05 October 2020 Conference Dates: 04-06 November 2020 All deadlines are 23:59 AoE (UTC-12h). AUTHORS TAKE NOTE: The official publication date is the date the proceedings are made available in the ACM Digital Library. This date may be up to two weeks prior to the first day of your conference. The official publication date affects the deadline for any patent filings related to published work. COVID-19 -------- MPLR will be held virtual to avoid any health risks to attendees and avoid uncertainties around traveling. Organization ------------ Program Committee: LubomÃr Bulej, Charles University, Czech Republic Jeronimo Castrillon, TU Dresden, Germany Shigeru Chiba, University of Tokyo, Japan Irene Finocchi, LUISS Guido Carli University, Italy Juliana Franco, Microsoft Research, UK Elisa Gonzalez Boix, Vrije Universiteit Brussel, Belgium Robert Hirschfeld, Hasso Plattner Institute, Germany Roberto Ierusalimschy, PUC-Rio, Brazil Georgia Kouveli, ARM, UK Burcu KÃ¼lahÃ§Ä±oÄlu Ãzkan, MPI-SWS, Germany Doug Lea, SUNY Oswego, USA Daryl Maier, IBM, Canada Mark Marron, Microsoft Research, USA Hidehiko Masuhara, Tokyo Institute of Technology, Japan Hanspeter MÃ¶ssenbÃ¶ck, JKU Linz, Austria Hannes Payer, Google, Germany Julien Ponge, Red Hat, France Aleksandar Prokopec, Oracle Labs, Switzerland Manuel Rigger, ETH Zurich, Switzerland Andrea Rosa, USI, Switzerland Jeremy Singer, University of Glasgow, UK Eli Tilevich, Virginia Tech, USA Sam Tobin-Hochstadt, Indiana University, USA Tobias Wrigstad, Uppsala University, Sweden General Chair: Christos Kotselidis, University of Manchester, UK Program Chair: Stefan Marr, University of Kent, UK If you are unsure whether a particular topic falls within the scope of MPRLâ20 or if you have any other questions, please do not hesitate to contact the Program Chair (s.marr(a)kent.ac.uk) -- Stefan Marr School of Computing, University of Kent https://stefan-marr.de/research/

July 21, 2020

what is newFrom:

by StÃ©phane Ducasse

Hi Iâm spotting real inconsistency in the specification and use of newFrom: In Pharo and Object we have newFrom: aSimilarObject "Create an object that has similar contents to aSimilarObject. If the classes have any instance variables with the same names, copy them across. If this is bad for a class, override this method." ^ (self isVariable ifTrue: [self basicNew: aSimilarObject basicSize] ifFalse: [self basicNew]) copySameFrom: aSimilarObject The ANSI standard does not define newFrom: Now in Pharo some classes such dictionary expect as argument a dictionary but OrderedDictionary expects a like of association! Set expects a collection, Bag too and many others. CompiledMethod expects a compiledMethod I think that it would be good to strengthen this method and we could define newFromSibling: but it looks like a copy to me. S -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Aurore Dalle 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

July 21, 2020

[Pharo 9.0] Build #536: Make RBComment a subclass of RBProgramNode

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

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

July 21, 2020

[Pharo 9.0] Build #535: Variables-isBlockVar-via-Variable

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

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

July 21, 2020

[Pharo 9.0] Build #534: 6928-BaselineOf-should-have-an-empty-baseline-class-method

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

There is a new Pharo build available! The status of the build #534 was: SUCCESS. The Pull Request #6932 was integrated: "6928-BaselineOf-should-have-an-empty-baseline-class-method" Pull request url: https://github.com/pharo-project/pharo/pull/6932 Issue Url: https://github.com/pharo-project/pharo/issues/6928 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 21, 2020

[Pharo 9.0] Build #533: Variable-isSelf-isSuper-deprecation

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

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

July 21, 2020

[Pharo 9.0] Build #532: Improving debugger infrastructure step 1: a Trait to unify the debugger API used by the system to open debuggers

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

There is a new Pharo build available! The status of the build #532 was: SUCCESS. The Pull Request #6901 was integrated: "Improving debugger infrastructure step 1: a Trait to unify the debugger API used by the system to open debuggers" Pull request url: https://github.com/pharo-project/pharo/pull/6901 Issue Url: https://github.com/pharo-project/pharo/issues/Unified Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 21, 2020