Squeak-dev March 2022

squeak-dev@lists.squeakfoundation.org

33 participants
304 discussions

The Trunk: Compiler-ul.473.mcz
by commits＠source.squeak.org 31 Mar '22

31 Mar '22

Levente Uzonyi uploaded a new version of Compiler to project The Trunk: http://source.squeak.org/trunk/Compiler-ul.473.mcz ==================== Summary ==================== Name: Compiler-ul.473 Author: ul Time: 31 March 2022, 4:52:35.531668 pm UUID: 110ed766-02b6-4cba-9053-f274e0c600ae Ancestors: Compiler-eem.472 - use Symbol class >> #lookup: instead of #hasInterned:ifTrue: =============== Diff against Compiler-eem.472 =============== Item was changed: ----- Method: Encoder>>lookupInPools:ifFound: (in category 'private') ----- lookupInPools: varName ifFound: assocBlock + ^(Symbol lookup: varName) + ifNil: [ false ] + ifNotNil: [ :symbol | + (cue bindingOf: symbol) + ifNil: [ false ] + ifNotNil: [:assoc| + assocBlock value: assoc. + true ]]! - ^Symbol - hasInterned: varName - ifTrue: - [:sym| - (cue bindingOf: sym) - ifNil: [^false] - ifNotNil: [:assoc| assocBlock value: assoc]]!

1 0

Call for Workshop Papers - ECOOP 2022
by Carolin Brandt 31 Mar '22

31 Mar '22

