November 2025 - Pharo-dev - lists.pharo.org

Re: Fw: Pharo CIG Crash Issue

by Esteban Lorenzano

Hello, pharo-cig has never been tested on windows, I no wonder is crashing :) until now, generation always happened in linux-side (generatedlibraries however have been tested on windows, time to time... when generation has nothing to do with the platform :P). I have to say that pharo-cig is not a "pharo team" project (in the sense any member of the pharo team can take it). While we can have this conversation here, I would very much prefer if we have it at https://github.com/pharo-cig/pharo-cigÂ :) Esteban On 11/29/25 03:09, MORGAN LEE GUAN HAN via Pharo-dev wrote: > Forwarding the original email. > > ------------------------------------------------------------------------ > *From:*Â MORGAN LEE GUAN HAN <1211107272(a)student.mmu.edu.my> > *Sent:*Â Saturday, November 29, 2025 12:08 AM > *To:*Â Aik-Siong Koh <askoh(a)askoh.com> > *Subject:*Â Pharo CIG Crash Issue > Dear Pharo Team, > > I am currently attempting to replicate what Esteban Lorenzano did for > this Youtube Video <https://www.youtube.com/watch?v=U9fpvZJaFx4> > /(/*/Esteban Lorenzano - Pharo-CIG: C++ Interface Generator - 23 April > 2025/*/), /which is to//generate C Bindings for Pharo uFFI to > call,//in Windows 11/. /Unfortunately, I am unable to replicate the > results of the video. The results of my attempts leads to Pharo's > Virtual Machine crashing and exiting abruptly to the launcher. I am > unable to find any logs for this, and would appreciate your support > for this matter. > > *OS:*Â Windows 11 > *Clang:* > https://github.com/llvm/llvm-project/releases/tag/llvmorg-18.1.8 > <https://github.com/llvm/llvm-project/releases/tag/llvmorg-18.1.8>Â (LLVM-18.1.8-win64.exe) > *Pharo Template:*Â Pharo 14.0 - 64bit (development version, latest) > *Pharo CIG Github:* https://github.com/pharo-cig/pharo-cig > <https://github.com/pharo-cig/pharo-cig> > *Raylib: https://github.com/raysan5/raylib > <https://github.com/raysan5/raylib>* > > *Steps to Reproduce* > > *Step 1: Create Image* > > ** > > *Step 2: Installing Pharo CIG* > > Open Playground wtih 'Ctrl + O + P' (or 'Cmd + O + P'). > Copy and paste the Installation Code from the Pharo CIG Github > <https://github.com/pharo-cig/pharo-cig>. > Click the "Do it All" green triangle button on the top left of the > Playground Window. > > ** > > *Step 3: Installing Clang* > > Download and run the Pre-built binaries from this Github page > <https://github.com/llvm/llvm-project/releases/tag/llvmorg-18.1.8>Â according > to your platform. > The folder named LLVM should be in your "C:\Program Files" directory > after installation for Windows 11. > Other installation methods may be used according to your preference. > > *Step 4: Installing raylib* > > Download or clone the raylib Github repository > <https://github.com/raysan5/raylib>. > > Extract the folder ('raylib-master') if you are downloading the > repository. > Place the folder in a directory of your preference. E.g > "C:\Users\morgan\raylib-master" > > *Step 5: Setting Pharo CIG Requirements* > > CIG needs to be able to find the clang library. If it cannot find it > automatically, set the location in LibClang>>unix64LibraryName, e.g. - > Pharo CIG Github <https://github.com/pharo-cig/pharo-cig> > Open System Browser with 'Ctrl + O + B' (or 'Cmd + O + B'). > Create a "win32LibraryName" method in the LibClang class under the > CIG-LibClang package to set your "libclang.dll" location. This method > is missing from the default installation. > Paste in this code (/There may be whitespace character issues)/: > |win32LibraryName Â Â ^ FFIWindowsLibraryFinder new Â Â Â Â userPaths: > #('C:\Program Files\LLVM\bin'); Â Â Â Â findAnyLibrary: #('libclang.dll')| > > Save and create the method with 'Ctrl + S' (or 'Cmd + S'). > > > *Step 6: The Example Recipe from Github* > > Open Playground wtih 'Ctrl + O + P' (or 'Cmd + O + P'). > > Copy andÂ paste the example recipe from Github > <https://github.com/pharo-cig/pharo-cig?tab=readme-ov-file>into the > Playground. > > Configure the example recipe from Github > <https://github.com/pharo-cig/pharo-cig?tab=readme-ov-file>. > > Change "import:" and "cIncludedPath:" directories according to your > file structure. E.g '/home/esteban/dev/vm/raylib/src/raylib.h' > âÂ 'C:\Users\morgan\raylib-master\src\raylib.h' > > Click the "DoÂ it All" green triangle button on the top left of the > Playground Window. This should cause the Virtual Machine to abruptly > exit or crash. > > Code Snippet (/There may be whitespace character issues):/ > > (lib := CigCLibraryGenerator new) > Â "Prefix to be added to the generated classes (structures, enums, etc.)" > Â prefix: 'Ray'; > Â "name of the generated package (by default, is the same as the > libraryName, capitalized)" > Â packageName: 'Raylib'; > Â "Library name. If not unixLibraryName, macLibraryName and winLibraryName > Â Â are specified, it will be taken as base name for the existing libraries > Â Â (e.g. in this case raylib.so, raylib.dylib and raylib.dll)" > Â libraryName: 'raylib'; > Â "headers to import (there can be as many of them as is needed)." > Â import: 'C:\Users\morgan\raylib-master\src\raylib.h'; > Â import: 'C:\Users\morgan\raylib-master\src\rcamera.h'; > Â "include path (-I of c compiler), to allow libclang to find other > Â Â includedÂ headers." > Â cIncludePath: 'C:\Users\morgan\raylib-master\src'; > Â "Since thisÂ is a graphical library, instruct the library to run in > mainthread > Â Â (otherwise, default is 'same thread' which is the same thread the > pharo is > Â Â running)" > Â useMainThread. > "generate the library" > lib generate. > > > > End of email. > > > >

