January 2023 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Sacrilegeous question : what are compelling use cases for Pharo

by mayuresh＠kathe.in

Hello, In response to my email below, I received 5 interesting responses. I thank those people for writing-in. Here is my take on what I've understood and why I am still hesitant to go along. My comments on those responses are further below, but, at the moment, let me explain my situation. I am a 46 year-old who has been programming computers since the age of 16. I used to be a highly sought-after programmer till the year 2000, when due to circumstances beyond my control, my life and career got destroyed completely. In fact, I was so highly valued, that in spite of me being from India, I was pursued by Verizon US. I am now confined to my home (mostly) and I have very little to do, in the past 12 years I have not programmed anything beyond a basic prime-number tester and a fibonacci-sequence generator in C. I am getting my life back in order and I need some occupation, though, not necessarily one from which I would demand financial returns. I have been dilly-dallying on a decision, primarily because I am unable to take a call on whether to pursue my love for the low-level (x64 assembler + Forth) or the extremely high-level (work involving reasoning using symbolic inference) using a Smalltalk (either Squeak or Pharo). The above is not meant to elicit sympathy, but has been tacked-in just to give potential advisers an idea about my state. Onward to my take on the responses I received to my first email. As Noury Bouraqadi and Stephane Ducasse mentioned: It's not about what you can do, but it's about how you do it. I'd say, that is the basic problem with all Smalltalk aficionados. The whole environment is such a joy to work with that it is addictive, to the extent that developers forget that it is the "what you can do" which is of utmost importance. Jupiter Jones email provided the most amount of real-world use-cases. Though, I am interested in understanding how to use Pharo as the development tool to be able to release code via GemStone Smalltalk. Is it so that Seaside runs identically on Pharo as well as GemStone Smalltalk? So, in a sense, Seaside would to Smalltalk, what "Ruby on Rails" is to Ruby. Tim Mackinnon is very correct in observing that relative to C# and Swift, Smalltalk (and hence Pharo) is very compact, simple and approachable. Though, I did not understand his statement about conditional logic becoming easier to understand after working especially with Smalltalk. Would he care to elaborate? Also, on Tim's allusion to Lisp being a cousin, well, Smalltalkers had better acknowledge the fact that most Lispers "look down" upon Smalltalk and do not spare any opportunity to berate its users/developers (this is from personal experience). Along those lines, I would also like to get an explanation from Jupiter Jones' for "how do you do an if/then?" which as he states leads to a "mind-blown" moment. Thank you, ~Mayuresh On Saturday, January 14, 2023 01:31 PM IST, "mayuresh(a)kathe.in via Pharo-users" <pharo-users(a)lists.pharo.org> wrote: > Hello, > > This isn't a mail intended to troll this community. > > I am genuinely curious about what would be the type of use cases which would be exemplary for Pharo? > > Now-a-days, anything one could have accomplished solely with Smalltalk (and hence Pharo) can be accomplished with a number of modern programming languages and their associated frameworks, e.g. Google's Dart with Flutter, Apple Swift with SwiftUI, Microsoft's C# with WinUI. > And such languages and their associated frameworks are built from the ground-up for a particular platform, while Pharo does not have any such targets, which usually renders graphical applications built using Pharo to "look like" aliens. > > What does stand-out regarding Smalltalk (and hence Pharo) is the superior developer experience furnished as a result of the true object system combined with a full graphical environment. > In addition to that, Pharo, specifically, provides advanced tools like Git integration, etc. > > But, are these things all that there are to be considered enough for highlighting the full inherent power of Pharo? > > Again, apologies if anyone found the subject line as well as the message body to be troll-ish. That has not been the intent. > > Kind regards, > > ~Mayuresh

Jan. 15, 2023

New to Pharo: Some questions

by Juan Cruz

Hello, I hope everyone is doing well. I am new to Pharo but not to programming. I have a background in Python, and Javascript mostly. I mostly use Python due to the data, plotting, and math libraries. But after toying a little with Pharo, the language I came to appreciate its beauty of it and how expressive the language is. I was wondering if there are libraries equivalent to Matplotlib, Pandas, Numpy, etc. I mostly apply Python to finance -in particular to quantitative finance. I read somewhere that top investment banks use Smalltalk as their secret weapon, so I'm sure that there are some users that have some insights to share on this subject. Thanks to all and all the best for this 2023. Greetings Juan P. Cruz

