- Pharo-dev - lists.pharo.org

DNU Create button auto extension category
by Ben Coman May 12, 2019

May 12, 2019

Currently when a DNU occurs we get this cool <Create> button, but when this presents the dialog "New Protocol Name" I get a blank list and the default is "as yet unclassified" and I end up with a heap of such unclassified methods to sort later. I am wondering if it could be smarter when tests are being run. A reasonable assumption could be that the test's package name is closely related to the likely extension package name. So for a DNU, I wonder if the debugger could walk the stack to discover if a TestCase subclass was on the stack (e.g. MyTestCase) and then determine which package MyTestCase belonged to, and present that as a choice for "New Protocol Name", helping categorize extension methods. I've started to play like this... TestCase subclass: #MyTestRoot MyTestRoot >> runCase [ super runCase ] on: MessageNotUnderstood do: [ :ex | "do something here, but for now..." ex pass ]. but before getting to deep, I'm seeking suggestions/solutions from the community. cheers -ben

4 9

Call for Papers: COP 2019
by Fabio Niephaus May 12, 2019

May 12, 2019

============================================================================ Call for Papers: COP 2019 The 11th International Workshop on Context-Oriented Programming and Advanced Modularity (COP) Co-located with ECOOP 2019 July 15th - 19th, 2019, London, United Kingdom https://2019.ecoop.org/home/COP-2019 ============================================================================ Contextual information plays an ever-increasing role in our information- centric world. Current-day software systems adapt continuously to changing execution and usage contexts, even while running. Unfortunately, mainstream programming languages and development environments still do not support this kind of dynamicity very well, leading developers to implement complex designs to anticipate various dimensions of variability. Context-Oriented Programming directly supports variability at the programming level, depending on a wide range of dynamic attributes. It enables run-time behavior to be dispatched directly on any detected properties of the execution or user context. Since more than a decade, researchers have been working on a variety of notions approaching that idea. Implementations ranging from first prototypes to mature platform extensions used in commercial deployments have illustrated how multidimensional dispatch can be supported effectively to achieve expressive run-time variation in behavior. The previous editions of this workshop at ECOOP (since 2009) have each attracted around 30 participants. The goal of the 11th Workshop on Context-Oriented Programming is to further establish context orientation as a common thread throughout language design, application development, and system support. In 2019 we also hope to advance this vibrant research domain at ECOOP in the versatile city of London. According to Wikipedia, London is considered to be one of the worldâs most important global cities and has been termed the worldâs most powerful, most desirable, most influential, most visited, most expensive, innovative, sustainable, most investment friendly, most popular for work, and the most vegetarian friendly city in the world, all depending on the context. Call for Papers --------------- COP invites submissions of high-quality papers reporting original research, or describing innovative contributions to, or experience with context- oriented programming, its implementation, and application. Papers that depart significantly from established ideas and practices are particularly welcome. All papers must be original. Submissions must not have been published previously and must not be simultaneously submitted or under review at any other refereed event or publication. The program committee will evaluate each contributed paper based on its relevance, significance, clarity, and originality. Topics ------ Topics of interest to the workshop include, but are not limited to: - Interesting application domains and scenarios for COP; - Programming language abstractions for COP (e.g., dynamic scoping, roles, traits, prototype-based extensions); - Implementation techniques and mechanisms for COP (e.g., different kinds of dynamic, contextual, and multi-dimensional dispatch or pre-dispatch); - Implementation issues for COP (e.g., optimization, VM support, JIT compilation); - Implemented use-cases, case studies, or prototypes of COP; - Theoretical foundations for COP (e.g., semantics, type systems); - Configuration languages (e.g., feature description interpreters, transformational approaches); - Interaction between non-functional programming concerns and COP (e.g., security, persistence, concurrency, distribution); - Modularization approaches for COP (e.g., modules, aspects, features, layers, plugins); Guidelines to apply COP (e.g., best practices, idioms, patterns); - Run-time support for COP (e.g., reflection, dynamic binding); - Tool support (e.g., design tools, IDEs, debuggers); - Support for COP at the modeling level; - Beyond context-oriented behavior adaptation (e.g., UI adaptation, DB adaptation). Submission Guidelines --------------------- Papers are to be submitted via EasyChair. They must be written in English, provided as PDF documents, and follow the new ACM Master Article Template with the sigconf option. They should not exceed 8 pages. Accepted papers will be published in the ACM Digital Library. Submission Site: https://easychair.org/conferences/?conf=cop2019 Template: https://www.acm.org/publications/proceedings-template Important Dates --------------- Submission deadline: 2019-05-20 Author notification: 2019-06-10 All deadlines are Anywhere on Earth (AoE), i.e. GMT/UTC-12:00 hour. Program Committee ----------------- Walter Binder, University of Lugano, Switzerland Walter Cazzola, UniversitÃ degli Studi di Milano, Italy Shigeru Chiba, University of Tokyo, Japan Cynthia Disenfeld, University of Toronto, Canada BenoÃ®t Duhoux, UniversitÃ© catholique de Louvain, Belgium David H. Lorenz, Open University and Technion IIT, Israel Robert Hirschfeld, Hasso-Plattner-Institut (HPI), Germany Atsushi Igarashi, Kyoto University, Japan Tetsuo Kamina, Oita University, Japan Gary Leavens, University of Central Florida, United States Mariana Marasoiu, University of Cambridge, United Kingdom Hidehiko Masuhara, Tokyo Institute of Technology, Japan Roly Perera, Alan Turing Institute, United Kingdom Organizers ---------- David H. Lorenz, Open University and Technion IIT, Israel Robert Hirschfeld, Hasso-Plattner-Institut (HPI), Germany Atsushi Igarashi, Kyoto University, Japan Hidehiko Masuhara, Tokyo Institute of Technology, Japan