Nov. 29, 2025

Fw: Pharo CIG Crash Issue

by MORGAN LEE GUAN HAN

Forwarding the original email. ________________________________ From: MORGAN LEE GUAN HAN <1211107272(a)student.mmu.edu.my> Sent: Saturday, November 29, 2025 12:08 AM To: Aik-Siong Koh <askoh(a)askoh.com> Subject: Pharo CIG Crash Issue Dear Pharo Team, I am currently attempting to replicate what Esteban Lorenzano did for this Youtube Video<https://www.youtube.com/watch?v=U9fpvZJaFx4> (Esteban Lorenzano - Pharo-CIG: C++ Interface Generator - 23 April 2025), which is to generate C Bindings for Pharo uFFI to call, in Windows 11. Unfortunately, I am unable to replicate the results of the video. The results of my attempts leads to Pharo's Virtual Machine crashing and exiting abruptly to the launcher. I am unable to find any logs for this, and would appreciate your support for this matter. OS: Windows 11 Clang: https://github.com/llvm/llvm-project/releases/tag/llvmorg-18.1.8 (LLVM-18.1.8-win64.exe) Pharo Template: Pharo 14.0 - 64bit (development version, latest) Pharo CIG Github: https://github.com/pharo-cig/pharo-cig Raylib: https://github.com/raysan5/raylib Steps to Reproduce Step 1: Create Image [cid:1a4a23bb-52e6-47a5-b0a7-b251d6ddc8ea] Step 2: Installing Pharo CIG Open Playground wtih 'Ctrl + O + P' (or 'Cmd + O + P'). Copy and paste the Installation Code from the Pharo CIG Github<https://github.com/pharo-cig/pharo-cig>. Click the "Do it All" green triangle button on the top left of the Playground Window. [cid:2a667f99-b808-4950-a40a-798054e502e4] Step 3: Installing Clang Download and run the Pre-built binaries from this Github page<https://github.com/llvm/llvm-project/releases/tag/llvmorg-18.1.8> according to your platform. The folder named LLVM should be in your "C:\Program Files" directory after installation for Windows 11. Other installation methods may be used according to your preference. Step 4: Installing raylib Download or clone the raylib Github repository<https://github.com/raysan5/raylib>. Extract the folder ('raylib-master') if you are downloading the repository. Place the folder in a directory of your preference. E.g "C:\Users\morgan\raylib-master" Step 5: Setting Pharo CIG Requirements CIG needs to be able to find the clang library. If it cannot find it automatically, set the location in LibClang>>unix64LibraryName, e.g. - Pharo CIG Github<https://github.com/pharo-cig/pharo-cig> Open System Browser with 'Ctrl + O + B' (or 'Cmd + O + B'). Create a "win32LibraryName" method in the LibClang class under the CIG-LibClang package to set your "libclang.dll" location. This method is missing from the default installation. Paste in this code (There may be whitespace character issues): win32LibraryName ^ FFIWindowsLibraryFinder new userPaths: #('C:\Program Files\LLVM\bin'); findAnyLibrary: #('libclang.dll') [cid:3241b208-b515-4b7b-98fc-45312ec65c82] Save and create the method with 'Ctrl + S' (or 'Cmd + S'). [cid:7d0e72f0-4086-411a-8e27-c2b11c4df817] Step 6: The Example Recipe from Github Open Playground wtih 'Ctrl + O + P' (or 'Cmd + O + P'). Copy and paste the example recipe from Github <https://github.com/pharo-cig/pharo-cig?tab=readme-ov-file> into the Playground. Configure the example recipe from Github<https://github.com/pharo-cig/pharo-cig?tab=readme-ov-file>. Change "import:" and "cIncludedPath:" directories according to your file structure. E.g '/home/esteban/dev/vm/raylib/src/raylib.h' â 'C:\Users\morgan\raylib-master\src\raylib.h' Click the "Do it All" green triangle button on the top left of the Playground Window. This should cause the Virtual Machine to abruptly exit or crash. Code Snippet (There may be whitespace character issues): (lib := CigCLibraryGenerator new) "Prefix to be added to the generated classes (structures, enums, etc.)" prefix: 'Ray'; "name of the generated package (by default, is the same as the libraryName, capitalized)" packageName: 'Raylib'; "Library name. If not unixLibraryName, macLibraryName and winLibraryName are specified, it will be taken as base name for the existing libraries (e.g. in this case raylib.so, raylib.dylib and raylib.dll)" libraryName: 'raylib'; "headers to import (there can be as many of them as is needed)." import: 'C:\Users\morgan\raylib-master\src\raylib.h'; import: 'C:\Users\morgan\raylib-master\src\rcamera.h'; "include path (-I of c compiler), to allow libclang to find other included headers." cIncludePath: 'C:\Users\morgan\raylib-master\src'; "Since this is a graphical library, instruct the library to run in mainthread (otherwise, default is 'same thread' which is the same thread the pharo is running)" useMainThread. "generate the library" lib generate. [cid:55b4605c-3b19-45f0-8ed8-ef9093b6fa89] End of email.

Nov. 29, 2025

ANN: More syntax highlights for Pharo code :)

by Esteban Lorenzano

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

Nov. 24, 2025

Pharo News of the Week 46/2025

by Marcus Denker

# 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

Nov. 20, 2025

unsubscribe

by Kaan Ozdincer

-- Kaan Ozdincer http://kaan.ozdincer.com

Nov. 17, 2025

Pharo News of the Week 45/2025

by Marcus Denker

# 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

Nov. 17, 2025

MPLR 2026 Call for Papers

by stephane ducasse

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

Nov. 13, 2025