- Pharo-dev - lists.pharo.org

[ Smalltalkers wanted... ]

by stephane ducasse

We are looking for Smalltalkers for adesso insurance solutions GmbH. Remote work is possible and German language is required (at least B2). Links: https://www.adesso.de/de/jobs-karriere/unsere-stellenangebote/Software-Engi… <https://www.adesso.de/de/jobs-karriere/unsere-stellenangebote/Software-Engi…> https://www.linkedin.com/jobs/view/3353601212/ <https://www.linkedin.com/jobs/view/3353601212/> Text: About the job FÃ¼r unsere Tochtergesellschaft, die adesso insurance solutions GmbH, suchen wir einen Software Engineer Smalltalk (all genders) Als Teil der adesso group bÃ¼ndelt die adesso insurance solutions GmbH das eigene Produktportfolio fÃ¼r den Versicherungsmarkt und treibt innovative Software-LÃ¶sungen in diesem Umfeld voran. Wir sind ein Team aus Ã¼ber 200 engagierten Kollegen und Kolleginnen. Und du kannst ein Teil davon werden. DEINE ROLLE - DAS WARTET AUF DICH Du kennst dich mit objektorientierter Programmierung aus? Smalltalk ist fÃ¼r dich eine Programmiersprache mit Tiefgang? Dann suchen wir genau dich als Software Engineer fÃ¼r unser Professional Services Team im Umfeld des Pensionsmanagements. Bei uns arbeitest du gemeinsam im Team mit Entwicklern, Testern und Projektmanagern an den besten LÃ¶sungen fÃ¼r unsere CollPhir-Software. Ãbrigens: Wir sind langjÃ¤hriger Sponsor der EUSG. Deine Aufgaben Â· Auf Basis von Smalltalk programmierst du neue Anforderungen und Erweiterungen. Â· Neue Anforderungen unserer CollPhir-Software setzt du um. Â· Du analysierst, konzipierst und realisierst eigenstÃ¤ndig kundenspezifische Erweiterungen. Â· Im Third-Level unterstÃ¼tzt du das Support-Team bei technischen Fragen zur Software. Â· Die Dokumentation und das Beheben von Fehlern gehÃ¶ren auch zu deinen Aufgaben. Deine Skills - Das Bringst Du Mit Â· Du verfÃ¼gst Ã¼ber einen technischen Hochschulabschluss (Informatik, Ingenieurwissenschaften, Mathematik, Physik, o.Ã.) oder hast bereits Erfahrung in der Softwareentwicklung mit Smalltalk gesammelt Â· Du hast keine Scheu vor Datenbankmanagementsystemen und verfÃ¼gst Ã¼ber â zumindest rudimentÃ¤res â Wissen in technologisch benachbarten Bereichen (z.B. Java) Â· Du bist neugierig und lernbereit, denn bei uns wird Weiterentwicklung sowohl technologisch als auch persÃ¶nlich groÃgeschrieben Â· Deine Deutschkenntnisse sind sehr gut und mindestens auf Level B2 CHANCENGEBER - WAS ADESSO AUSMACHT Unser Versprechen: Du wirst dich bei uns wohlfÃ¼hlen! Kollegial, familiÃ¤r und auf AugenhÃ¶he â wir leben Austausch, Teamgeist und einen respektvollen Umgang miteinander. Das und viel mehr steht fÃ¼r unser ganz besonderes Wir-GefÃ¼hl. FÃ¼r das es sogar ein Wort gibt: adessi. Denn wir sind alle adessi ab Tag Eins und bei uns bist du von Anfang an Teil des Teams. Unsere Kultur und das Zusammenarbeiten sind geprÃ¤gt von gegenseitiger WertschÃ¤tzung, Anerkennung und UnterstÃ¼tzung. Das verbindet uns hierarchieÃ¼bergreifend â auch im Home-Office. Jeder und jedem adessi stehen alle MÃ¶glichkeiten zur persÃ¶nlichen und beruflichen Entwicklung offen. Unser umfangreiches Trainings- und Weiterbildungsangebot sorgt dafÃ¼r, dass deine Entwicklung bei uns nicht stillsteht. Denn Chancengeber zu sein, das liegt in unserer DNA. Â· Welcome Days - Zwei Tage zum Reinkommen und Netzwerken Â· Bis zu drei Tage mobiles Arbeiten â keine Frage von Pandemien, sondern von Ãberzeugung Â· Deine Entwicklung - Ã¼ber 260 Lern- und Trainingsthemen Â· Events - fachlich und mit SpaÃfaktor Â· Hemden-/Blusenreinigung - zweimal die Woche frisch aufgebÃ¼gelt Â· SportfÃ¶rderung - Zuschuss zum Fitnessstudio und mehr Ã¼ber qualitrain sowie Ãbernahme der Platzmiete fÃ¼r die Sporthalle Â· adesso Mind - Das adesso-Programm rund um Mindfulness Â· PrÃ¤mien fÃ¼r Mitarbeitende - eine Vielzahl an PrÃ¤mien fÃ¼r zusÃ¤tzliches Engagement Â· Auszeitprogramm - Raum fÃ¼r deine persÃ¶nliche Lebensplanung KONTAKT Du bist offen fÃ¼r neue und anspruchsvolle Aufgaben? Dann sende uns deine Bewerbungsunterlagen (inkl. deines CV, deiner Arbeits- und Studienzeugnisse sowie deiner Gehaltsvorstellungen und dem frÃ¼hestmÃ¶glichen Eintrittstermin) vorzugsweise Ã¼ber unser Webformular. Â· Sina MÃ¶schl Â· Recruiting Â· +49 231 7000 7100 Best wishes, -- FÃ©lix Madrid adesso insurance solutions GmbH Agrippinawerft 26 50678 KÃ¶ln T +49 221 27850-355 M +49 152 38869-784 F +49 221-27850-500 E felix.madrid(a)adesso-insurance-solutions.de <mailto:felix.madrid@adesso-insurance-solutions.de> www.adesso-insure.de <http://www.adesso-insure.de/>