---------------------------------------------------------------------------------------- ECOOP 2022: Call for Workshop Papers ---------------------------------------------------------------------------------------- Summary: COP 2022: International Workshop on Context-Oriented Programming and Advanced Modularity Deadline: Friday, 15th of April Workshop on Formal Techniques for Java-like Programs Deadline: Friday, 1st of April ICOOOLPS’22: Workshop on Implementation, Compilation, Optimization of OO Languages, Programs and Systems Deadline: Thursday, 21st off April (Submission Talks, Demos, Position Papers) Program Analysis for WebAssembly (PAW) 2022 Deadline: Monday, 11th of April Programming Local-first Software Deadline: Friday, 1st of April PRIDE 2022: Workshop on Practical Research IDEs Deadline: Friday, 15th of April Truffle 2022: Truffle/GraalVM Languages Workshop Deadline: Saturday, 30th of April VORTEX 2022: Workshop on Verification and mOnitoring at Runtime EXecution Deadline: Monday, 18th of April ---------------------------------------------------------------------------------------- Detailed Calls for Papers: ---------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------- COP 2022: International Workshop on Context-Oriented Programming and Advanced Modularity ---------------------------------------------------------------------------------------- https://2022.ecoop.org/home/COP-2022 <https://2022.ecoop.org/home/COP-2022> Deadline: Friday, 15th of April ---------------------------------------------------------------------------------------- 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 scope of this workshop will further encompass diverse and advanced forms of modularity support in programming languages. We encourage results and discussions on advanced modularity that go beyond COP. ## 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: - Context-Oriented Programming (COP) and Contextual modeling in modern computer systems (mobile systems, IoTs, cloud/edge computing, autonomous systems, etc.); - Programming language abstractions for COP (e.g., dynamic scoping, roles, traits, prototype-based extensions); - Implementation issues for COP (e.g., optimization, VM support, JIT compilation); - COP applications in computer systems (e.g., mobile systems, IoTs, cloud/edge computing, security); - COP applications in autonomous systems (e.g., unmanned aerial vehicles, autonomous vehicles); - Configuration languages (e.g., feature description interpreters, transformational approaches); - Programming language abstractions for composition and modularization (e.g., modules, aspects, features, layers, plugins, libraries, components); - Theoretical foundations and reasoning support for COP and modular systems (e.g., semantics, type systems, mechanized proofs); - Software lifecycle support for modularization (e.g., requirements; architecture; synthesis; metrics; software product lines; economics; testing; patterns); - Tool support for modular software development (e.g., platform; refactoring; static and dynamic analysis; evolution; reverse engineering; mining); - Modular applications (e.g., data-intensive applications, micro-services, serverless computing); ### Submission guidelines Papers are to be submitted via [EasyChair](https://easychair.org/my/conference?conf=cop2022). They must be written in English, provided as PDF documents, and follow the new [ACM Master Article Template](https://www.acm.org/publications/proceedings-template) with the sigconf option. They should not exceed 8 pages. Accepted papers will be published in the ACM Digital Library (SCOPUS). ---------------------------------------------------------------------------------------- Workshop on Formal Techniques for Java-like Programs ---------------------------------------------------------------------------------------- https://2022.ecoop.org/track/ftfjp-2022 <https://2022.ecoop.org/track/ftfjp-2022> Deadline: Friday, 1st of April ---------------------------------------------------------------------------------------- Participation: Participation in the workshop is hybrid as with ECOOP 2022, but registration through the ECOOP registration system is required. As a hybrid event, when considering virtual mode, the registration system will provide you with the link to participate in the Zoom conference sessions. Formal techniques can help analyse programs, precisely describe program behaviour, and verify program properties. Modern programming languages are interesting targets for formal techniques due to their ubiquity and wide user base, stable and well-defined interfaces and platforms, and powerful (but also complex) libraries. New languages and applications in this space are continually arising, resulting in new programming languages (PL) research challenges. Work on formal techniques and tools and on the formal underpinnings of programming languages themselves naturally complement each other. FTfJP is an established workshop which has run annually since 1999 alongside ECOOP, with the goal of bringing together people working in both fields. The workshop has a broad PL theme; the most important criterion is that submissions will generate interesting discussions within this community. The term “Java-like” is somewhat historic and should be interpreted broadly: FTfJP solicits and welcomes submission relating to programming languages in general, beyond Java, including C#, Scala, etc. Example topics of interest include (but not limited to): - Language design and semantics - Type systems - Concurrency and new application domains - Specification and verification of program properties - Program analysis (static or dynamic) - Program synthesis - Security Pearls (programs or proofs) - Programming environments FTfJP welcomes submissions on technical contributions, case studies, experience reports, challenge proposals, tools, and position papers. Webpages for previous workshops in this series are available at: https://ftfjp.github.io/. We plan that, as in previous years, accepted papers will be published in the ACM Digital Library, though authors will be able to opt out of this publication, if desired. At least one author of an accepted paper must attend the workshop to present the work and participate in the discussions. ## Submissions Contributions are sought in two categories: * Full Papers (6 pages, excluding references) present a technical contribution, case study, tool, or detailed experience report. We welcome both complete and incomplete technical results; ongoing work is particularly welcome, provided it is substantial enough to stimulate interesting discussions. * Short Papers (2 pages, excluding references) should advocate a promising research direction, or otherwise present a position likely to stimulate discussion at the workshop. We encourage e.g. established researchers to set out a personal vision, and beginning researchers to present a planned path to a PhD. All submissions and reviews will be managed within EasyChair. Submissions should be made via https://easychair.org/conferences/?conf=ftfjp2022. There is no need to indicate the paper category (long/short). Both types of contributions will benefit from feedback received at the workshop. Submissions will be peer reviewed, and will be evaluated based on their clarity and their potential to generate interesting discussions. Reviewing will be single blind, there is no need to anonymize submissions. The format of the workshop encourages interaction. FTfJP is a forum in which a wide range of people share their expertise, from experienced researchers to beginning PhD students. ## Formatting and Publication All authors should use the official “ACM Master article template”, which can be obtained from the ACM Proceedings Template pages ( https://www.acm.org/publications/proceedings-template ). Latex users should use the “sigconf” option as well as “review” (to produce line numbers for easy reference by the reviewers). To that end, the following latex code can be placed at the start of the latex document: \documentclass[sigconf,review]{acmart} We plan that, as in previous years, accepted papers will be published in the ACM Digital Library, though authors will be able to opt out of this publication, if desired. At least one author of an accepted paper must register to the conference by the early registration date and attend the workshop to present the work and participate in the discussions. Selected papers will also be considered for extended versions to be submitted to the Journal of Object Technology (JOT). ---------------------------------------------------------------------------------------- ICOOOLPS’22: Workshop on Implementation, Compilation, Optimization of OO Languages, Programs and Systems ---------------------------------------------------------------------------------------- https://2022.ecoop.org/home/ICOOOLPS-2022 <https://2022.ecoop.org/home/ICOOOLPS-2022> Deadline: Thursday, 21st off April (Submission Talks, Demos, Position Papers) ---------------------------------------------------------------------------------------- The ICOOOLPS workshop series brings together researchers and practitioners working in the field of language implementation and optimization. The goal of the workshop is to discuss emerging problems and research directions as well as new solutions to classic performance challenges. The topics of interest for the workshop include techniques for the implementation and optimization of a wide range of languages including but not limited to object-oriented ones. Furthermore, virtual machines, meta-compilation techniques or language-agnostic approaches are welcome, too. Call for Contributions The ICOOOLPS workshop series brings together researchers and practitioners working in the field of language implementation and optimization (even beyond the historical OO background of the workshop). The goal of the workshop is to discuss emerging problems and research directions, as well as new solutions and techniques. We hope to provide a space for participation and discussion and in particular to discuss your work in progress. That’s why we’ll have two additional submission categories for position papers and talks. We also accept talk proposals for papers that have appeared at some other past conference, but didn’t receive much discussion there due to the conference being cancelled or virtual because of Covid. A non-exclusive list of topics of interest for this workshop is: • Implementation and optimization of fundamental languages features (from automatic memory management to metaprogramming) • Runtime systems technology (libraries, virtual machines) • Static, adaptive, and speculative optimizations and compiler techniques • Meta-compilation techniques and language-agnostic approaches for the efficient implementation of languages • Compilers (intermediate representations, offline and online optimizations,…) • Empirical studies on language usage, benchmark design, and benchmarking methodology • Resource-sensitive systems (real-time, low power, mobile, cloud) • Studies on design choices and tradeoffs (dynamic vs. static compilation, heuristics vs. programmer input,…) • Tooling support, debuggability and observability of languages as well as their implementations Workshop Format The workshop welcomes the presentation and discussion of new ideas and emerging problems. We aim to provide an environment to present and discuss your work at different stages of maturity. Therefore we provide three submission categories: • Full papers (up to 12 pages), which will be included in the proceedings; • Position papers (up to 4 pages), for work in progress, ideas in early stages; • Talks, Demos. Please note that option (1) features a different submission deadline than the rest and will include a short rebuttal period, in which authors will be able to answer reviewers comments. Submission To submit a paper please use the official “ACM Master article template”, which can be obtained from the ACM Proceedings Template pages. ICOOOLPS features a light-weight double-blind review process. Authors should omit their names in the submission. Use the sigconf option as well as review and anonymous, i.e., place the following at the start of the latex document: \documentclass[sigconf,review,anonymous]{acmart}. ---------------------------------------------------------------------------------------- Program Analysis for WebAssembly (PAW) 2022 ---------------------------------------------------------------------------------------- https://2022.ecoop.org/home/paw-2022 <https://2022.ecoop.org/home/paw-2022> Deadline: Monday, 11th of April ---------------------------------------------------------------------------------------- WebAssembly is a recently introduced portable virtual machine, to which code written in many high-level languages can be compiled in order to be executed in web browsers and other runtimes. There have been several independent efforts to bring static and dynamic analysis tools to the WebAssembly ecosystem. This workshop aims to bring together researchers working in the domain of static and dynamic analyses for WebAssembly. Specifically, this workshop aims to discuss all techniques related to detecting bugs and vulnerabilities in WebAssembly binaries, to build models of such binaries, to prove their correctness, to monitor their execution, or to optimize binaries for running time and binary size. The workshop will be a community-building event to exchange ideas and build collaborations in these domains. To that end, contributions in the form of submitted talks are welcome. The workshop will also hold discussion sessions in order to foster collaborations. Questions? Use the PAW contact form (https://2022.ecoop.org/contact2/paw-2022-papers <https://2022.ecoop.org/contact2/paw-2022-papers>). Call for presentations WebAssembly is a recently introduced portable virtual machine, to which code written in many high-level languages can be compiled in order to be executed in web browsers and other runtimes. There have been several independent efforts to bring static and dynamic analysis tools to the WebAssembly ecosystem. This workshop aims to bring together researchers working in the domain of static and dynamic analyses for WebAssembly. Specifically, this workshop aims to discuss all techniques related to detecting bugs and vulnerabilities in WebAssembly binaries, to build models of such binaries, to prove their correctness, to monitor their execution, or to optimise binaries for running time and binary size. The PAW workshop is a community-building event, for exchanging ideas and fostering collaborations in these domains. The workshop will consist of submitted and invited talks, as well as discussion sessions. To that end, we invite submissions for talks in the form of a 1-page abstract delineating at a high-level the content of the proposed presentation. Submission site: https://easychair.org/conferences/?conf=paw2022 Timeline: • April 11 2022: Submission deadline • May 2 2022: Acceptance notification • June 6-10 2022: ECOOP conference ---------------------------------------------------------------------------------------- Programming Local-first Software ---------------------------------------------------------------------------------------- https://2022.ecoop.org/home/plf-2022 <https://2022.ecoop.org/home/plf-2022> Deadline: Friday, 1st of April ---------------------------------------------------------------------------------------- Languages for Multi-Device Collaborative Applications Due to ubiquitous connectivity and cheap availability of user devices from smartphones to desktops, applications supporting multi-device and collaborative use have become more common, and with the Corona pandemic this trend has tremendously accelerated. While most of the distributed applications that we see nowadays are cloud-based, avoiding the cloud can lead to privacy and performance benefits for users and operational and cost benefits for companies and developers. Following this idea, Local-First Software runs and stores its data locally while still allowing collaboration, thus retaining the benefits of existing collaborative applications without depending on the cloud. Many specific solutions already exist: operational transformation, client-side databases with eventually consistent replication based on CRDTs, and even synchronization as a service provided by commercial offerings, and a vast selection of UI design libraries. However, these solutions are not integrated with the programming languages that applications are developed in. Language based solutions related to distribution such as type systems describing protocols, reliable actor runtimes, data processing, machine learning, etc., are designed and optimized for the cloud not for a loosely connected set of cooperating devices. This workshop aims at bringing the issue to the attention of the PL community, and accelerating the development of suitable solutions for this area. Workshop timeline Note: Times are only examples and will change along the main conference and other workshops. We currently plan an in-person event, however, we will keep monitoring the ongoing situation. In case of a virtual workshop, we will ask speakers to prerecord their talk, and organize live Q&A sessions. We do plan to make the workshop accessible to remote participation for non-speakers. • ~09:30 Keynote (TBA) • ~10:30 Accepted talk block 1 • ~13:00 Accepted talk block 2 • ~16:00 Panel discussion (TBA) Call for Talks and Papers Note: details about the process are still subject to change. Scope of contributions We are looking to advance the state of the art to program local-first software, that is, programs that are useful to a single user while offline, but allow sharing and collaboration when connected. Examples topics include: • language constructs that enable offline use • case studies that consider what works well and what is challenging using existing languages • UI techniques that consider connectivity states • users, identities, and trust as language constructs • type systems to track what functionality is available offline • easy to use APIs for (new and existing) efficient data synchronization algorithms • dynamic placement techniques that scale down to a single offline device Types of contribution We encourage a range of contributions to facilitate exchange between academia and industry. Specifically, we are looking for: • Talk proposals of at most 1 page summarizing: • the content and scope • the context (speaker, company, research group, larger project, etc.) • include links to further info if available (an existing published paper, prior talks, project websites, etc.) • Relevant in progress research papers: • no format or page limit • if the paper is longer than 8 pages: include a summary one or two key contributions/sections the reviewers should focus on • these will receive reviews by the organizing committee focused on potential improvements • there will be no officially published proceedings, but papers will be listed on the website if the authors agree If accepted, authors of both types of submission are assigned a 25 minute slot for a talk + 5 minutes for questions. In addition, submissions are published on the website. Timeline and submission • 2022-04-01 Submission closes • 2022-05-01 Notification of accepted papers Use the submission link at the top of the right sidebar. For talk proposals, you may either upload a PDF, or put the proposal into the “abstract” field of the submission site. For in progress papers of more than 8 pages, include the description of what the reviewers should focus on as part of the abstract. In case will would only attend the workshop in person or only via video conferencing, please indicate this as part of the submission (in the abstract field). Questions? Use the PLF contact form (https://2022.ecoop.org/contact2/plf-2022-papers <https://2022.ecoop.org/contact2/plf-2022-papers>) ---------------------------------------------------------------------------------------- PRIDE 2022: Workshop on Practical Research IDEs ---------------------------------------------------------------------------------------- https://2022.ecoop.org/home/pride-2022 <https://2022.ecoop.org/home/pride-2022> Deadline: Friday, 15th of April ---------------------------------------------------------------------------------------- Goal of the Workshop The goal of this workshop is to help researchers take their research developments and integrate them easily into existing IDE tools. We are seeking participation from researchers who have developed novel analysis technology and would like an easy way to deploy this technology in existing IDE tools. For example, a new, more-precise taint analysis is nice, but it will be potentially much easier to use and to evaluate if it is available in popular IDE’s—e.g. IntelliJ, VisualStudio Code—in editors—e.g. Sublime Text, Atom—and traditional editors used by programmers—e.g. Emacs, Vim. We welcome researchers who are interested in IDE integration of program analyses to submit talk proposals (see Call for Talks). We will also host a hands-on Panathon session (Call for Participation in Panathon) where participants will be using MagpieBridge to integrate their own program analysis tools. MagpieBridge provides support for accomplishing this: it provides a framework in which a research analysis can be invoked from standard IDE’s. The underlying mechanism makes use of the Language Server Protocol (LSP), but that is completely hidden by a straightforward API that allows analyses to be invoked on source projects from IDE’s and report results that get displayed in idioms natural to each IDE. Such functionality could benefit a wide range of research tools, and so we encourage participation by bringing either your own research analysis or any analysis that you would like to see in a tool. Preliminary Workshop Program Date: Tuesday, 7 June 2022 Time Session 09:00 - 09:15 — Welcome by the organizers 09:15 - 12:00 — Invited Talks (See Call for Talks) 13:00 - 14:00 — MagpieBridge Tutorial 14:00 - 17:00 — Panathon (See Call for Participation in Panathon) 17:00 - 18:30 — Demonstration and Best IDE Integration Award Questions? Use the PRIDE contact form (https://2022.ecoop.org/contact2/pride-2022 <https://2022.ecoop.org/contact2/pride-2022>) --- Call for Talks --- We look for talk proposals for the Invited Talks session. We welcome submissions addressing the following topics: • Past experience with integrating program analyses into IDEs. E.g, it would describe an integration into an IDE, and discuss how MagpieBridge simplified it. It could contrast MagpieBridge with other integrations, or it could show issues using MagpieBridge and possible improvements, • Tool demonstration. A tool demonstration should show a running analysis integrated into IDEs, and the talk would focus on how the information is displayed and how the mechanisms are used to show the analysis. • Report of user experience and expectation. A report of user experience would discuss user studies of IDE integration of program analyses. It should focus on how the integration works, what informations is displayed, how the study was designed and results. • Explainability of analysis result. Explainability of analysis results would describe novel IDE mechanisms for displaying results, and how that was done. For instance, mechanisms for showing interprocedural data-flow paths. Authors of accepted proposals will be invited to give a talk (10 - 15 mins + 5 mins Q&A) at the workshop. How to Submit All submissions must confirm to the ECOOP 2022 formatting instructions and must not exceed 2 pages for the main text, inclusive of all figures and tables. Reference has no page limit. The submission is non-blind. Please include your name, e-mail and affiliation in the submission. The proposal should describe: motivation, background about the program analysis tool, lessons learned or features of the IDE integration, looks of the analysis result in IDE, user feedbacks, challenges for future research. • Submission deadline: 15. April 2022 • Submission website: click here • Accepted talk proposals will be notified by 1. May 2022 --- Call for Participation in Panathon --- Researchers who want to integrate their program analysis tools into IDEs are welcome to participate in the Panathon session, get cool Swag and win the Best IDE Integration Award with prize money. Before the Panathon session, participants will be given a tutorial on how to use MagpieBridge for integrating program analysis tools into IDEs. During the Panathon session, participants will be given three hours to build an IDE integration of their analysis tools using MagpieBridge. Afterwards, each participant will be given 5 minutes to demonstrate an integrated analysis tool. The demonstration will be evaluated by a panel of judges. A winner will be chosen and receive the Best IDE Integration Award. All participants will get cool Swag as a gift from the organizers. For participation, the idea is to create integration, so the ideal analysis will already work on code and produce some kind of result amenable to displaying in an IDE, such as issues or warnings about specific code constructs or variables. How to participate Participants first need to register their interests by providing some basic information such as the background of the analysis tool that needs to be integrated into IDEs. • Registration link: click here • Registration deadline: 15. April 2022. • Selected participants for the Panathonn session will be notified by 1. May 2022. • Selected participants come to the workshop and build IDE integration for their analysis tools. • A winner will be selected after the demonstration of integrated analysis tools. Guidelines MagpieBridge is designed to be broadly useful, but there are a few guidelines as to what sort of analysis would likely work best. Consult these guidelines to understand whether your analysis would be easy to integrate and whether you could display information as you would like: 1. Ease of use • The MagpieBridge wiki provides documentation and tutorials. • MagpieBridge is available on Maven Central. It can be easily added to projects using common build tools such as Maven and Gradle. 2. Performance and language requirements • MagpieBridge is largely asynchronous with respect to the IDE, so analysis computation time will never block the IDE and results are reported when they are ready. Latency-sensitive features such as hovers can have results computed during analysis, so analysis computation time can be hidden even there. This increases the amount of analysis time that is tolerable compared to on-demand analysis; however, analyses that take excessive amounts of time would not be suitable. • MagpieBridge is written in Java, which makes integrating analyses also written in Java simplest. However, the protocol for communicating with analyses is straightforward, and we will support projects communicating with other languages with JNI bindings when appropriate and also with JSON messaging when that is most convenient. As such, the language in which your analysis is written should not be an issue for taking part in the hackathon. 3. How analysis results can be displayed MagpieBridge largely supports functionality provided by LSP, with a focus on three features given below, but also provides a mechanism to integrate arbitrary HTML pages including forms and JavaScript. The three focus features are the following: • Diagnostics are the kind of error, warning and informational messages commonly supported in IDE’s. MagpieBridge provides an API for returning these kinds of messages, which then get displayed by the IDE using its usual mechanisms. • Hovers are messages that pop up when the mouse hovers over a specific code segment . Note that LSP in most IDE’s integrates its hovers seamlessly with any other hover messages that the IDE generates. • Code lenses are comments injected into program buffers by the IDE, typically accentuated by means of different fonts or colors. These lenses can be linked to actions that interact with the analysis. • Code actions such as quick fixes, displaying a HTML page which presents more complex information. MagpieBridge does not support wholesale changes to the IDE, but, using the HTML integration mechanism, it allows non-trivial views to e.g. configure an analysis or display results. This HTML integration is robust across all IDE’s supported: if an IDE provides such a mechanism (e.g. VS Code), MagpieBridge uses it; otherwise these views would show up in the user’s Web browser. 4. How analysis results can be used MagpieBridge supports the LSP notion of code actions, in which an analysis provides a code range from the program and the text with which it would like to replace that range. This is the primary mechanism, but it is straightforward to extend it to multiple ranges for a single fix. MagpieBridge supports arbitrary HTML documents, which can be used by an analysis to display more complex information than can be easily rendered in a hover. For example, a detailed description of a security warning could be displayed for a brief error message, a data-flow path could be displayed in a graph-like structure. We encourage student participants with limited funding to apply for student volunteers at ECOOP. ---------------------------------------------------------------------------------------- Truffle 2022: Truffle/GraalVM Languages Workshop ---------------------------------------------------------------------------------------- https://2022.ecoop.org/home/truffle-2022 <https://2022.ecoop.org/home/truffle-2022> Deadline: Saturday, 30th of April ---------------------------------------------------------------------------------------- The Truffle/GraalVM Languages Workshop is intended to bring together researchers and developers from both industry and academia that work with the technologies offered by the Truffle language framework and the GraalVM runtime, as well as those working on related approaches pertaining to specializing dynamic language runtimes and tooling. The workshop is meant to foster the exchange of experiences of working with Truffle, provide introductions to Truffle & GraalVM to developers interested in starting their own projects, present specific implementation aspects of existing languages on Truffle, and discuss limitations and future directions of language implementation frameworks in general and Truffle/GraalVM in particular. The format of the workshop will include both presentations of current research and experiences in dynamic language runtime and tool implementations, as well as tutorial-style presentations of specific aspects of using Truffle and GraalVM. We explicitly encourage presentations of work-in-progress as well as work in the early exploration phases to solicit early feedback from and foster discussion with other experienced language developers. Questions? Use the Truffle contact form (https://2022.ecoop.org/contact2/truffle-2022 <https://2022.ecoop.org/contact2/truffle-2022>) Call for Participation: We solicit discussion topic proposals, describing both ongoing and future projects, in the form of extended (1-3 page) abstracts. The discussion topics include but are not limited to the following areas: • Case studies of existing language implementations on Truffle and/or GraalVM. • Comparing alternative language implementation techniques to Truffle. • Performance analysis and/or optimizations for GraalVM and Truffle language implementations. • Tooling support for Truffle languages and GraalVM. • Infrastructure-level optimizations and extensions that can benefit languages built with Truffle. • Research project proposals utilizing Truffle and/or GraalVM. Depending on the number of accepted submissions, we expect topics to cover between 30 minutes and 60 minutes time slots at the workshop. All proposals should be submitted by email to Tim Felgentreff • Deadline for proposal submissions: Apr 30, 2022 (by 11:59 PM AoE) • Notification: May 6, 2022 Although we would like to encourage participants to join the workshop in person, we are planning for a hybrid event due to the continued uncertainties surrounding travel. Please indicate if you plan to attend in person or via video conferencing. ---------------------------------------------------------------------------------------- VORTEX 2022: Workshop on Verification and mOnitoring at Runtime EXecution ---------------------------------------------------------------------------------------- https://2022.ecoop.org/home/vortex-2022 <https://2022.ecoop.org/home/vortex-2022> Deadline: Monday, 18th of April ---------------------------------------------------------------------------------------- Runtime Monitoring (RM) is concerned with the runtime analysis of software and hardware system executions in order to infer properties relating to system behaviour. Example applications include telemetry, log aggregation, threshold alerting, performance monitoring and adherence to correctness properties (more commonly referred to as runtime verification). RM has gained popularity as a solution to ensure software reliability, bridging the gap between formal verification and testing: on the one hand, the notion of event trace abstracts over system executions, thus favoring system agnosticism to better support reuse and interoperability; on the other hand, monitoring a system offers more opportunities for addressing error recovery, self-adaptation, and issues that go beyond software reliability. The goal of VORTEX is to bring together researchers contributing on all aspects of RM covering and possibly integrating both theoretical and practical aspects, with particular focus on hybrid approaches inspired by formal methods, program analysis, testing. Call for Papers Submissions are expected to be in English and to belong to one of the following two categories: • regular paper, page limit 8 in acmart style: unpublished self-contained work • extended abstract, page limit 4 in acmart style: original contribution, not yet fully developed Topics of interest include, but are not limited to, the following ones: • monitor construction and synthesis techniques • program adaptation • monitoring oriented programming • runtime enforcement, fault detection, recovery and repair • combination of static and dynamic analyses • specification formalisms for RM • specification mining • monitoring concurrent/distributed systems • RM for safety and security • RM for the Internet of Things • industrial applications • integrating RM, formal verification, and testing • tool development • instrumentation techniques for RM • surveys on different RM tools, formal frameworks or methodologies • presentations of RM tools Papers must be submitted electronically via EasyChair; the submission deadline is April 18 AoE. Authors should use the official ACM Master article template, which can be obtained from the ACM Proceedings Template pages. Latex users should use the sigconf option, as well as review to produce line numbers for easy reference by the reviewers, as indicated by the following command: \documentclass[sigconf,review]{acmart} Proceedings Depending on the quality and number of submissions, the workshop proceedings will be published in the ACM DL, and authors of selected papers will be invited to contribute with extended versions to be included in a special issue of the Journal of Object Technology (JOT) Questions? Use the VORTEX contact form (https://2022.ecoop.org/contact2/vortex-2022 <https://2022.ecoop.org/contact2/vortex-2022>) ---------------------------------------------------------------------------------------- Carolin Brandt PhD Student // she/her // 🇬🇧 🇩🇪 🇳🇱 TU Delft // EEMCS // Software Engineering Research Group // TestShift Project E c.e.brandt(a)tudelft.nl // T https://twitter.com/laci_noire // W https://carolin-brandt.de/