Jan. 15, 2023

Re: Sacrilegeous question : what are compelling use cases for Pharo

by Jupiter Jones

Hey Tim, > On 15 Jan 2023, at 4:59 am, Tim Mackinnon <tim(a)testit.works> wrote: > > In fact Boolean logic follows suit. This has far reaching implications which just lead to beautiful, compact, readable code. This is one of the first things I introduce new Smalltalkers to, typically after the question âHow do you do an if / then?â More often than not, it leads to a âmind-blownâ moment. They come to understand that C++, or Swift, or Java, or Dart, or whatever quasi-oop language they know has really only added a few OOP concepts to their development (and sometimes runtime) workflow. Understanding Smalltalk makes you a better developer in other languages, and makes it easier to learn new languages, since you clearly see the line between pure Object Oriented, and Language idiosyncrasies. > Finally, itâs just a joyful language, and so fun. It makes me smile just to write this. And when I read about how the community continues to strive make it even simpler - I punch the air. OMG Yes! I sometimes think of myself as a lazy programmer since the thought of having "to go back to" C++ or C# or Go makes me wince - Itâs just too much work and not enough fun! :) Iâd also add that once you adopt Smalltalk end-to-end you gain another significant advantage - no matter the role, your developers can actually support each other right down to the code. This isnât possible with the mish-mash of more âpopularâ languages and technologies. The entire development industry has largely become a sausage factory with jobs so specific in nature that they provide no joy, no diversity, and no clear path for advancement. Cheers, J PS The missing piece of the puzzle for Smalltalk ubiquity is a VM with native UI's on major platforms (MacOS / iOS / Linux / Android / Windows). If we had that, thereâd be no reason / excuse to use any other language :)

Jan. 14, 2023

Re: Sacrilegeous question : what are compelling use cases for Pharo

by Tim Mackinnon