Nov. 23, 2022

Re: This week (46/2022) on the Pharo Issue Tracker

by Tim Mackinnon

Wow - thats even neater... all done with our normal tools - on the fly. So cool. Not sure many environments/languages can reason about things in this way. Worthy of a blog post for the wider world I would say - as this kind of stuff should be on more people's radars. Thanks again for all this kind of work. It would be so easy to just continue to think the job was done 20 years ago, where in fact we've only scratched the surface as our understanding of effective software development has improved. Tim On Fri, 18 Nov 2022, at 10:19 AM, Marcus Denker wrote: > > > > On 18 Nov 2022, at 08:15, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > > We merged 18 PRs > > > > Lots of improvements related to BlockClosures this week. > > > > First some helper methods on the AST: > > - #hasNonLocalReturn: check if there is a non-local return > > - #isConstant: Blocks of the kind [#justSomeLiteral] > > - #constantValue: return that literal (and nil for empty [] ) > > - #numArgs for RBBlockNode, as we have already for BlockClosure "[:a | ] sourceNode numArgsâ > > > > Some numbers: > > "there are lots of blocks" > allBlocks := Smalltalk globals allMethods flatCollect: [:meth | meth ast blockNodes ]. > allBlocks size. "100140" > > "but many are compiled inline (eg argunments of #ifTrue:)" > currentFullBlocks := allBlocks select: [:blockNode | blockNode isInlined not]. > currentFullBlocks size. "45193" > > "What we could compile as CleanBlockClosure" > cleanBlocks := currentFullBlocks select: [:blockNode | blockNode isClean]. > cleanBlocks size. "11090" > > "many clean blocks are actually constant" > constantBlocks := cleanBlocks select: [:blockNode | blockNode isConstant]. > constantBlocks size. "3200" > > "FullBlocks that need the outerContext to return" > fullBocksWithReturn := currentFullBlocks select: [ :each | each hasNonLocalReturn ]. > fullBocksWithReturn size â3816â > > We can inspect the collections and then use the inspector to browse the code (with the block > that you look at hightlighted), to get a feel where these are used, e.g. for constant: > > > >

Nov. 18, 2022

Re: This week (46/2022) on the Pharo Issue Tracker

by Marcus Denker