1 0

The Trunk: Chronology-Core-ul.76.mcz
by commits＠source.squeak.org 31 Mar '22

31 Mar '22

Levente Uzonyi uploaded a new version of Chronology-Core to project The Trunk: http://source.squeak.org/trunk/Chronology-Core-ul.76.mcz ==================== Summary ==================== Name: Chronology-Core-ul.76 Author: ul Time: 31 March 2022, 10:29:59.505362 am UUID: b883c0a9-ae6e-4c05-bea8-2ca5b9c3d464 Ancestors: Chronology-Core-ct.75 - avoid the creation of a Duration in Time class >> #localMicrosecondClock by using #localOffsetSeconds instead of #localOffset and #asSeconds. - fixed the comment of Time class >> #updateTimeZoneCacheAt: =============== Diff against Chronology-Core-ct.75 =============== Item was changed: ----- Method: Time class>>localMicrosecondClock (in category 'clock') ----- localMicrosecondClock "Answer the local microseconds since the Smalltalk epoch (January 1st 1901, the start of the 20th century). The value is derived from the current UTC wallclock time and the image's current notion of time zone." + ^self utcMicrosecondClock + (DateAndTime localOffsetSeconds * 1000000)! - ^self utcMicrosecondClock + (DateAndTime localOffset asSeconds * 1000000)! Item was changed: ----- Method: Time class>>updateTimeZoneCacheAt: (in category 'clock') ----- updateTimeZoneCacheAt: posixUtcMicrosecondClock + "Tell the VM to update its cached time zone value if the POSIX UTC time has reached the value stored in UpdateVMTimeZoneCacheAt. Assume that posixUtcMicrosecondClock is an integer with the current POSIX UTC microsecond clock value. Return true if the cache was updated to indicate that the time zone may have changed." - "Tell the VM to update its cached time zone value if the POSIX UTC time reached the valute stored in UpdateVMTimeZoneCacheAt has been reached. Assume that posixUtcMicrosecondClock is an integer with the current POSIX UTC microsecond clock value. Return true when the cache was updated to indicate that the time zone may have changed." | updateInterval | UpdateVMTimeZoneCacheAt ifNil: [ "Automatic update is disabled." ^false ]. posixUtcMicrosecondClock < UpdateVMTimeZoneCacheAt ifTrue: [ ^false ]. self primitiveUpdateTimeZone ifNil: [ "The primitive failed." ^false ]. + updateInterval := 1800000000. "This could be a preference but 30 minutes works for all upcoming DST change times." - updateInterval := 1800000000. "This could be a preference but 30 minutes matches all upcoming DST change times." UpdateVMTimeZoneCacheAt := posixUtcMicrosecondClock // updateInterval + 1 * updateInterval "Round up posixUtcMicrosecondClock to the next multiple of updateInterval.". ^true!

