- Pharo-users - lists.pharo.org

ANN: More syntax highlights for Pharo code :)
by Esteban Lorenzano Nov. 24, 2025

Nov. 24, 2025

Hi, Last week I was with insomnia and playing with IAs and I managed to create some nice styles (based on existing ones) you can use to improve how your Pharo code lookÂ :) Metacello new Â Â repository: 'gtithub://estebanlm/themes'; Â Â baseline: 'Themes'; Â Â load: 'HighlightStyles' ... then you can have some nice styles (other than the current ones), both for dark and light themes :) Enjoy, Esteban

1 0

Artifacts and Smalltalk code
by Benoit St-Jean Nov. 20, 2025

Nov. 20, 2025

Hello everyone, Can anyone point me to any document and/or blog post regarding best practices (and HOWTO) in handling project artifacts in a Pharo project? For example, how do you handle Smalltalk code AND other files, SQL code, documentation, class diagrams, intilization scripts, user data files, etc? The Smalltalk code itself, in my case, has to go along with all other files.Â Do you handle "everything not Smalltalk" manually with git or there is another way ?Â How do you guys do it in your projects? tia

6 5

Pharo News of the Week 46/2025
by Marcus Denker Nov. 20, 2025

Nov. 20, 2025

# Pharo News of the Week 46/2025 - [Blog Post] What if Java had Symmetric Converter Methods on Collection? https://donraab.medium.com/what-if-java-had-symmetric-converter-methods-on-… - [Research] 221 research papers in the PHARO Collection: https://inria.hal.science/PHARO. You can add your papers: https://pharo.org/web/PharoPublications - [ANN][TALK] Wednesday, Nov 26: Norbert Hartl - Soil: a database for fun and profit https://www.meetup.com/ukstug/events/311265917/ News wanted! You can add your news to this list (that is, next week) using this form: https://tinyurl.com/4c89buy4 # The week on the Pharo Issue Tracker # Fixes - fix: make OnlineSourceDebugInfo>>#readVariableNamed:fromContext: workâ¦ #18719 https://github.com/pharo-project/pharo/pull/18719 - Fix #testUndeclared #18893 https://github.com/pharo-project/pharo/pull/18893 - Fix large array compilation #18825 https://github.com/pharo-project/pharo/pull/18825 # Tools - Using DebugInfo #1259 https://github.com/pharo-spec/NewTools/pull/1259 - Migrate Epicea browsers to NewTools #1282 https://github.com/pharo-spec/NewTools/pull/1282 - Remove Epicea browsers from Pharo #18896 https://github.com/pharo-project/pharo/pull/18896 - Add back sha in about #1281 https://github.com/pharo-spec/NewTools/pull/1281 - Bring back Select package as right dependency feature #1279 https://github.com/pharo-spec/NewTools/pull/1279 - Add a defaultAction to InformativeNotification #1278 https://github.com/pharo-spec/NewTools/pull/1278 - Inspecting a string should display the ' ' (Fix #814) #1277 https://github.com/pharo-spec/NewTools/pull/1277 - Fixes: Message browser panes cannot be removed with Cmd x anymore #18872 https://github.com/pharo-project/pharo/pull/18872 # Refactoring - Better comment and names for refactoring #18891 https://github.com/pharo-project/pharo/pull/18891 - Fix issue #18507: Scope issue breaks refactoring (retry) + new hook instantiateRefactoring #18890 https://github.com/pharo-project/pharo/pull/18890 - Tests references #18871 https://github.com/pharo-project/pharo/pull/18871 - Adding tests and comments for references: OCNodes #18863 https://github.com/pharo-project/pharo/pull/18863 - Feat/exposing temp def move #18861 https://github.com/pharo-project/pharo/pull/18861 # Spec - Do not use StPharoApplication in Spec #1842 https://github.com/pharo-spec/Spec/pull/1842 - fixes on SpCodePresenter>>styleScheme and revert a rename #1841 https://github.com/pharo-spec/Spec/pull/1841 - add selectedRowPresenter to tables #1840 https://github.com/pharo-spec/Spec/pull/1840 # VM - A new file plugin #1024 https://github.com/pharo-project/pharo-vm/pull/1024 - Only scan the class table if become: was performed to an active class object #1023 https://github.com/pharo-project/pharo-vm/pull/1023 # Git / Iceberg - Introduce IceTipRepositoryStatusModel to avoid multiple commit lookups #1918 https://github.com/pharo-vcs/iceberg/pull/1918 - 1686-SSH-Key-pair-should-not-ask-user-it-should-use-the-user-from-the-URL #1687 https://github.com/pharo-vcs/iceberg/pull/1687 - MetacelloPharoPlatform>>#withMetacelloLoadSessionDo: is now in Pharo #1990 https://github.com/pharo-vcs/iceberg/pull/1990 - Fixing the fetchAllRemotes DNU #1989 https://github.com/pharo-vcs/iceberg/pull/1989 - Litlle fix for inform call #1986 https://github.com/pharo-vcs/iceberg/pull/1986 - Miss select a folder to clone user input validation #1985 https://github.com/pharo-vcs/iceberg/pull/1985 # inform: cleanup - Less meta prog for classes that are loaded. #18889 https://github.com/pharo-project/pharo/pull/18889 - Less inform: #18888 https://github.com/pharo-project/pharo/pull/18888 - Reduce dependencies to UIManager #18844 https://github.com/pharo-project/pharo/pull/18844 # Cleanup - 18813-Remove-Binary-representation-in-MCZ-files #18815 https://github.com/pharo-project/pharo/pull/18815 # Command Line - Allow to fetch flags and positionals not declared in the last subcommand #18875 https://github.com/pharo-project/pharo/pull/18875 # Packaging / Boostrap / Package loading - Fix multiple dependencies in DebugPoints #18892 https://github.com/pharo-project/pharo/pull/18892 - Clean Keymapping baseline #18887 https://github.com/pharo-project/pharo/pull/18887 - Fix kernel system dependency test #18886 https://github.com/pharo-project/pharo/pull/18886 - Fix minimal image tests #18885 https://github.com/pharo-project/pharo/pull/18885 - Clean a few dependencies of the kernel #18884 https://github.com/pharo-project/pharo/pull/18884 - Extract ParseTreeRewriter to its own package #18883 https://github.com/pharo-project/pharo/pull/18883 - Fix TFFI reset and fix load order #18882 https://github.com/pharo-project/pharo/pull/18882 - Revert loading order of TFFI #18880 https://github.com/pharo-project/pharo/pull/18880 - Start SessionManager with a session #18870 https://github.com/pharo-project/pharo/pull/18870 - Fix startup preferences loading #18867 https://github.com/pharo-project/pharo/pull/18867 - Clean traits in the bootstrap #18842 https://github.com/pharo-project/pharo/pull/18842