> On 18 Nov 2022, at 08:15, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > We merged 18 PRs > > Lots of improvements related to BlockClosures this week. > > First some helper methods on the AST: > - #hasNonLocalReturn: check if there is a non-local return > - #isConstant: Blocks of the kind [#justSomeLiteral] > - #constantValue: return that literal (and nil for empty [] ) > - #numArgs for RBBlockNode, as we have already for BlockClosure "[:a | ] sourceNode numArgsâ > Some numbers: "there are lots of blocks" allBlocks := Smalltalk globals allMethods flatCollect: [:meth | meth ast blockNodes ]. allBlocks size. "100140" "but many are compiled inline (eg argunments of #ifTrue:)" currentFullBlocks := allBlocks select: [:blockNode | blockNode isInlined not]. currentFullBlocks size. "45193" "What we could compile as CleanBlockClosure" cleanBlocks := currentFullBlocks select: [:blockNode | blockNode isClean]. cleanBlocks size. "11090" "many clean blocks are actually constant" constantBlocks := cleanBlocks select: [:blockNode | blockNode isConstant]. constantBlocks size. "3200" "FullBlocks that need the outerContext to return" fullBocksWithReturn := currentFullBlocks select: [ :each | each hasNonLocalReturn ]. fullBocksWithReturn size â3816â We can inspect the collections and then use the inspector to browse the code (with the block that you look at hightlighted), to get a feel where these are used, e.g. for constant:

Nov. 18, 2022

Re: This week (46/2022) on the Pharo Issue Tracker

by Tim Mackinnon

The attention to detail on these cleanups to make everything symmetrical is very nice - cool work. Tim On Fri, 18 Nov 2022, at 7:15 AM, Marcus Denker wrote: > We merged 18 PRs > > Lots of improvements related to BlockClosures this week. > > First some helper methods on the AST: > - #hasNonLocalReturn: check if there is a non-local return > - #isConstant: Blocks of the kind [#justSomeLiteral] > - #constantValue: return that literal (and nil for empty [] ) > - #numArgs for RBBlockNode, as we have already for BlockClosure "[:a | > ] sourceNode numArgs" > > Some improvements for isClean: > - unify between AST and BlockClosure > - more tests > - inlined blocks can be clean, important as it is recursive: [true > ifTrue: []] should be clean > - cleanup code in CleanBlock, receiver is known to be nil > > Compiler support for ConstantBlockClosure: > - We can specialize clean blocks of the kind [#justSomeLiteral] to > execute faster > - add ConstantBlockClosure, add compiler support, active when compiling > with clean blocks enabled > > Compiler support for full block without outer context: > - we only need the outerContext for non-local returns. > - add support to IRBuilder for full blocks without outer context > - implement compiler support (option #optionBlockClosureOptionalOuter, > false for now) > > Quick return for Blocks: > - Compile quickreturn for CompiledBlock, just like CompiledMethod (e.g. > for [^1]). > - speeds up execution a little (but of course not creation) > > Block Closures > ============== > > - AST: add a recursive #hasNonLocalReturn and #isConstant #11882 > https://github.com/pharo-project/pharo/pull/11882 > > - add #numArgs to RBBlockNode #11902 > https://github.com/pharo-project/pharo/pull/11902 > > - CleanBlock cleanup code: there should be no receiver ivar #11884 > https://github.com/pharo-project/pharo/pull/11884 > > - 11881-RBBlockNodeisClean-takes-every-optimized-block-to-be-not-clean #11890 > https://github.com/pharo-project/pharo/pull/11890 > > - 1883-CleanBlockChecker-does-not-recurse-into-the-blocks #11900 > https://github.com/pharo-project/pharo/pull/11900 > > - ConstantBlockClosure: active when compiling with clean blocks enabled #11894 > https://github.com/pharo-project/pharo/pull/11894 > > - CompiledBlocks: compile quick returns #11907 > https://github.com/pharo-project/pharo/pull/11907 > > - IRBuilder: add support for outerContext flag for Closure creation #11905 > https://github.com/pharo-project/pharo/pull/11905 > > - 11911-Compiler-add-compiler-option-for-outerContextNeeded #11917 > https://github.com/pharo-project/pharo/pull/11917 > > > > Fixes > ===== > > - Register-as-basicInspector #431 > https://github.com/pharo-spec/NewTools/pull/431 > > - 11803 return value of inspect should be the receiver and not a sp > window presenter #11886 > https://github.com/pharo-project/pharo/pull/11886 > > - Fixes #429, VersionBrowser: left pane empty #430 > https://github.com/pharo-spec/NewTools/pull/430 > > - Turn off ReLongMethodsRule for test methods #11892 > https://github.com/pharo-project/pharo/pull/11892 > > - ClassParser: Implement #asSlot to return a correct Slot instances for > complex slots #11898 > https://github.com/pharo-project/pharo/pull/11898 > > - Fixes #11802 - Adds full consistency checks to class Time #11891 > https://github.com/pharo-project/pharo/pull/11891 > > - Fixing to correctly get the VM for running the tests #11897 > https://github.com/pharo-project/pharo/pull/11897 > > - Fixes #429, VersionBrowser: left pane empty #430 > https://github.com/pharo-spec/NewTools/pull/430 > > Cleanup > ======= > - 11810-FT2Handle-classstartUp-compiled-code-on-image-startup #11811 > https://github.com/pharo-project/pharo/pull/11811 > > > > Comments > ========= > > - fixing comments in package Regex #11888 > https://github.com/pharo-project/pharo/pull/11888