1 0

The Trunk: Environments-ul.84.mcz
by commits＠source.squeak.org 31 Mar '22

31 Mar '22

Levente Uzonyi uploaded a new version of Environments to project The Trunk: http://source.squeak.org/trunk/Environments-ul.84.mcz ==================== Summary ==================== Name: Environments-ul.84 Author: ul Time: 31 March 2022, 9:44:33.789829 am UUID: 8bddd87e-953c-485a-b76a-991fd4548c87 Ancestors: Environments-ct.83 - use Symboll class >> #lookup: instead of #hasInterned:ifTrue: - just check whether baseName is an existing symbol in Environment >> #classOrTraitNamed: instead of interning it, because if it is not a symbol, it cannot be present as a key in declarations =============== Diff against Environments-ct.83 =============== Item was changed: ----- Method: Environment>>classOrTraitNamed: (in category 'classes and traits') ----- classOrTraitNamed: aString "aString is either a class or trait name or a class or trait name followed by ' class' or 'classTrait' respectively. Answer the class or metaclass it names." | meta baseName | (aString endsWith: ' class') + ifTrue: [ + meta := true. + baseName := aString copyFrom: 1 to: aString size - 6 ] - ifTrue: [meta := true. - baseName := aString copyFrom: 1 to: aString size - 6] ifFalse: [ (aString endsWith: ' classTrait') ifTrue: [ meta := true. + baseName := aString copyFrom: 1 to: aString size - 11 ] - baseName := aString copyFrom: 1 to: aString size - 11] ifFalse: [ meta := false. + baseName := aString ] ]. + ^(Symbol lookup: baseName) ifNotNil: [ :baseNameSymbol | + declarations at: baseNameSymbol ifPresent: [ :global | + global isBehavior ifTrue: [ + meta + ifFalse: [ global ] + ifTrue: [ global classSide ] ] ] ]! - baseName := aString]]. - - ^declarations at: baseName asSymbol ifPresent: - [ :global | - global isBehavior ifTrue: - [ meta - ifFalse: [ global ] - ifTrue: [ global classSide ]]]! Item was changed: ----- Method: Environment>>hasClassNamed: (in category 'classes and traits') ----- hasClassNamed: aString + + ^(Symbol lookup: aString) + ifNil: [ false ] + ifNotNil: [:symbol | + (declarations at: symbol ifAbsent: [nil]) + isKindOf: Class]! - Symbol hasInterned: aString ifTrue: - [:symbol | - ^ (declarations at: symbol ifAbsent: [nil]) - isKindOf: Class]. - ^ false.!