1 0

[Pharo 8.0] Build #268: Fixes #3115
by ci-pharo-ci-jenkins2＠inria.fr May 12, 2019

May 12, 2019

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

1 0

consortium engineers
by Ben Coman May 12, 2019

May 12, 2019

I hadn't heard before... four consortium engineers for a year, very cool... slides 3 & 4... https://www.slideshare.net/pharoproject/pharo-70-and-80-alpha thanks Schmidt & LIfeware, and all consortium partners. cheers -ben

2 1

[Pharo 8.0] Build #267: 3320-Improve-HistorySlot-and-other-small-fixes
by ci-pharo-ci-jenkins2＠inria.fr May 12, 2019

May 12, 2019

There is a new Pharo build available! The status of the build #267 was: FAILURE. The Pull Request #3321 was integrated: "3320-Improve-HistorySlot-and-other-small-fixes" Pull request url: https://github.com/pharo-project/pharo/pull/3321 Issue Url: https://github.com/pharo-project/pharo/issues/3320 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #266: Fix wording typo
by ci-pharo-ci-jenkins2＠inria.fr May 11, 2019

May 11, 2019

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

1 0

[Pharo 8.0] Build #265: 3312-KMKeymapnotifyPartialMatchTo-leads-to-an-error
by ci-pharo-ci-jenkins2＠inria.fr May 10, 2019

May 10, 2019

There is a new Pharo build available! The status of the build #265 was: FAILURE. The Pull Request #3313 was integrated: "3312-KMKeymapnotifyPartialMatchTo-leads-to-an-error" Pull request url: https://github.com/pharo-project/pharo/pull/3313 Issue Url: https://github.com/pharo-project/pharo/issues/3312 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #264: 3328-SubclassResponsibility-error-when-running-RBParserparseFaultyMethod
by ci-pharo-ci-jenkins2＠inria.fr May 10, 2019

May 10, 2019

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

1 0

introducing my GSoC project - Improving Code Completion
by Myroslava Romaniuk May 9, 2019

May 9, 2019

Hi everyone, My name is Myroslava, I'm a 3rd year CS student in Ukraine, and my project Improving Code Completion has been selected for this year's GSoC. Some of you might know me from the 2 ESUGs I was at or maybe remember me previously doing GSoC in 2017, in any case I'm very happy to have been given this opportunity and I look forward to working with you! I started working on code completion last year during my internship at RMoD with Marcus and Stef, and I really want to make even more progress with code completion this summer and properly implement it inside Pharo as one of the options to use. You can read more about what has been done last summer and what is yet to be done this summer in my proposal (see attached). If you have any feedback or questions, don't hesitate to email me. Help and suggestions throughout my work on the project will be incredibly welcome too, as there's a lot to figure out how to do best. If you are interested in updates or want to keep in touch, I'm also on twitter <https://twitter.com/myroslavarm>, and I have a blog <https://medium.com/@myroslavarm> where I used to post about my progress in the last GSoC and about my internship at RMoD, and I will be writing there this summer, too. I'll also try to be more active in the mailing list and on discord :) Cheers, Myroslava

1 0

[Pharo 8.0] Build #263: [Fork2]2938 - Fixing FFIConstantHandleType externalType wrong in 64 bit
by ci-pharo-ci-jenkins2＠inria.fr May 9, 2019

May 9, 2019

There is a new Pharo build available! The status of the build #263 was: SUCCESS. The Pull Request #3252 was integrated: "[Fork2]2938 - Fixing FFIConstantHandleType externalType wrong in 64 bit " Pull request url: https://github.com/pharo-project/pharo/pull/3252 Issue Url: https://github.com/pharo-project/pharo/issues/2938 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0