Nov. 18, 2022

This week (46/2022) on the Pharo Issue Tracker

by Marcus Denker

We merged 18 PRs Lots of improvements related to BlockClosures this week. First some helper methods on the AST: - #hasNonLocalReturn: check if there is a non-local return - #isConstant: Blocks of the kind [#justSomeLiteral] - #constantValue: return that literal (and nil for empty [] ) - #numArgs for RBBlockNode, as we have already for BlockClosure "[:a | ] sourceNode numArgs" Some improvements for isClean: - unify between AST and BlockClosure - more tests - inlined blocks can be clean, important as it is recursive: [true ifTrue: []] should be clean - cleanup code in CleanBlock, receiver is known to be nil Compiler support for ConstantBlockClosure: - We can specialize clean blocks of the kind [#justSomeLiteral] to execute faster - add ConstantBlockClosure, add compiler support, active when compiling with clean blocks enabled Compiler support for full block without outer context: - we only need the outerContext for non-local returns. - add support to IRBuilder for full blocks without outer context - implement compiler support (option #optionBlockClosureOptionalOuter, false for now) Quick return for Blocks: - Compile quickreturn for CompiledBlock, just like CompiledMethod (e.g. for [^1]). - speeds up execution a little (but of course not creation) Block Closures ============== - AST: add a recursive #hasNonLocalReturn and #isConstant #11882 https://github.com/pharo-project/pharo/pull/11882 - add #numArgs to RBBlockNode #11902 https://github.com/pharo-project/pharo/pull/11902 - CleanBlock cleanup code: there should be no receiver ivar #11884 https://github.com/pharo-project/pharo/pull/11884 - 11881-RBBlockNodeisClean-takes-every-optimized-block-to-be-not-clean #11890 https://github.com/pharo-project/pharo/pull/11890 - 1883-CleanBlockChecker-does-not-recurse-into-the-blocks #11900 https://github.com/pharo-project/pharo/pull/11900 - ConstantBlockClosure: active when compiling with clean blocks enabled #11894 https://github.com/pharo-project/pharo/pull/11894 - CompiledBlocks: compile quick returns #11907 https://github.com/pharo-project/pharo/pull/11907 - IRBuilder: add support for outerContext flag for Closure creation #11905 https://github.com/pharo-project/pharo/pull/11905 - 11911-Compiler-add-compiler-option-for-outerContextNeeded #11917 https://github.com/pharo-project/pharo/pull/11917 Fixes ===== - Register-as-basicInspector #431 https://github.com/pharo-spec/NewTools/pull/431 - 11803 return value of inspect should be the receiver and not a sp window presenter #11886 https://github.com/pharo-project/pharo/pull/11886 - Fixes #429, VersionBrowser: left pane empty #430 https://github.com/pharo-spec/NewTools/pull/430 - Turn off ReLongMethodsRule for test methods #11892 https://github.com/pharo-project/pharo/pull/11892 - ClassParser: Implement #asSlot to return a correct Slot instances for complex slots #11898 https://github.com/pharo-project/pharo/pull/11898 - Fixes #11802 - Adds full consistency checks to class Time #11891 https://github.com/pharo-project/pharo/pull/11891 - Fixing to correctly get the VM for running the tests #11897 https://github.com/pharo-project/pharo/pull/11897 - Fixes #429, VersionBrowser: left pane empty #430 https://github.com/pharo-spec/NewTools/pull/430 Cleanup ======= - 11810-FT2Handle-classstartUp-compiled-code-on-image-startup #11811 https://github.com/pharo-project/pharo/pull/11811 Comments ========= - fixing comments in package Regex #11888 https://github.com/pharo-project/pharo/pull/11888

Nov. 18, 2022