1 0

The Trunk: Tools-ul.1145.mcz
by commits＠source.squeak.org 31 Mar '22

31 Mar '22

Levente Uzonyi uploaded a new version of Tools to project The Trunk: http://source.squeak.org/trunk/Tools-ul.1145.mcz ==================== Summary ==================== Name: Tools-ul.1145 Author: ul Time: 30 March 2022, 5:28:44.378745 pm UUID: 1012c26d-a7d8-4985-a836-a050c950331a Ancestors: Tools-mt.1144 - fix MessageSet >> #sortByDate by keeping messageList an OrderedCollection - use Symbol class >> #lookUp: instead of #hasInterned:ifTrue: =============== Diff against Tools-mt.1144 =============== Item was changed: ----- Method: MessageNames>>computeSelectorListFrom: (in category 'search') ----- computeSelectorListFrom: searchString "Compute selector list from search string. The searchString is a list of expressions separated by ;. Each expression is matched individually. An expression can be a simple string (same as *expression*), a string with double quotes (exact match) or a match expression (see String >> #match:)." ^ (Array streamContents: [ :stream | (searchString findBetweenSubStrs: ';') do: [ :selPat | (selPat first = $" and: [ selPat last = $" and: [ selPat size > 2 ] ]) ifTrue: [ + (Symbol lookup: (selPat copyFrom: 2 to: selPat size - 1)) + ifNotNil: [ :sym | stream nextPut: sym ] ] - Symbol - hasInterned: (selPat copyFrom: 2 to: selPat size - 1) - ifTrue: [ :sym | stream nextPut: sym ] ] ifFalse: [ | raw n m | n := selPat occurrencesOf: $*. m := selPat occurrencesOf: $#. raw := ((n > 0 or: [ m > 0 ]) and: [ selPat size > (n + m) ]) ifTrue: [ Symbol selectorsMatching: selPat ] ifFalse: [ Symbol selectorsContaining: selPat ]. stream nextPutAll: raw ] ] ]) sort: [ :x :y | x caseInsensitiveLessOrEqual: y ]! Item was changed: ----- Method: MessageSet>>filterToImplementorsOf (in category 'filtering') ----- filterToImplementorsOf "Filter the receiver's list down to only those items with a given selector" | aFragment inputWithBlanksTrimmed | aFragment := self request: 'type selector:' initialAnswer: ''. aFragment isEmptyOrNil ifTrue: [^ self]. inputWithBlanksTrimmed := aFragment withBlanksTrimmed. + (Symbol lookup: inputWithBlanksTrimmed) ifNotNil: - Symbol hasInterned: inputWithBlanksTrimmed ifTrue: [:aSymbol | self filterFrom: [:aClass :aSelector | aSelector == aSymbol]]! Item was changed: ----- Method: MessageSet>>filterToNotImplementorsOf (in category 'filtering') ----- filterToNotImplementorsOf "Filter the receiver's list down to only those items whose selector is NOT one solicited from the user." | aFragment inputWithBlanksTrimmed | aFragment := self request: 'type selector: ' initialAnswer: ''. aFragment isEmptyOrNil ifTrue: [^ self]. inputWithBlanksTrimmed := aFragment withBlanksTrimmed. + (Symbol lookup: inputWithBlanksTrimmed) ifNotNil: - Symbol hasInterned: inputWithBlanksTrimmed ifTrue: [:aSymbol | self filterFrom: [:aClass :aSelector | aSelector ~~ aSymbol]]! Item was changed: ----- Method: MessageSet>>filterToNotSendersOf (in category 'filtering') ----- filterToNotSendersOf "Filter the receiver's list down to only those items which do not send a given selector" | aFragment inputWithBlanksTrimmed | aFragment := self request: 'type selector:' initialAnswer: ''. aFragment isEmptyOrNil ifTrue: [^ self]. inputWithBlanksTrimmed := aFragment withBlanksTrimmed. + (Symbol lookup: inputWithBlanksTrimmed) ifNotNil: - Symbol hasInterned: inputWithBlanksTrimmed ifTrue: [:aSymbol | self filterFrom: [:aClass :aSelector | | aMethod | (aMethod := aClass compiledMethodAt: aSelector) isNil or: [(aMethod hasLiteral: aSymbol) not]]]! Item was changed: ----- Method: MessageSet>>filterToSendersOf (in category 'filtering') ----- filterToSendersOf "Filter the receiver's list down to only those items which send a given selector" | aFragment inputWithBlanksTrimmed | aFragment := self request: 'type selector:' initialAnswer: ''. aFragment isEmptyOrNil ifTrue: [^ self]. inputWithBlanksTrimmed := aFragment withBlanksTrimmed. + (Symbol lookup: inputWithBlanksTrimmed) ifNotNil: - Symbol hasInterned: inputWithBlanksTrimmed ifTrue: [:aSymbol | self filterFrom: [:aClass :aSelector | | aMethod | (aMethod := aClass compiledMethodAt: aSelector) notNil and: [aMethod hasLiteral: aSymbol]]] ! Item was changed: ----- Method: MessageSet>>sortByDate (in category 'message list') ----- sortByDate "Sort the message-list by date of time-stamp" + | associations | + associations := messageList collect: - | assocs inOrder | - assocs := messageList collect: [:aRef | | aDate aCompiledMethod | aDate := aRef methodSymbol == #Comment ifTrue: [aRef actualClass organization dateCommentLastSubmitted] ifFalse: [aCompiledMethod := aRef actualClass compiledMethodAt: aRef methodSymbol ifAbsent: [nil]. aCompiledMethod ifNotNil: [aCompiledMethod dateMethodLastSubmitted]]. aRef -> (aDate ifNil: [Date fromString: '01/01/1996'])]. "The dawn of Squeak history" + messageList := associations + sort: #value asSortFunction; + replace: [ :association | association key ]; + yourself. - inOrder := assocs asArray sort: [:a :b | a value < b value]. - - messageList := inOrder collect: [:assoc | assoc key]. self changed: #messageList!