1 0

CfP: SLE 2026 - 19th ACM SIGPLAN International Conference on Software Language Engineering
by Andrei Chis Nov. 20, 2025

Nov. 20, 2025

19th ACM SIGPLAN International Conference on Software Language Engineering (SLE 2026) 2 - 3 July 2026 Rennes, France https://conf.researchr.org/home/sle-2026 https://www.sleconf.org/2026/ ------------------------------------------------------------------------ We are pleased to invite you to submit papers to the 19th ACM SIGPLAN International Conference on Software Language Engineering (SLE) which is devoted to the principles of software languages: their design, their implementation, and their evolution. The SLE 2026 conference will be co-located with STAF 2026 and hosted in Rennes, France, on 2 - 3 July 2026. --------------------------- Important Dates --------------------------- * Abstract submission (all tracks): Friday 27 February 2026 * Paper submission (all tracks): Friday 6 March 2026 * Paper notification (all tracks): Monday 20 April 2026 * Conference: Thursday 2 - Friday 3 July 2026 (co-located with STAF) All dates are Anywhere on Earth. --------------------------- Topics of Interest --------------------------- SLE covers software language engineering in general, rather than engineering a specific software language. Topics of interest include, but are not limited to: *Software Language Design and Implementation - Approaches to and methods for language design - Static semantics (e.g., design rules, well-formedness constraints) - Techniques for specifying behavioral/executable semantics - Generative approaches (incl. code synthesis, compilation) - Meta-languages, meta-tools, language workbenches - AI-assisted language design and optimisation * Software Language Quality - Verification and formal methods for languages - Testing techniques for languages - Simulation techniques for languages - Model-based testing - AI-assisted validation * Software Language Integration and Composition - Coordination of heterogeneous languages and tools - Mappings between languages (incl. transformation languages) - Traceability between languages - Deployment of languages to different platforms - (AI-assisted) Language refactorings * Software Language Maintenance - Software language reuse - Language evolution - Language families and variability, language and software product lines * Domain-specific approaches for any aspects of SLE (design, implementation, validation, maintenance) * Empirical evaluation and experience reports of language engineering tools - User studies evaluating usability - Performance benchmarks - Industrial applications * Synergies between Language Engineering and emerging/promising research areas - Generative AI in language engineering (e.g., AI-based language modelling, AI-driven code generation tools) - Language engineering for AI. AI and ML language engineering (e.g., ML compiler testing, code classification, DSLs for AI processes and tasksâ¦) - Quantum language engineering (e.g., language design for quantum machines) - Language engineering for physical systems (e.g., CPS, IoT, digital twins) - Socio-technical systems and language engineering (e.g., language evolution to adapt to social requirements) --------------------------- Types of Submissions --------------------------- SLE accepts the following types of papers: * Research papers: These are âtraditionalâ papers detailing research contributions to SLE. Papers may range from 6 to 12 pages in length and may optionally include 2 further pages of bibliography/appendices. Papers will be reviewed with an understanding that some results do not need 12 full pages and may be fully described in fewer pages. * New ideas/vision papers: These papers may describe new, unconventional software language engineering research positions or approaches that depart from standard practice. They can describe well-defined research ideas that are at an early stage of investigation. They could also provide new evidence to challenge common wisdom, present new unifying theories about existing SLE research that provides novel insight or that can lead to the development of new technologies or approaches, or apply SLE technology to radically new application areas. New ideas/vision papers must not exceed 5 pages and may optionally include 1 further page of bibliography/appendices. * SLE Body of Knowledge: The SLE Body of Knowledge (SLEBoK) is a community-wide effort to provide a unique and comprehensive description of the concepts, best practices, tools, and methods developed by the SLE community. In this respect, the SLE conference will accept surveys, essays, open challenges, empirical observations, and case study papers on the SLE topics. These can focus on, but are not limited to, methods, techniques, best practices, and teaching approaches. Papers in this category can have up to 20 pages, including bibliography/appendices. * Tool papers: These papers focus on the tooling aspects often forgotten or neglected in research papers. A good tool paper focuses on practical insights that will likely be useful to other implementers or users in the future. Any of the SLE topics of interest are appropriate areas for tool papers. Submissions must not exceed 5 pages and may optionally include 1 further page of bibliography/appendices. They may optionally include an appendix with a demo outline/screenshots and/or a short video/screencast illustrating the tool. **Workshops**: Workshops will be organised by STAF. Please inform us and contact STAF 2026 organisers if you would like to organise a workshop of interest to the SLE audience. Information on how to submit workshops can be found on the STAF 2026 Website. --------------------------- Submission --------------------------- SLE 2026 has a single submission round for papers, including a mandatory abstract registration. Authors of accepted research papers will be invited to submit artefacts. --------------------------- Format --------------------------- Submissions have to use the ACM SIGPLAN Conference Format âacmartâ ( https://sigplan.org/Resources/Author/#acmart-format) please make sure that you always use the latest ACM SIGPLAN acmart LaTeX template, and that the document class definition is \documentclass[sigplan,anonymous,review]{acmart}. Do not make any changes to this format! Ensure that your submission is legible when printed on a black and white printer. In particular, please check that colours remain distinct and font sizes in figures and tables are legible. To increase fairness in reviewing, a double-blind review process has become standard across SIGPLAN conferences. Accordingly, SLE will follow the double-blind process. Author names and institutions must be omitted from submitted papers, and references to the authorsâ own related work should be in the third person. No other changes are necessary, and authors will not be penalized if reviewers are able to infer their identities in implicit ways. All submissions must be in PDF format. You can access the submission site from the conference website: https://conf.researchr.org/home/sle-2026 --------------------------- Concurrent Submissions --------------------------- Papers must describe unpublished work that is not currently submitted for publication elsewhere as described by SIGPLANâs Republication Policy ( https://www.sigplan.org/Resources/Policies/Republication/) Submitters should also be aware of ACMâs Policy and Procedures on Plagiarism ( https://www.acm.org/publications/policies/plagiarism-overview) Submissions that violate these policies will be desk-rejected. --------------------------- Policy on Human Participant and Subject Research --------------------------- Authors conducting research involving human participants and subjects must ensure that their research complies with their local governing laws and regulations and the ACMâs general principles, as stated in the ACMâs Publications Policy on Research Involving Human Participants and Subjects ( https://www.acm.org/publications/policies/research-involving-human-particip…) If submissions are found to be violating this policy, they will be rejected. --------------------------- Reviewing Process --------------------------- All submitted papers will be reviewed by at least three members of the program committee. Research papers and tool papers will be evaluated concerning soundness, relevance, novelty, presentation, validation, and replicability. New ideas/vision papers will be evaluated primarily concerning soundness, relevance, novelty, and presentation. Tool papers will be evaluated concerning relevance, presentation, and replicability. For fairness reasons, all submitted papers must conform to the above instructions. Submissions that violate these instructions may be rejected without review at the discretion of the PC chairs. --------------------------- Artefact Evaluation --------------------------- SLE will use an evaluation process to assess the quality of artefacts on which papers are based to foster the culture of experimental reproducibility. Authors of accepted research papers are invited to submit artefacts. --------------------------- Awards --------------------------- * Distinguished paper: Award for the most notable paper, as determined by the PC chairs based on the recommendations of the program committee. * Distinguished artefact: Award for the artefact most significantly exceeding expectations, as determined by the AEC chairs based on the recommendations of the artefact evaluation committee. * Distinguished reviewer: Award for the programme committee member that produced the most useful reviews as assessed by paper authors. * Most Influential Paper: Award for the SLE 2016 paper with the greatest impact, as judged by the SLE Steering Committee. --------------------------- Publication --------------------------- All accepted papers will be published in the ACM Digital Library. **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 the conference. The official publication date affects the deadline for any patent filings related to published work. --------------------------- Organisation --------------------------- * General chair: Arnaud Blouin, Univ Rennes, INSA Rennes, Inria, CNRS, IRISA * PC co-chair: Jordi Cabot, Luxembourg Institute of Science and Technology * PC co-chair: Shigeru Chiba, University of Tokyo, Japan --------------------------- Contact --------------------------- For additional information, clarification, or answers to any questions, please get in touch with the program co-chairs (jordi.cabot(a)list.lu and chiba(a)g.ecc.u-tokyo.ac.jp)