This week (45/2022) on the Pharo Issue Tracker

by Marcus Denker

We merged 17 PR this week: Code Coverage ============= - Package 'Coverage' as a higher level API for code coverage #11830 https://github.com/pharo-project/pharo/pull/11830 - Coverage: add static callgraphs #11866 https://github.com/pharo-project/pharo/pull/11866 Refactoring Engine ================== - Transition deprecate method refactoring to use driver #11851 https://github.com/pharo-project/pharo/pull/11851 - Fix: #11868 generate hash and printOn: are NOT refactoring so indicatâ¦ #11869 https://github.com/pharo-project/pharo/pull/11869 - Fixes #11872 adding abstract method and improving generate accessors #11873 https://github.com/pharo-project/pharo/pull/11873 - Fixes #11874: Remove new method to class side #11875 https://github.com/pharo-project/pharo/pull/11875 - fix #11877: Cleaning Replace Calls Transformation #11878 https://github.com/pharo-project/pharo/pull/11878 Fixes ===== - Fix #11843 renaming a manifest breaks. #11857 https://github.com/pharo-project/pharo/pull/11857 - 11842-Context-menu-on-class-variables-opens-debug-menu #11864 https://github.com/pharo-project/pharo/pull/11864 - Fixes the problem related to backwards selection. Closes #11848 #11849 https://github.com/pharo-project/pharo/pull/11849 - Fix the printString of sequences including the same modifier. #11865 https://github.com/pharo-project/pharo/pull/11865 Cleanup ======= - Fix: #11852 one less obsolete pragma #11856 https://github.com/pharo-project/pharo/pull/11856 - Fix: #11854 removing useless code and obsolete pragmas! #11855 https://github.com/pharo-project/pharo/pull/11855 - Clean blocks simpler checks #11879 https://github.com/pharo-project/pharo/pull/11879 - #instVarNamed: does not need to send #asSymbol to the name #11860 https://github.com/pharo-project/pharo/pull/11860 - Make drtests spec2 compatible #11859 https://github.com/pharo-project/pharo/pull/11859 Pharo10 ======= - [improvement] backport of #11487: Underscore in class name breaks text completion #11837 https://github.com/pharo-project/pharo/pull/11837

Nov. 11, 2022

This week (44/2022) on the Pharo Issue Tracker

by Marcus Denker

We merged 7 PRs this week Fixes ===== - 11727 double click and drag does not select whole words #11838 https://github.com/pharo-project/pharo/pull/11838 - ClassParser: CDVariableNode should use AST of the variable definition #11788 https://github.com/pharo-project/pharo/pull/11788 - Closes #11817. The class creation text suggestion in Calypso now uses the current clâ¦ #11846 https://github.com/pharo-project/pharo/pull/11846 - fixing OCBcToASTCache so that pcsForNode: gives the bytecode offsets associated to a node, in the ascending order #11847 https://github.com/pharo-project/pharo/pull/11847 - Change extract method shortcut to cmd e, cmd m #11839 https://github.com/pharo-project/pharo/pull/11839 - Fix #11794: Enhance CI to use the right VM version #11795 https://github.com/pharo-project/pharo/pull/11795 Refactoring Engine ================== - Transition MoveMethodToClassSide refactoring to use driver object #11825 https://github.com/pharo-project/pharo/pull/11825

Nov. 7, 2022

Digital Twin applied to Software

by Aik-Siong Koh

Hi: I have a novel idea "Digital Twin applied to Software". See attached slides. It points to the future of improved programming productivity and reliability. Let me know what you think. Thanks, Aik-Siong Koh http://ar-cad.com Abstract Digital Twin applied to Software Aik-Siong Koh askoh.com There has been a major dichotomy in computing right from the beginning: Statically Typed vs Dynamically Typed programming languages. The former languages produce fast executables but are inflexible to program. The latter are just the converse. This dichotomy has been frustrating to programmers who always feel they have to make sacrifices when making a choice. It also often leads to futile language wars. The Digital Twin concept was introduced in engineering where a physical system is modeled digitally in geometry, simulation and other information. The concept has proven so successful that it is being applied to almost everything in engineering from simple mouse traps to complex whole cities. It occurred to the author that this concept can be extended to software too. For example, execution in C++ is famously fast. But development in C++ is notoriously difficulty because of language complexity and long build times. A flexible digital twin can be a program written in Smalltalk which is famous for live programming. "Development at the speed of thought" is the motto and is real. What is gained by this duplication? Firstly, the flexible twin can be use to explore new algorithms, features, solutions and fix bugs quickly. Only desired codes are translated to C++ manually or automatically. Secondly, the two programs can check each other so that bugs are reduced significantly. These two gains will define future programming productivity and quality. The Digital Twin concept will also drive the automatic translation of the flexible language to the fast language. Bio Dr Aik-Siong Koh has a PhD from The University of Texas at Austin where he programed in FORTRAN to simulation mechanical systems. While teaching at Texas Tech University and Nanyang Technological University, he developed interest in Multibody Dynamics. To develop his own Multibody Dynamics simulator, he researched for the most productive programming language and discovered Smalltalk. The live programming capabilities of Smalltalk permitted him to build a successful simulator which he then proceeded to commercialize. His later experience with C++ at Mechanical Dynamics and MathWorks gave him the idea of Digital Twin for Software.