1 0

The Trunk: Kernel-ul.1454.mcz
by commits＠source.squeak.org 31 Mar '22

31 Mar '22

Levente Uzonyi uploaded a new version of Kernel to project The Trunk: http://source.squeak.org/trunk/Kernel-ul.1454.mcz ==================== Summary ==================== Name: Kernel-ul.1454 Author: ul Time: 31 March 2022, 9:40:35.561194 am UUID: 77c53e53-4088-4309-9dcf-a2ea77469e41 Ancestors: Kernel-ct.1453 - do not try to compact immutable MethodDictionaries in #compactAllInstances - update the tally first when modifying a MethodDictionary, so that immutable MethodDictionaries raise an error before their non-immutable array variable is updated - do not send #rounded to #sign in Float >> #rounded. #sign is already rounded - use Symboll class >> #lookup: instead of #hasInterned:ifTrue: - use #anySatisfy: instead of reinventing it in Object >> #inheritsFromAnyIn:. Also, use #classNamed: to look up a class in the same method. =============== Diff against Kernel-ct.1453 =============== Item was changed: ----- Method: Behavior>>whichClassDefinesClassVar: (in category 'queries') ----- whichClassDefinesClassVar: aString + + ^(Symbol lookup: aString) ifNotNil: [ :aSymbol | - Symbol hasInterned: aString ifTrue: [ :aSymbol | ^self whichSuperclassSatisfies: [:aClass | + aClass classVarNames anySatisfy: [:each | each = aSymbol]]]! - aClass classVarNames anySatisfy: [:each | each = aSymbol]]]. - ^nil! Item was changed: ----- Method: Float>>rounded (in category 'truncation and round off') ----- rounded "Answer the integer nearest the receiver. Implementation note: super would not handle tricky inexact arithmetic" "self assert: 5000000000000001.0 rounded = 5000000000000001" self fractionPart abs < 0.5 ifTrue: [^self truncated] + ifFalse: [^self truncated + self sign]! - ifFalse: [^self truncated + self sign rounded]! Item was changed: ----- Method: MethodDictionary class>>compactAllInstances (in category 'initialize-release') ----- compactAllInstances | instancesToExchange newInstances | instancesToExchange := Array streamContents: [ :oldStream | newInstances := Array streamContents: [ :newStream | self allInstances do: [ :each | + each isReadOnlyObject ifFalse: [ + | newInstance | + newInstance := each compactWithoutBecome. + newInstance capacity = each capacity + ifTrue: [ each copyFrom: newInstance ] + ifFalse: [ + oldStream nextPut: each. + newStream nextPut: newInstance ] ] ] ] ]. - | newInstance | - newInstance := each compactWithoutBecome. - newInstance capacity = each capacity - ifTrue: [ each copyFrom: newInstance ] - ifFalse: [ - oldStream nextPut: each. - newStream nextPut: newInstance ] ] ] ]. instancesToExchange elementsForwardIdentityTo: newInstances! Item was changed: ----- Method: MethodDictionary>>removeDangerouslyKey:ifAbsent: (in category 'private') ----- removeDangerouslyKey: key ifAbsent: aBlock "This is not really dangerous. But if normal removal were done WHILE a MethodDict were being used, the system might crash. So instead we make a copy, then do this operation (which is NOT dangerous in a copy that is not being used), and then use the copy after the removal." | index element | index := self scanFor: key. (element := array at: index) ifNil: [ ^aBlock value ]. + tally := tally - 1. "Update tally first, so that read-only hashed collections raise an error before modifying array." array at: index put: nil. self basicAt: index put: nil. - tally := tally - 1. self fixCollisionsFrom: index. ^element! Item was changed: ----- Method: Object>>inheritsFromAnyIn: (in category 'class membership') ----- inheritsFromAnyIn: aList "Answer whether the receiver inherits from any class represented by any element in the list. The elements of the list can be classes, class name symbols, or strings representing possible class names. This allows speculative membership tests to be made even when some of the classes may not be known to the current image, and even when their names are not interned symbols." + ^aList anySatisfy: [ :element | + (Smalltalk classNamed: element asString) + ifNil: [ false ] + ifNotNil: [ :class | + (class isKindOf: Class) + and: [ self isKindOf: class ] ] ] - aList do: - [:elem | Symbol hasInterned: elem asString ifTrue: - [:elemSymbol | - | aClass | - (((aClass := Smalltalk at: elemSymbol ifAbsent: [nil]) isKindOf: Class) - and: [self isKindOf: aClass]) - ifTrue: - [^ true]]]. - ^ false - " {3. true. 'olive'} do: [:token | {{#Number. #Boolean}. {Number. Boolean }. {'Number'. 'Boolean'}} do: [:list | Transcript cr; show: token asString, ' list element provided as a ', list first class name, ' - ', (token inheritsFromAnyIn: list) asString]] "!

1 0

The Trunk: System-mt.1325.mcz
by commits＠source.squeak.org 31 Mar '22

31 Mar '22