1 0

UKSTUG Meeting: Norbert Hartl - Soil: a database for fun and profit - 26 November 2025
by UK Smalltalk Nov. 19, 2025

Nov. 19, 2025

Soil ( https://github.com/ApptiveGrid/Soil ) is an object oriented database implemented completely in smalltalk/pharo. It makes it easy to build a persistent solution without the burden of mapping everything to some external DSL/database. It supports storing arbitrary graphs and enables transparent access to them. It has binary search indexes to make lookups of huge collections quite efficient. It is the main database behind ApptiveGrid - low code tool to build business processes. ( https://www.apptivegrid.de/) Norbert Hartl ( https://github.com/noha ) is an experienced software engineer and entrepreneur with a strong track record of delivering business projects and developing key libraries and frameworks. As the co-founder of ApptiveGrid and PharoPro, he focuses on creating efficient, zero-dependency software solutions that drive business innovation and streamline operations. This will be an online meeting. If you'd like to join us, please sign up in advance on the meeting's Meetup page ( https://www.meetup.com/ukstug/events/311265917/ ) to receive the meeting details.

1 0

Pharo News of the Week 45/2025
by Marcus Denker Nov. 17, 2025

Nov. 17, 2025

# Pharo News of the Week 45/2025 New wanted! You can add your news to this list (that is, next week) using this form: https://tinyurl.com/4c89buy4 # The week on the Pharo Issue Tracker # Pharo11 - Implements compatibility with Strict Symbol Comparison feature in Pharo #1682 https://github.com/pharo-spec/Spec/pull/1682 # Fixes - Restore RGElementDefinition>>realParent's behavior of not setting the parent instance variable #18444 https://github.com/pharo-project/pharo/pull/18444 - Let simulation of click take enablement of presenter into account #1823 https://github.com/pharo-spec/Spec/pull/1823 - 18832-Saving-an-Image-with-the-Shortcut-produces-an-image-that-cannot-be-started #18835 https://github.com/pharo-project/pharo/pull/18835 - Post errorHandler fix #18823 https://github.com/pharo-project/pharo/pull/18823 # Tools - Fix class search after change on search options #1275 https://github.com/pharo-spec/NewTools/pull/1275 - Improve Finder search options #1274 https://github.com/pharo-spec/NewTools/pull/1274 - In MessageBrowser, decouple messageList presenter from its list of messages to present DNU in windowTitle method #1124 https://github.com/pharo-spec/NewTools/pull/1124 - Fix the DrTest coverage bug #18810 https://github.com/pharo-project/pharo/pull/18810 # FFI - uFFI FFIArray usage enhancement #18831 https://github.com/pharo-project/pharo/pull/18831 # VM - Simulator fixes #1025 https://github.com/pharo-project/pharo-vm/pull/1025 # Cleanup - Remove some usage of UIManager #1984 https://github.com/pharo-vcs/iceberg/pull/1984 - Refactoring cleanup spec standard dialogs #18837 https://github.com/pharo-project/pharo/pull/18837 - Deprecate ClassParentRenamed #18820 https://github.com/pharo-project/pharo/pull/18820 - Less NewUndeclared #18817 https://github.com/pharo-project/pharo/pull/18817 - Adding application in ClyBrowserMorph and CmdCommand to cut the depenâ¦ #18802 https://github.com/pharo-project/pharo/pull/18802 - Move deprecated methods to deprecated packages #18795 https://github.com/pharo-project/pharo/pull/18795 # Bootstrap / Packaging - Load Network-UUID later in the bootstrap #18834 https://github.com/pharo-project/pharo/pull/18834 - Do not load Debugging-Core with Hermes #18838 https://github.com/pharo-project/pharo/pull/18838 - Enable class initialization in BaselineOfMorphicCore #18836 https://github.com/pharo-project/pharo/pull/18836 - Introduce BaselineOfUIInfrastructure and clean dependencies #18830 https://github.com/pharo-project/pharo/pull/18830 - Cut dependency of Collection-Strings to Unicode #18826 https://github.com/pharo-project/pharo/pull/18826 - Extract Fonts and FreeType from BaselineOfMorphicCore #18824 https://github.com/pharo-project/pharo/pull/18824 - Bootstrap: Remove some duplicated load spots #18800 https://github.com/pharo-project/pharo/pull/18800 - Improve some baselines #18799 https://github.com/pharo-project/pharo/pull/18799 - Kill multiple bad dependencies #18798 https://github.com/pharo-project/pharo/pull/18798

1 0

DevEx survey
by stephane ducasse Nov. 16, 2025

Nov. 16, 2025

Hello people Sorry this is survey in french for developers, but it can interest french speaking developers. Bonjour, Pas plus de 5 min de votre temps! Je me permets de vous contacter afin de vous proposer de mener, au sein de vos Ã©quipes, une rÃ©plication de lâÃ©tude DevEx in Action, conduite en 2024 par N. Forsgren (Microsoft Research), E. Kalliamvakou (Github Next), A. Noda (DX), M. Greiler (DX), E. Houck (Microsoft) et M.-A. Storey (UniversitÃ© de Victoria). Article original disponible Ã https://queue.acm.org/detail.cfm?id=3639443 Cette rÃ©plication sâinscrit dans le cadre de ma thÃ¨se portant sur lâimpact rÃ©ciproque de la dette technique sur la santÃ© mentale des dÃ©veloppeurs. Lâobjectif de cette Ã©tude est dâÃ©valuer lâexpÃ©rience dÃ©veloppeur (DevEx), qui dÃ©finit la qualitÃ© de lâexpÃ©rience vÃ©cue par les dÃ©veloppeurs et dÃ©veloppeuses dans leur environnement technique et organisationnel. LâÃ©tude sâappuie sur trois dimensions principales : les boucles de retour (feedback), la charge cognitive et la capacitÃ© Ã maintenir sa concentration. La rÃ©plication consiste Ã mesurer ces dimensions et leur impact sur les rÃ©sultats perÃ§us au niveau individuel, de lâÃ©quipe et de lâentreprise. Le dispositif repose sur un questionnaire unique et identique Ã celui de lâÃ©tude originale. Il est anonyme, volontaire et prend environ 5 minutes Ã remplir. Les rÃ©ponses sont analysÃ©es par modÃ©lisation PLS-SEM (via SmartPLS 4), comme prÃ©cisÃ© dans lâÃ©tude originale. Lien du questionnaire : https://annac.limesurvey.net/422315?lang=fr Cordialement, Anna Cathelineau anna.cathelineau(a)gmail.com <mailto:anna.cathelineau@gmail.com>

2 1

A thought for Vanessa Freudenberg
by stephane ducasse Nov. 13, 2025

Nov. 13, 2025

Hello Pharoers Today I just learned that Vanessa Freudenberg passed away. And Iâm super sad. I knew her from Squeak Central, Impara and the funny Plop Project. Vanessa pushed SqueakJS and more projects. At ESUG this year we had fun with the new version of Plop. I do not have contact with her family and friend but I want to express my sincere condolences. Please pass them this message if you get in touch with them. S.

2 1

MPLR 2026 Call for Papers
by stephane ducasse Nov. 13, 2025

Nov. 13, 2025

Dear Smalltalk friends Please find the following conference call for papers that can interest you. If you know other forums that could be interested in virtual machines, compilers â¦. do not hesitate to forward this call. S. Ducasse and C. Scholliers PC chair of MPLR 26 ################################################################################## The 23rd International Conference on Managed Programming Languages & Runtimes (MPLR, formerly ManLang, originally PPPJ) 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). https://2026.ecoop.org/home/mplr-2026 Important Dates --------------- - Abstract Submission Deadline: February 27, 2026 - Paper Submission Deadline: March 6, 2026 - Paper Author Notification: April 15, 2026 - Camera Ready for Papers: April 30, 2026 - Conference Date: June 29, 2026 All deadlines are 23:59 AoE (UTC-12h). #### Topics The areas of interest related to managed programming languages and runtime systems include but are not limited to: - **Virtual Machines** - Portable intermediate representations (e.g., JVM, WebAssembly, RPython, ...) - Managed runtime systems (e.g., GraalVM, Android Runtime (ART), V8, JavaScriptCore, .NET, â¦) - VM design and optimization - VMs for mobile and embedded devices - VMs for real-time applications - Memory management and garbage collection - Hardware/software co-design - Domain-specific languages - Security and privacy - Persistence - **Languages and Compilers** - Managed languages - Compilers and interpreters - Type systems and program logics - Language interoperability - Parallelism, distribution, and concurrency - **Techniques, Tools, and Applications** - Static and dynamic program analysis - Testing and debugging - Simulation - Refactorings - Program synthesis - Performance analysis and monitoring - Compiler and program verification and model checking If you are unsure whether a particular topic falls within the scope of MPLR â26 or if you have any other questions, please do not hesitate to contact the Program Chair. #### Submission Categories MPLR accepts three types of submissions: - **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); - **Work-in-progress research papers**, describing hot topics or 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); - **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; up to 12 pages allowed if justified by the content); Accepted submissions will be published in the ACM Digital Library, except if the authors prefer not to be included. MPLR 2026 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 SIGPLAN format with the `sigplan` style. If you are using LaTeX, submissions need to use the `acmart` document class with the `sigplan` option (*not* the `sigconf` option). In the `acmart-primary.zip` file that downloads from the LaTeX (Version 1.90) link on the https://www.acm.org/publications/proceedings-template page, look for `samples/sample-sigplan.tex` as a guide. If you use Overleaf, be sure to change the `documentclass` option `manuscript` to `sigplan`. For ease of reviewing, please include page numbers in your submission using the LaTeX command `\settopmatter{printfolios=true}`. Please use the standard setting, e.g., the default font size for the SIGPLAN style is 10 point and the format uses two columns for the test. All submissions need to be in PDF format. MPLR now uses **double-blind reviewing**. **Authors should not show their names on a submission and should refer to their own work in third person.** We further recommend that they avoid publicizing the work, at least under the same or similar title, while it is under review. 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://mplr26.hotcrp.com

1 0

Re: Pharo and AI: A Natural Fit for the Future
by Kasper Osterbye Nov. 7, 2025

Nov. 7, 2025

And an other AI thing that I have now made work is Pharo, AI and PlantUML. This is what I write in Playground: aaa := 'Write a PlantUML code for the meta function umlToImage: in class AIAPlantUML. [RESONSETYPE]Please just return the PlantUML code. No comments' q0: [ AIASourceCodeBuilder new forClass: AIAPlantUML ]. AIAPlantUML umlToImage: aaa. And the result is: So now I can ask for a PlantUML for some specific topic, and the UML is build by the AI, and the PlantUML is then shown in Pharo. It is on a very experimental level yet. â Kasper

1 0