Oct. 28, 2022

This week (43/2022) on the Pharo Issue Tracker

by Marcus Denker

This week (43/2022) on the Pharo Issue Tracker We merged 8 PRs this week: Features ======== - Add a shortcut to extract method refactoring #11814 https://github.com/pharo-project/pharo/pull/11814 - Adding removeKey:ifAbsent: #11821 https://github.com/pharo-project/pharo/pull/11821 - add Collection>>atRandom:weighting: and cie and tests #11829 https://github.com/pharo-project/pharo/pull/11829 Fixes ======== - Fix : missing isScripting method in LessonView #11815 https://github.com/pharo-project/pharo/pull/11815 - made rename method refactor "Spec2 compliant" #11826 https://github.com/pharo-project/pharo/pull/11826 - Cleanup-asCollectionElement-ChunkFileFormatParser #11827 https://github.com/pharo-project/pharo/pull/11827 - Bugfix: Browse class from Meta inspector pane #425 https://github.com/pharo-spec/NewTools/pull/425 Pharo10 ======= - Pharo10: 6191 find between substrings freezes the image #11770 https://github.com/pharo-project/pharo/pull/11770

Oct. 28, 2022

Looking for an engineer position to work on Virtual Machines

by Pierre Misse-Chanabier

Hello, My name is Pierre Misse-Chanabier. I'm finishing my PhD in the RMOD team on testing Virtual Machines in about two months. I am therefore looking for a Job, hopefully in the Pharo community ! Ideally, I'm looking to work in the domains of Virtual Machines or Language Tooling, or Meta-programing, but I'm open to other opportunities. See my CV attached. I have to stay in Lille for at least the next year, therefore, I am looking to work remotely. Here are my most important projects and publications about them: Illicium : a framework to generate C code from Pharo code. Github repository: [ https://github.com/hogoww/Illicium | https://github.com/hogoww/Illicium ] IWST'19 Illicium: A modular transpilation toolchain from Pharo to C [ https://hal.archives-ouvertes.fr/hal-02297860/ | https://hal.archives-ouvertes.fr/hal-02297860/ ] version poster SAC'22 & full ICSR'22: Differential testing of simulation-based VM generators: automatic detection of VM generator semantic gaps between simulation and generated VMs [ https://link.springer.com/chapter/10.1007/978-3-031-08129-3_7 | https://link.springer.com/chapter/10.1007/978-3-031-08129-3_7 ] [ https://dl.acm.org/doi/abs/10.1145/3477314.3507171 | https://dl.acm.org/doi/abs/10.1145/3477314.3507171 ] Polyphemus: Retro engineering of the Pharo Image, and ease of VM tooling Github Repository: [ https://github.com/hogoww/Polyphemus/ | https://github.com/hogoww/Polyphemus/ ] Video Presentation for Esug Innovation award (I was unable to present it myself): [ https://www.youtube.com/watch?v=zf3cCtNW830 | https://www.youtube.com/watch?v=zf3cCtNW830 ] VMIL'22: Ease VM Level Tooling with Language Level Ordinary Object Pointers [ https://hal.inria.fr/hal-03827632 | https://hal.inria.fr/hal-03827632 ] (preprint) I am particularly interested in my latest work: Polyphemus. I have also worked on many part of the Pharo ecosystem. The Pharo VM, The Pharo bootstrap, Calypso, Debugger, selector extraction, Iceberg scripting, SUnit ... Let me know if you have openings or questions ! Pierre

Oct. 25, 2022