Marcel Taeumel uploaded a new version of System to project The Trunk: http://source.squeak.org/trunk/System-mt.1325.mcz ==================== Summary ==================== Name: System-mt.1325 Author: mt Time: 14 March 2022, 4:34:33.986786 pm UUID: 0499f29c-88b0-dc40-8c69-a97e5ffe4321 Ancestors: System-mt.1324 Remove manual line breaks in dialog texts. Keep double-breaks (i.e., '\\' or ' ') as visual gap. Complements Morphic-mt.1935. =============== Diff against System-mt.1324 =============== Item was changed: ----- Method: ChangeSet>>fileOut (in category 'fileIn/Out') ----- fileOut "File out the receiver, to a file whose name is a function of the change-set name and either of the date & time or chosen to have a unique numeric tag, depending on the preference 'changeSetVersionNumbers'" | slips nameToUse | self checkForConversionMethods. ChangeSet promptForDefaultChangeSetDirectoryIfNecessary. nameToUse := Preferences changeSetVersionNumbers ifTrue: [self defaultChangeSetDirectory nextNameFor: self name extension: FileStream cs] ifFalse: [self name , FileDirectory dot , Utilities dateTimeSuffix, FileDirectory dot , FileStream cs]. Cursor write showWhile: [ | internalStream | internalStream := WriteStream on: (String new: 10000). internalStream header; timeStamp. self fileOutPreambleOn: internalStream. self fileOutOn: internalStream. self fileOutPostscriptOn: internalStream. internalStream trailer. FileStream writeSourceCodeFrom: internalStream baseName: (nameToUse copyFrom: 1 to: nameToUse size - 3) isSt: false useHtml: false. ]. Preferences checkForSlips ifFalse: [^ self]. slips := self checkForSlips. (slips size > 0 + and: [Project uiManager confirm: 'Changeset was filed out. Still, methods in this file-out have halts or references to the Transcript or other ''slips'' in them. Would you like to browse them?' translated asTextFromHtml + title: 'Browse Slips?' translated]) - and: [UIManager default confirm: 'Changeset was filed out. Still, methods in this fileOut have halts\or references to the Transcript or other ''slips'' in them.\Would you like to browse them?' withCRs - title: 'Browse Slips?']) ifTrue: [self systemNavigation browseMessageList: slips name: 'Possible slips in ' , name]! Item was changed: ----- Method: DeepCopier>>warnIverNotCopiedIn:sel: (in category 'like fullCopy') ----- warnIverNotCopiedIn: aClass sel: sel "Warn the user to update veryDeepCopyWith: or veryDeepInner:" + self inform: ('An instance variable was added to to class {1} and it is not copied in the method {2}. Please rewrite it to handle all instance variables. See DeepCopier class comment.' translated format: { aClass name . sel}) asTextFromHtml. - self inform: ('An instance variable was added to to class ', aClass name, ',\and it is not copied in the method ', sel, '.\Please rewrite it to handle all instance variables.\See DeepCopier class comment.') withCRs. ToolSet browse: aClass selector: sel! Item was changed: ----- Method: Preferences class>>initializeParameters (in category 'parameters') ----- initializeParameters "Preferences initializeParameters" Parameters := IdentityDictionary new. + Parameters at: #maxBalloonHelpLineLength put: 45.! - Parameters at: #maxBalloonHelpLineLength put: 28.! Item was changed: ----- Method: Preferences class>>maxBalloonHelpLineLength (in category 'prefs - misc') ----- maxBalloonHelpLineLength + ^ Parameters at: #maxBalloonHelpLineLength ifAbsent: [45]! - ^ Parameters at: #maxBalloonHelpLineLength! Item was added: + ----- Method: Preferences class>>maxBalloonHelpLineLength: (in category 'prefs - misc') ----- + maxBalloonHelpLineLength: numChars + + Parameters + at: #maxBalloonHelpLineLength + put: numChars.! Item was changed: ----- Method: SmalltalkImage>>openSourcesAndChanges:forImage: (in category 'image, changes names') ----- openSourcesAndChanges: changesName forImage: imageName "Open the changes and sources files and install them in SourceFiles. Inform the user of problems regarding write permissions or CR/CRLF mixups." "Note: SourcesName and imageName are full paths; changesName is a local name." | sources changes msg wmsg | + msg := 'Squeak cannot locate {1}. - msg := 'Squeak cannot locate &fileRef. + Please check that the file is named properly and is in the same directory as this image.'. + wmsg := 'Squeak cannot write to {1}. - Please check that the file is named properly and is in the - same directory as this image.'. - wmsg := 'Squeak cannot write to &fileRef. Please check that you have write permission for this file. You won''t be able to save this image correctly until you fix this.'. sources := Smalltalk openSources. sources ifNotNil: [sources setConverterForCode]. changes := Smalltalk openChanges: changesName forImage: imageName. changes ifNotNil: [changes setConverterForCode]. ((sources == nil or: [sources atEnd]) and: [Preferences valueOfFlag: #warnIfNoSourcesFile]) ifTrue: [Smalltalk platformName = 'Mac OS' ifTrue: [msg := msg , ' Make sure the sources file is not an Alias.']. + self inform: (msg format: { 'the sources file named ' , self sourcesName })]. - self inform: (msg copyReplaceAll: '&fileRef' with: 'the sources file named ' , self sourcesName)]. (changes == nil and: [Preferences valueOfFlag: #warnIfNoChangesFile]) + ifTrue: [self inform: (msg format: { 'the changes file named ' , changesName })]. - ifTrue: [self inform: (msg copyReplaceAll: '&fileRef' with: 'the changes file named ' , changesName)]. ((Preferences valueOfFlag: #warnIfNoChangesFile) and: [changes notNil]) ifTrue: [changes isReadOnly + ifTrue: [self inform: (wmsg format: { 'the changes file named ' , changesName })]. - ifTrue: [self inform: (wmsg copyReplaceAll: '&fileRef' with: 'the changes file named ' , changesName)]. ((changes next: 200) includesSubstring: String crlf) + ifTrue: [self inform: ('The changes file named {1} has been injured by an unpacking utility. Line endings were changed from Cr to CrLf. Please set the preferences in your decompressing program to + do not convert text files and unpack the system again.' translated format: { changesName }) asTextFromHtml]]. - ifTrue: [self inform: 'The changes file named ' , changesName , ' - has been injured by an unpacking utility. Crs were changed to CrLfs. - Please set the preferences in your decompressing program to - "do not convert text files" and unpack the system again.']]. SourceFiles := Array with: sources with: changes! Item was changed: ----- Method: SystemNavigation>>confirmAndRemoveClass: (in category 'ui') ----- confirmAndRemoveClass: aClass | allCalls subclasses hasForeignCalls className numberOfMethods allChoices yourChoice remove browse| allCalls := self allCallsOnClass: aClass. subclasses := aClass subclasses. hasForeignCalls := allCalls anySatisfy: [:ea | ea actualClass ~= aClass]. className := aClass name. numberOfMethods := aClass methodDict size + aClass class methodDict size. allChoices := OrderedDictionary new. allChoices at: 'Yes, remove it' translated put: [remove := true. browse := false]. (allCalls notEmpty or: [subclasses notEmpty]) ifTrue: [ allChoices at: 'Yes, remove it, then browse references' translated put: [remove := true. browse := true]. allChoices at: 'No, don''t remove it, but browse references' translated put: [remove := false. browse := true]]. allChoices at: 'No, don''t remove it' translated put: [remove := false. browse := false]. yourChoice := Project uiManager chooseFromLabeledValues: allChoices + title: ('Are you sure that you want to remove the class\\ {1}\\and all its {2} methods? Maybe save your image before doing this.{3}{4}' translated withCRs asText format: { - title: ('Are you sure that you want to remove\the class\\ {1}\\and all its {2} methods? Maybe save\your image before doing this.{3}{4}' translated withCRs asText format: { className asText allBold. numberOfMethods asString asText allBold. hasForeignCalls ifFalse: [''] ifTrue: [ '\\(There are {1} references to this class.)' translated withCRs asText format: { allCalls size asString asText allBold }]. subclasses ifEmpty: [''] ifNotEmpty: [ + '\\(There are {1} subclasses, whose superclass must be updated manually after this.)' translated withCRs asText - '\\(There are {1} subclasses, whose superclass\must be updated manually after this.)' translated withCRs asText format: { subclasses size asString asText allBold }] }). remove := browse := false. "Defaults" yourChoice value. "Supports nil because of defaults above." remove ifTrue: [ aClass removeFromSystem]. browse ifTrue: [ hasForeignCalls ifTrue: [ self browseAllCallsOnClass: aClass]. subclasses ifNotEmpty: [ self browseMessageList: (subclasses collect: [:subclass | MethodReference class: subclass selector: #Definition environment: self environment]) name: ('Subclasses of {1}' translated format: {className}) autoSelect: className]]. ^ remove! Item was changed: ----- Method: SystemNavigation>>confirmAndRemoveMessageCategory:class: (in category 'ui') ----- confirmAndRemoveMessageCategory: aCategory class: aClass | categoryList | categoryList := aClass organization listAtCategoryNamed: aCategory. (categoryList isEmpty + or: [Project uiManager confirm: ('Are you sure you want to remove the message category\\ {1}\ from {2}\\and all its {3} methods? Maybe save your image before doing this.' translated withCRs asText format: { - or: [Project uiManager confirm: ('Are you sure you want to remove\the message category\\ {1}\ from {2}\\and all its {3} methods? Maybe save\your image before doing this.' translated withCRs asText format: { aCategory asText allBold. aClass name. categoryList size asString asText allBold }) title: 'Remove Message Category' translated]) ifFalse: [^ false]. aClass removeCategory: aCategory. ^ true! Item was changed: ----- Method: SystemNavigation>>confirmAndRemoveSelector:class: (in category 'ui') ----- confirmAndRemoveSelector: selector class: aClass | method allCalls remove browse | method := MethodReference class: aClass selector: selector environment: self environment. allCalls := self allCallsOn: selector. (allCalls anySatisfy: [:ea | ea ~= method]) ifFalse: [remove := true. browse := false] ifTrue: [ | allChoices yourChoice | allChoices := OrderedDictionary new. allChoices at: 'Yes, remove it' translated put: [remove := true. browse := false]. allChoices at: 'Yes, remove it, then browse senders' translated put: [remove := true. browse := true]. allChoices at: 'No, don''t remove it, but browse senders' translated put: [remove := false. browse := true]. allChoices at: 'No, don''t remove it' translated put: [remove := false. browse := false]. yourChoice := Project uiManager chooseFromLabeledValues: allChoices + title: ('Are you sure that you want to remove the message {1} from {2}?\\The message has {3} senders.' translated withCRs asText format: { - title: ('Are you sure that you want to remove the message\{1} from {2}?\\The message has {3} senders.' translated withCRs asText format: { selector asText allBold. aClass name asText allBold. allCalls size asString asText allBold }). remove := browse := false. "Defaults" yourChoice value. "Supports nil because of defaults above."]. remove ifTrue: [ aClass removeSelector: selector]. browse ifTrue: [ self headingAndAutoselectForLiteral: selector do: [ :label :autoSelect | self browseMessageList: allCalls name: label autoSelect: autoSelect]]. ^ remove! Item was changed: ----- Method: SystemNavigation>>confirmAndRemoveSystemCategory: (in category 'ui') ----- confirmAndRemoveSystemCategory: aCategory | systemOrganizer categoryList | systemOrganizer := self environment organization. categoryList := systemOrganizer listAtCategoryNamed: aCategory. (categoryList isEmpty or: [Project uiManager + confirm: ('Are you sure you want to remove the system category\\ {1}\\and all its {2} classes? Maybe save your image before doing this.' translated withCRs asText - confirm: ('Are you sure you want to remove\the system category\\ {1}\\and all its {2} classes? Maybe save\your image before doing this.' translated withCRs asText format: { aCategory asText allBold. categoryList size asString asText allBold}) title: 'Remove System Category' translated]) ifFalse: [^ false]. systemOrganizer removeSystemCategory: aCategory. ^ true! Item was changed: ----- Method: SystemVersion>>description (in category 'printing') ----- description + self isAlpha ifTrue: [^ 'ALPHA. New features which are not stable yet may come in with each update. Also, existing features might not work reliably due to updates and related changes.' translated withCRs]. - self isAlpha ifTrue: [^ 'ALPHA. New features which are not stable yet may come in\with each update. Also, existing features might not work\reliably due to updates and related changes.' translated withCRs]. + (self isFeatureFreeze and: [self isCodeFreeze not]) ifTrue: [^ 'FEATURE FREEZE. A new release is being prepared. There will be only bugfixes, but no new features.' translated withCRs]. - (self isFeatureFreeze and: [self isCodeFreeze not]) ifTrue: [^ 'FEATURE FREEZE. A new release is being prepared.\There will be only bugfixes, but no new features.' translated withCRs]. + self isCodeFreeze ifTrue: [^ 'RELEASE CANDIDATE. The new release is almost ready. There will be only bugfixes, if any.' translated withCRs]. - self isCodeFreeze ifTrue: [^ 'RELEASE CANDIDATE. The new release is almost ready.\There will be only bugfixes, if any.' translated withCRs]. self isRelease ifTrue: [^ ''].!