This question comes up every few years - and itâs a good one to revisit, particularly in a new year. Youâve already had a few good answers - and Iâm sure you will get a few more. Of the languages you cite - Iâve tried 2 of them (C# and Swift) - and they are just too complicated. They donât share the elegance of Smalltalk, itâs such a compact, simple and approachable language. But itâs not just the language - itâs the tools which are all built and self hosted in the language as well , meaning they serve as great examples in how to do most things and also enable you to trivially get in there and extend your programming experience. Even deeper - they let you gradually understand how everything works - even down to the compiler and debugger. Then you understand there is no incomprehensible magic, itâs just straight forward code and messages. I rarely find average C# or Swift programmers who understand how things work in their language - itâs all voodoo and stack overflow for them, whereas most Smalltalkers after 6 months will understand how conditional logic works and many other lower level concepts. Itâs also not surprising that many computing innovations (more than most languages Iâd say) trace back to Smalltalk (and continue to do so). That simplicity and elegance just inspires creative thinking. While many languages have borrowed ideas from Smalltalk (which none of us mind) - they just got awkwardly bolted on. As an example - most languages now have closures , but the ethos of them is never properly embraced. For example, while we have exceptions - they dont get used as much as other languages because the convention (pervasive in all libraries) is to carry an error closure along with an operation - so on an error condition you can evaluate some code exactly where you need it vs winding back up the stack. Eg #at:ifAbsent: or #detect:ifNone: (and as previously mentioned, you can see how these work, and implement your own similar conventions in your models too). In fact Boolean logic follows suit. This has far reaching implications which just lead to beautiful, compact, readable code. I keep looking at new languages hoping to find the same elegance, but it seems that such simplicity is just not appreciated (I think lisp is one of the few that does - and itâs a cousin of Smalltalk). Finally, itâs just a joyful language, and so fun. It makes me smile just to write this. And when I read about how the community continues to strive make it even simpler - I punch the air. If you havenât tried it, I encourage you to dip a toe in the water. Even if you use other things, we all seem to find that we just come back to Smalltalk as itâs so deceptively addictive. Tim > On 14 Jan 2023, at 08:01, mayuresh(a)kathe.in via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > ï»¿Hello, > > This isn't a mail intended to troll this community. > > I am genuinely curious about what would be the type of use cases which would be exemplary for Pharo? > > Now-a-days, anything one could have accomplished solely with Smalltalk (and hence Pharo) can be accomplished with a number of modern programming languages and their associated frameworks, e.g. Google's Dart with Flutter, Apple Swift with SwiftUI, Microsoft's C# with WinUI. > And such languages and their associated frameworks are built from the ground-up for a particular platform, while Pharo does not have any such targets, which usually renders graphical applications built using Pharo to "look like" aliens. > > What does stand-out regarding Smalltalk (and hence Pharo) is the superior developer experience furnished as a result of the true object system combined with a full graphical environment. > In addition to that, Pharo, specifically, provides advanced tools like Git integration, etc. > > But, are these things all that there are to be considered enough for highlighting the full inherent power of Pharo? > > Again, apologies if anyone found the subject line as well as the message body to be troll-ish. That has not been the intent. > > Kind regards, > > ~Mayuresh

Jan. 14, 2023

Re: Sacrilegeous question : what are compelling use cases for Pharo

by Jupiter Jones

Hi Mayuresh, We use Smalltalk almost exclusively for all our server systems - database and applications. This includes POS applications and payment systems, SaaS applications, multiplayer games and IoT devices. We use GemStone Smalltalk [1] as our database and application server, and Pharo as the development tool. Our IoT devices are Raspberry Pi based and run Pharo IoT [2]. Also, most of these systems have a web based interface developed and served via Seaside [3] running in GemStone. We also have Mobile apps that connect to these systems that are developed in Swift, Dart or Java as users have come to expect native interfaces on their devices. Using these languages to create nothing but thin client like interfaces is quick and easy to maintain. Thatâs where they shine. Compared to Smalltalk these languages suck for writing anything more complex. Weâve had many recent graduates join the team with experience in Oracle or MongoDB or Redis or React or Node or any number of tools who are convinced (like most recent graduates are) that the tools with which they have experience are the âbest" and only serious way to move forward on projects. Typically, as a training exercise, we encourage them to build their first project in the tools they know, along side someone working with GemStone and Seaside. Without fail, a feature identical Seaside application (including a full suite of tests), is completed in a fraction of the time. Sometimes so much quicker that they choose to abandon their attempt and focus on learning Smalltalk and Seaside. FYI, Smalltalk is quite often found at the top-end-of-town. Itâs used on highly complex systems that contain substantial intellectual property, and often require confidentiality. Itâs considered a serious competitive advantage, and itâs where I find much of my work :) Youâre unlikely to get responses from these teams for obvious reasons, Hope this adds to your investigation. Cheers, J [1] https://gemtalksystems.com/ [2] https://www.pharoiot.org/ [3] https://www.seaside.st/ > On 14 Jan 2023, at 7:01 pm, mayuresh(a)kathe.in via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > Hello, > > This isn't a mail intended to troll this community. > > I am genuinely curious about what would be the type of use cases which would be exemplary for Pharo? > > Now-a-days, anything one could have accomplished solely with Smalltalk (and hence Pharo) can be accomplished with a number of modern programming languages and their associated frameworks, e.g. Google's Dart with Flutter, Apple Swift with SwiftUI, Microsoft's C# with WinUI. > And such languages and their associated frameworks are built from the ground-up for a particular platform, while Pharo does not have any such targets, which usually renders graphical applications built using Pharo to "look like" aliens. > > What does stand-out regarding Smalltalk (and hence Pharo) is the superior developer experience furnished as a result of the true object system combined with a full graphical environment. > In addition to that, Pharo, specifically, provides advanced tools like Git integration, etc. > > But, are these things all that there are to be considered enough for highlighting the full inherent power of Pharo? > > Again, apologies if anyone found the subject line as well as the message body to be troll-ish. That has not been the intent. > > Kind regards, > > ~Mayuresh

Jan. 14, 2023

Re: Sacrilegeous question : what are compelling use cases for Pharo

by Noury Bouraqadi

Hi Mayuresh, It's not about what you can do, but it's about how you do it. The language and the community culture have a huge influence on the way we build software. They have consequences not only at the implementation level, but also at the design level. The Pharo language and its main libraries are simple, pure OO, highly reflective, dynamic... So, when building software, we tend to adopt the same good practices. The Pharo powerful IDE addresses all development facets (coding, refactoring, debugging, versionning, ...). It makes it easy to make things right. This is what makes Pharo compelling. Noury On Jan 14 2023, at 9:01 am, mayuresh(a)kathe.in via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > Hello, > > This isn't a mail intended to troll this community. > I am genuinely curious about what would be the type of use cases which would be exemplary for Pharo? > Now-a-days, anything one could have accomplished solely with Smalltalk (and hence Pharo) can be accomplished with a number of modern programming languages and their associated frameworks, e.g. Google's Dart with Flutter, Apple Swift with SwiftUI, Microsoft's C# with WinUI. > And such languages and their associated frameworks are built from the ground-up for a particular platform, while Pharo does not have any such targets, which usually renders graphical applications built using Pharo to "look like" aliens. > > What does stand-out regarding Smalltalk (and hence Pharo) is the superior developer experience furnished as a result of the true object system combined with a full graphical environment. > In addition to that, Pharo, specifically, provides advanced tools like Git integration, etc. > > But, are these things all that there are to be considered enough for highlighting the full inherent power of Pharo? > Again, apologies if anyone found the subject line as well as the message body to be troll-ish. That has not been the intent. > Kind regards, > ~Mayuresh

Jan. 14, 2023

Sacrilegeous question : what are compelling use cases for Pharo

by mayuresh＠kathe.in

Hello, This isn't a mail intended to troll this community. I am genuinely curious about what would be the type of use cases which would be exemplary for Pharo? Now-a-days, anything one could have accomplished solely with Smalltalk (and hence Pharo) can be accomplished with a number of modern programming languages and their associated frameworks, e.g. Google's Dart with Flutter, Apple Swift with SwiftUI, Microsoft's C# with WinUI. And such languages and their associated frameworks are built from the ground-up for a particular platform, while Pharo does not have any such targets, which usually renders graphical applications built using Pharo to "look like" aliens. What does stand-out regarding Smalltalk (and hence Pharo) is the superior developer experience furnished as a result of the true object system combined with a full graphical environment. In addition to that, Pharo, specifically, provides advanced tools like Git integration, etc. But, are these things all that there are to be considered enough for highlighting the full inherent power of Pharo? Again, apologies if anyone found the subject line as well as the message body to be troll-ish. That has not been the intent. Kind regards, ~Mayuresh

Jan. 14, 2023

CfP: Journal of Systems and Software - Special Issue on Software Language Engineering

by Andrei Chis

Dear Colleagues, We invite submissions for the Journal of Systems and Software Special Issue on Â«Software Language EngineeringÂ». This special issue is related to the 2022 edition of the Software Language Engineering Conference (https://2022.splashcon.org/home/sle-2022?) but **it is open to all authors.** Details follow. -------------------------------------------------------------------------------------- Journal of Systems and Software Software Language Engineering Special Issue Guest Editors â Lola BurgueÃ±o, University of Malaga, Spain â Walter Cazzola, Professor, UniversitÃ degli Studi di Milano, Italy â Dimitris Kolovos, Professor, University of York, United Kingdom Special issue information: With the ubiquity of computers, software has become the dominating intellectual asset of our time. In turn, this software depends on software languages, namely the languages it is written in, the languages used to describe its environment, and the languages driving its development process. Given that everything depends on software and that software depends on software languages, it seems fair to say that for many years to come, everything will depend on software languages. Software language engineering (SLE) is the discipline of engineering languages and their tools required for the creation of software. It abstracts from the differences between programming languages, modeling languages, and other software languages, and emphasizes the engineering facet of the creation of such languages, that is, the establishment of the scientific methods and practices that enable the best results. While SLE is certainly driven by its meta-circular character (software languages are engineered using software languages), SLE is not self-satisfying: its scope extends to the engineering of languages for all and everything. This special issue will represent a further step in identification, definition and tooling of software languages. Topics of interest related to the special issue, 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 â Software Language Validation â Verification and formal methods for languages â Testing techniques for languages â Simulation techniques for languages â 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 â 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 â AI and ML language engineering (e.g., ML compiler testing, code classification) â 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) Manuscript submission information: Proposed Dates and Outcomes â Submission: 15 February 2023 â Notification to authors (first round): 15 April 2023 â Submission of revised papers (second round): 15 June 2023 â Notification to authors (second round): 15 August 2023 â Submission after second review: 15 October 2023 â Final acceptance: 15 November 2023 â Date of publication: 15 December 2023 Submission Guidelines The call for this special issue is an open call. We invite innovative research with a sound scientific or technological basis and validation. We accept submissions of original and previously unpublished manuscripts and we especially encourage the submission of revised and extended papers from the 15th ACM SIGPLAN International Conference on Software Language Engineering (SLE 2022). If a previous version of the manuscript has been published in a conference or journal, then authors must explicitly explain the novelty of this new submission and provide at least 30% new material. Surveys, literature reviews and mapping studies would not be considered as part of this special issue. All manuscripts and any supplementary material should be submitted through the Elsevier Editorial System at https://www.editorialmanager.com/jssoftware/default1.aspx. Follow the submission instructions given on this site. During the submission process, select the article type "VSI:SLE" from the "Choose Article Type" pull-down menu. All submissions must adhere to the general principles of the Journal of Systems and Software articles. Submissions have to be prepared according to the Guide for Authors, available on the journal website, and must follow the format specified in the JSS Guide for Authors https://www.elsevier.com/journals/journal-of-systems-and-software/0164-1212…. For more information about the special issue, please contact the guest editors.

Jan. 13, 2023

Re: MIDI Interface?

by StÃ©phane Ducasse

Hi antoine is not working with us anymore. We are looking for another student. I think that it would be great that someone looks at what he did. S > On 13 Jan 2023, at 03:08, Stewart MacLean <stewart(a)xtra.co.nz> wrote: > > Hi All, > > Prompted by a recent chat with Domenico on Discord, I've dusted off the Midi package I was working on and added some background notes, getting started etc. I've yet to get it to Git, but please find it attached. > > Thank you all very much for your assistance with the development of this package - I hope it may be useful for the Pharo community! > > Cheers, > > Stewart > > On Sat, May 21, 2022 at 1:07 AM Stewart MacLean <stewart(a)xtra.co.nz <mailto:stewart@xtra.co.nz>> wrote: >> Hi Antoine, >> >> For some reason your message below didn't come to me, I just "stumbled" across it. >> >> Thanks for the link to your work, it looks interesting. >> >> For now, I'm focused on the "plumbing", and this will be a great help with getting the FFI library going and I'll share my thoughts along the way! >> >> I've just started porting my dusty VisualWorks MidiAccessLayer that utilises PortMidi and RtMidi. Once I've got it in shape I'll be glad to share it with you. >> >> Cheers, >> >> Stewart >> >> Hello Stewart, >> >> Indeed I am working on PortMidi C library binding on Pharo. >> >> For now, the code I wrote contains an object that represents the C library and you can use its methods to try some MIDI stuff. I added several layers to these methods to make it easier to use. You can also create what I call scores which are sequences of notes and play them either separately or add them in an object called Prestation that is able to play several scores at the same time. >> >> You can find the code on GitHub : https://github.com/pharo-contributions/pharo-sound . >> >> Do not hesitate to tell me what you think about it ! >> >> Antoine >> >> >> On Thu, May 19, 2022 at 2:23 AM stephane ducasse <stephane.ducasse(a)inria.fr <mailto:stephane.ducasse@inria.fr>> wrote: >>> Antoine can you reply to Stewart? >>> >>> >>>> On 16 May 2022, at 01:03, Stewart MacLean <stewart(a)xtra.co.nz <mailto:stewart@xtra.co.nz>> wrote: >>>> >>>> Hi Santiago, >>>> >>>> Thanks for this. My primary interest at the moment is interfacing with Midi. >>>> >>>> The sound stuff looks interesting, even if it is not quite my cup of tea music wise :) >>>> >>>> How far has your student got with the PortMidi bindings? As a first step, as I can get a precompiled library via homebrew I thought I'd start by migrating my VisualWorks PortMidi bindings - are they able to share this to get me started? >>>> >>>> I have built a Midi Access Layer (in VisualWorks) which layers over both RtMidi and PortMidi, which I had working on Windows quite a while ago. This maybe useful? >>>> >>>> Cheers, >>>> >>>> Stewart >>>> >>>> On Sun, May 15, 2022 at 11:48 PM Santiago Bragagnolo <santiagobragagnolo(a)gmail.com <mailto:santiagobragagnolo@gmail.com>> wrote: >>>>> Hi all! >>>>> In inria we are working with an student on the bindings of PortMIDI in Pharo, and having some exchanges with an italian Dj that uses pharo for live-performances (https://www.youtube.com/watch?v=yBK0UpalBfk) >>>>> >>>>> We are trying to recover, in the long term the things in https://github.com/pharo-contributions/Sound, since there are awesome! >>>>> >>>>> If you have ideas feel free to share them! >>>>> >>>>> Santiago >>>>> >>>>> El dom, 15 may 2022 a las 6:07, Stewart MacLean (<stewart(a)xtra.co.nz <mailto:stewart@xtra.co.nz>>) escribiÃ³: >>>>>> Hi all, >>>>>> >>>>>> Just wondering what the current state of interfaces to MIDI within Pharo are? >>>>>> >>>>>> I gather that there was one (SoundScores that used primitives), but that seems to have disappeared... >>>>>> >>>>>> Cheers, >>>>>> >>>>>> Stewart >>> > <SIM-Midi-Access-Layer.st>

Jan. 13, 2023

This week (2/2023) on the Pharo Issue Tracker

by Marcus Denker

42 PRs merged, 40 Issues closed Features ======= - RubTextEditor/TextEditor: Make ctrl+backspace delete the previous word #12096 https://github.com/pharo-project/pharo/pull/12096 - Add source and target labels to SpChooserPresenter ( #1341) #1342 https://github.com/pharo-spec/Spec/pull/1342 Git/Iceberg ============ - add a manual way to add/remove tags #1657 https://github.com/pharo-vcs/iceberg/pull/1657 - add default tag "system" to bootstrap registered projects #12303 https://github.com/pharo-project/pharo/pull/12303 - fix bad categorizations #1655 https://github.com/pharo-vcs/iceberg/pull/1655 - Adapt to latest spec2 pass2 #1632 https://github.com/pharo-vcs/iceberg/pull/1632 Refactoring Engine ================== - Cleaning RB issues #12151 https://github.com/pharo-project/pharo/pull/12151 - Refactorings cleanup #12256 https://github.com/pharo-project/pharo/pull/12256 Fixes ===== - Fix refactoring using old class def #12195 https://github.com/pharo-project/pharo/pull/12195 - remove ByteLayout from FFIBackend and children #12225 https://github.com/pharo-project/pharo/pull/12225 - 12289-Refactoring-Tests-are-failling-when-using-Fluid-syntax #12290 https://github.com/pharo-project/pharo/pull/12290 - Fix hasSelector:specialSelectorIndex: on FFI methods that are compiled #12305 https://github.com/pharo-project/pharo/pull/12305 - 12300-Compiler-is-slow-with-string-literals-containing-exclamation-marks #12306 https://github.com/pharo-project/pharo/pull/12306 Cleanups ======== - 18 whitespace cleanups like Cleanup: Condense CodeImport packages #12229 https://github.com/pharo-project/pharo/pull/12229 - 5 remove return out of isTrue:ifFalse: lke extract return from ifTrue:ifFalse: expression in Number floor #12292 https://github.com/pharo-project/pharo/pull/12292 - remove #Numeric from source code. #12265 https://github.com/pharo-project/pharo/pull/12265 - 12307 remove gt pragma #12308 https://github.com/pharo-project/pharo/pull/12308 - Unncessary class RBMissingOpenerErrorNode #12313 https://github.com/pharo-project/pharo/pull/12313 - Class RBShortAssignmentToken is not needed anymore #12315 https://github.com/pharo-project/pharo/pull/12315 Comments ======== - Improving layoutFrame comments and add examples (fixes #12259) #12260 https://github.com/pharo-project/pharo/pull/12260 - extract comments as runnable example in Number>>#// #12263 https://github.com/pharo-project/pharo/pull/12263 - use isInstanceSide message in example #12270 https://github.com/pharo-project/pharo/pull/12270

Jan. 13, 2023