4 4

Election!
by Ron Teitelbaum 30 Mar '22

30 Mar '22

Hi All, There is only 15 or so days left to announce that you are running for the Squeak Borad. First thank you everyone that has served. It is a great benefit to our community to have such great people volenteer their time to help! This is also a great way for you to support your Squeak community! Right now we have only 4 people running for 7 board seats. And one of those doens't want to be elected! It's time to step up! If you are going to run please announce soon. Also if you know someone that you think should run, please reach out to them and ask them to run. Some people will not run without encouragement. Thank you! Ron Teitelbaum

4 5

The Trunk: Collections-ul.1002.mcz
by commits＠source.squeak.org 30 Mar '22

30 Mar '22

Levente Uzonyi uploaded a new version of Collections to project The Trunk: http://source.squeak.org/trunk/Collections-ul.1002.mcz ==================== Summary ==================== Name: Collections-ul.1002 Author: ul Time: 30 March 2022, 5:32:03.565112 pm UUID: 7d079f04-98dd-49ea-a0d0-6aaff26ee090 Ancestors: Collections-ul.1001 - do not try to rehash and compact immutable hashed collections in #rehashAllInstances and #compactAllInstances, respectively =============== Diff against Collections-ul.1001 =============== Item was changed: ----- Method: HashedCollection class>>compactAllInstances (in category 'initialize-release') ----- compactAllInstances + "Do not use #allInstancesDo: because #compact may create new instances. Ignore immutable instances." - "Do not use #allInstancesDo: because #compact may create new instances." + self allInstances do: [ :each | + each isReadOnlyObject ifFalse: [ each compact ] ]! - self allInstances do: [ :each | each compact ]! Item was changed: ----- Method: HashedCollection class>>rehashAllInstances (in category 'initialize-release') ----- rehashAllInstances + "Do not use #allInstancesDo: because #rehash may create new instances. Ignore immutable instances." - "Do not use #allInstancesDo: because #rehash may create new instances." + self allInstances do: [ :each | + each isReadOnlyObject ifFalse: [ + each rehash ] ]! - self allInstances do: [ :each | each rehash ]!

1 0

The Trunk: Morphic-mt.1954.mcz
by commits＠source.squeak.org 30 Mar '22

30 Mar '22

Marcel Taeumel uploaded a new version of Morphic to project The Trunk: http://source.squeak.org/trunk/Morphic-mt.1954.mcz ==================== Summary ==================== Name: Morphic-mt.1954 Author: mt Time: 30 March 2022, 2:07:43.932263 pm UUID: bfd62696-7e09-d94a-b437-1ec22c999508 Ancestors: Morphic-mt.1953 Makes the preference #disableDeferredUpdates: functional by clearing the world's current canvas. See #assuredCanvas. =============== Diff against Morphic-mt.1953 =============== Item was changed: ----- Method: WorldState class>>disableDeferredUpdates: (in category 'accessing') ----- disableDeferredUpdates: aBoolean "If the argument is true, disable deferred screen updating." "Details: When deferred updating is used, Morphic performs double-buffered screen updates by telling the VM to de-couple the Display from the hardware display buffer, drawing directly into the Display, and then forcing the changed regions of the Display to be copied to the screen. This saves both time (an extra BitBlt is avoided) and space (an extra display buffer is avoided). However, on platforms on which the Display points directly to the hardware screen buffer, deferred updating can't be used (you'd see ugly flashing as the layers of the drawing were assembled). In this case, the drawing is composited into an offscreen FormCanvas and then copied to the hardware display buffer." DisableDeferredUpdates := aBoolean. + Project current isMorphic ifTrue: [Project currentWorld canvas: nil].! - !

1 0

← Newer
1
...
7
8
9
10
11
12
13
...
31
Older →

Jump to page: