- Pharo-dev - lists.pharo.org

Woden download from Github error

by Aik-Siong Koh

Hi: I opened Pharo 9.0 - 64bit image. Executed Metacello new baseline: 'WodenEngine'; repository: 'github://woden-engine/woden'; load I got the following error: NotFound: revspec 'master' not found Please advise. Thanks, Aik-Siong Koh

May 20, 2023

Re: Fun with CleanBlocks or: Speeding up Dictionary>>#at:

by Tim Mackinnon

I love these little discussions/examples that you share... things you take for granted have subtle impacts that are worth reasoning about. Whenever I read them, it definitely improves my understanding and makes me a better programmer. Thanks Markus. Tim On Fri, 19 May 2023, at 12:01 PM, Marcus Denker wrote: > Dictionary lookup is used a lot. Let's look at Dictionary>>#at: > > > at: key > "Answer the value associated with the key." > ^ self at: key ifAbsent: [self errorKeyNotFound: key] > > > The method looks simple and at a first glance, there are no obvious problems. > > But if we look at it again, we see that for every execution of #at:, > the block [self errorKeyNotFound: key] > has to be created. The method stores a CompiledBlock in the literals, > and a bytecode "create block" creates > the block: > > ``` > (Dictionary>>#at:) symbolic > > "'41 <4C> self > 42 <40> pushTemp: 0 > 43 <40> pushTemp: 0 > 44 <F9 00 01> fullClosure:a CompiledBlock: [self errorKeyNotFound: key] > NumCopied: 1 > 47 <A1> send: at:ifAbsent: > 48 <5C> returnTop'" > ``` > > This happens at *every* execution of #at:, even though the block that > we spend time to create will never > be executed at runtime (outside of real errors). > > If you look at the rest of the code path of #at: in a Dictionary, it is > carefully written to avoid block creation > by using optimized contructs (ifTrue: and friends). > > Could clean blocks help? Clean blocks are blocks that only use data > that the compiler knows at compile time, > thus we can create a CleanBlockClosure (which has the CompiledBlock) > and store *that* as a Literal. > > This then would mean that we could just use as fast pushLiteral: to > push the block, no creation at runtime needed. > > Clean blocks are not yet enabled by default, but we can use a compiler > option pragma to enable them just for this > method: > > ``` > <compilerOptions: #(+ optionCleanBlockClosure)> > ``` > > The problem is that the block references both "self" and the key to be > able to show a nice error message. > Referencing either one make the block not clean. > > Could we change the block to be clean? I guess we could not refer self > and inline the method #errorKeyNotFound: > (knowing the instance is not that important for logging the error in > production, for example). But we do want > to know the key that is not found, it really simplifies debugging > especially if you have to look at log files. > > If we closely look at the block: we know a bit more about it and how it > is used. We know that if it gets evaluated, > that evaluation will *always* happen with the homeContext of the block > on the stack, as it is will always be #at:ifAbsent: > that evaluates that block. > > And in that case, there is a trick that we can do: we can use > reflection to read the needed values via the stack. > > You might not be aware, but the debugger needs some quite interesting > features from the reflective layer of the system to provide > the user experience that you take for granted (and that feels trivial). > Imagine a block like that: > > ``` > tt > > | temp1 temp2 | > temp1 := 1. > temp2 := 2. > > self class methods do: [ :each | self halt. each with: temp1 ]. > ^ temp2 > ``` > > > The block does not reference temp2, so it actually is created as a > block that does not know temp2 at all. temp2 is not accessibe from the > block or it's context. > Yet, when debugging, you want to just be able to write temp2 in the > block and eval it (without saving the method), as *if* you would access > the temp in this block and recompile, the compiler would compile a > different block that would know temp2. > > So the reflective API of Context (and the infrastructure of reading > Variables reflectively), is build in a way that #readVariableNamed: > will > use the stack to find the value of temps that are not available in the > block context, but could be available if they would be referenced > statically. > > And if you think about it, we have just a case like that here, in > reverse: if we would use #readVariableNamed: on the context to read the > argument, > the compiler would not see a read of "key", thus compile a block that > does not have that temp available. And if we then read "self" via > thisContext, too, > the compiler sees a block that it can compile as a clean block: > > > at: key > "Answer the value associated with the key." > > <compilerOptions: #(+ optionCleanBlockClosure)> > > ^ self at: key ifAbsent: [ > > "this block is never executed, yet we pay runtime cost to create it > if it is a full block. > We use instead the reflective API to read the argument and receiver > via the stack, making > the block clean. > > We enable cleanBlocks for this method by setting > optionCleanBlockClosure as it is not yet > enabled by default" > > KeyNotFound signalFor: (thisContext readVariableNamed: #key) in: > thisContext sender receiver > "This is equivalent to: > self errorKeyNotFound: key" > ] > > > Let's look at the printed symbolic bytecode: > > > ``` > Dictionary>>#at:) symbolic > > "'41 <4C> self > 42 <40> pushTemp: 0 > 43 <20> pushConstant: [ > > "this block is never executed, yet we pay runtime cost to create it > if it is a full block. > We use instead the reflective API to read the argument and receiver > via the stack, making > the block clean. > > We enable cleanBlocks for this method by setting > optionCleanBlockClosure as it is not yet > enabled by default" > > KeyNotFound signalFor: (thisContext readVariableNamed: #key) in: > thisContext sender receiver > "This is equivalent to: > self errorKeyNotFound: key" > ] > 44 <A1> send: at:ifAbsent: > 45 <5C> returnTop'" > ``` > > you see that it now uses pushConstant: to push the pre-compiled > CleanBlockClosure, which is *much* faster. > > A very naive benchmark using a fairly large Dictionary (Smalltalk globals): > > ``` > [Smalltalk globals at: #Object] bench > > 8591996.801/7040335.266 "1.220395972119888" > ``` > > Shows a speedup of ~20%, which is qute a lot! > > Of course, this is a hack. For one, it just solves this for this one > case. And we do not want to add code like > that everywhere. And real world impact of speed will be quite limited > due to that (it just speeds up > Dictionary>#at:) > > The alternative would be to inline #at:ifAbsent: This inlining, due to > the existing subclasses, leads to quite some > needed refactorings, and has the same problem of being a solution for > this problem in this one place. > > The real solution in the long term is a JIT that removes blocks like > that by inlining automatically for the code it executes, > while not changing the image level code at all. This would then solve > this for all similar cases everywhere all at once. > > But the nice aspect of the hack is: it is local (touches just this one > method), gives us some speedup now and will be > trivially removable when we deploy a better solution in the future. > > But the code is quite ugly and indeed relies on reflection... which > maybe for Dictionary>>#at: is not that nice > (e.g. if you want to create a minimal image without reflection) > > But it is save to add this to your own image, it works in Pharo11 and > Pharo12 and I guess even in Pharo10 > (not tested there). > > Marcus

May 19, 2023

This week (20/2023) on the Pharo Issue Tracker.

by Marcus Denker

This week, we continued the work on Pharo12. #Fixes - Drop use of Paragraph from #drawOn: in ToggleWithSymbolMenuItemShortcut to fix menu item alignment #13764 https://github.com/pharo-project/pharo/pull/13764 - 13657-With-CleanBlocks-enabled-tests-fail-when-trying-to-Fuel-out-stack #13763 https://github.com/pharo-project/pharo/pull/13763 - Adjust icon and key text spacing in ToggleMenuItemMorph #13722 https://github.com/pharo-project/pharo/pull/13722 # Features - add object to represent the Native Window #13566 https://github.com/pharo-project/pharo/pull/13566 - Add menu items âIndentâ and âOutdentâ to the menu built through #menuOn: in RubSmalltalkCodeMode #13714 https://github.com/pharo-project/pharo/pull/13714 # Compiler - Remove Object bindingOf: and hasBindingOf: #13736 https://github.com/pharo-project/pharo/pull/13736 https://github.com/pharo-spec/Spec/pull/1392 - Compiler: remove #lookupVar:declare: #13737 https://github.com/pharo-project/pharo/pull/13737 https://github.com/pharo-spec/Spec/pull/1390 - 13723-Binding-for-variable-in-Playground-is-nil-after-assigning-a-number-to-it #13739 https://github.com/pharo-project/pharo/pull/13739 # Protocols - Method announcements should use real protocols #13730 https://github.com/pharo-project/pharo/pull/13730 - Clean the way to get the selectors in a protocol #13759 https://github.com/pharo-project/pharo/pull/13759 - Inline protocol removal from ClassOrganization #13753 https://github.com/pharo-project/pharo/pull/13753 - Diver cleanings around protocols #13749 https://github.com/pharo-project/pharo/pull/13749 - Inline ClassOrganization>>#removeElement: in ClassDescription #13748 https://github.com/pharo-project/pharo/pull/13748 - Implement ClassDescription>>#protocolNameOfSelector: #13728 https://github.com/pharo-project/pharo/pull/13728 - Move #protocolOfSelector: to ClassDescription #13711 https://github.com/pharo-project/pharo/pull/13711 - Improve removal of protocols and add tests #13692 https://github.com/pharo-project/pharo/pull/13692 # Refactoring Engine - Refactoring RBRefactoringWarning and RBRefactoringError #13367 https://github.com/pharo-project/pharo/pull/13367 # Cleanup - Update 01-loadMetacello.st: MetacelloPharoCommonPlatform #13762 https://github.com/pharo-project/pharo/pull/13762 - update-dependencies #13754 https://github.com/pharo-project/pharo/pull/13754 - 10069-Review-NullTextStyler #13752 https://github.com/pharo-project/pharo/pull/13752 - 12444-cleanup-todo-from-testClassSideInitializeMethodNeedsToBeInClassInitializationProtocol #13750 https://github.com/pharo-project/pharo/pull/13750 - Cleanup-MetacelloPharoPlatform #13738 https://github.com/pharo-project/pharo/pull/13738 https://github.com/pharo-project/pharo/pull/13747 https://github.com/pharo-project/pharo/pull/13716 - Move-isObservableSlot #13745 https://github.com/pharo-project/pharo/pull/13745 https://github.com/pharo-spec/Spec/pull/1393 - Add class comments to mocks #13743 https://github.com/pharo-project/pharo/pull/13743 - Class-Deprecate-classComment #13744 https://github.com/pharo-project/pharo/pull/13744 - Cleanup TheManifestBuilder #13742 https://github.com/pharo-project/pharo/pull/13742 - finally remove AbstractTool #13715 https://github.com/pharo-project/pharo/pull/13715 https://github.com/pharo-spec/NewTools/pull/523 - Remove dead code in session manager #13729 https://github.com/pharo-project/pharo/pull/13729 - Fix deprecated call #13710 https://github.com/pharo-project/pharo/pull/13710 - extract return from ifNilifNotNil in ChangeSorterModel #516 https://github.com/pharo-spec/NewTools/pull/516 - Do not listen to method recategorization in MessageBrowser #524 https://github.com/pharo-spec/NewTools/pull/524

May 19, 2023

Fun with CleanBlocks or: Speeding up Dictionary>>#at:

by Marcus Denker

Dictionary lookup is used a lot. Let's look at Dictionary>>#at: at: key "Answer the value associated with the key." ^ self at: key ifAbsent: [self errorKeyNotFound: key] The method looks simple and at a first glance, there are no obvious problems. But if we look at it again, we see that for every execution of #at:, the block [self errorKeyNotFound: key] has to be created. The method stores a CompiledBlock in the literals, and a bytecode "create block" creates the block: ``` (Dictionary>>#at:) symbolic "'41 <4C> self 42 <40> pushTemp: 0 43 <40> pushTemp: 0 44 <F9 00 01> fullClosure:a CompiledBlock: [self errorKeyNotFound: key] NumCopied: 1 47 <A1> send: at:ifAbsent: 48 <5C> returnTop'" ``` This happens at *every* execution of #at:, even though the block that we spend time to create will never be executed at runtime (outside of real errors). If you look at the rest of the code path of #at: in a Dictionary, it is carefully written to avoid block creation by using optimized contructs (ifTrue: and friends). Could clean blocks help? Clean blocks are blocks that only use data that the compiler knows at compile time, thus we can create a CleanBlockClosure (which has the CompiledBlock) and store *that* as a Literal. This then would mean that we could just use as fast pushLiteral: to push the block, no creation at runtime needed. Clean blocks are not yet enabled by default, but we can use a compiler option pragma to enable them just for this method: ``` <compilerOptions: #(+ optionCleanBlockClosure)> ``` The problem is that the block references both "self" and the key to be able to show a nice error message. Referencing either one make the block not clean. Could we change the block to be clean? I guess we could not refer self and inline the method #errorKeyNotFound: (knowing the instance is not that important for logging the error in production, for example). But we do want to know the key that is not found, it really simplifies debugging especially if you have to look at log files. If we closely look at the block: we know a bit more about it and how it is used. We know that if it gets evaluated, that evaluation will *always* happen with the homeContext of the block on the stack, as it is will always be #at:ifAbsent: that evaluates that block. And in that case, there is a trick that we can do: we can use reflection to read the needed values via the stack. You might not be aware, but the debugger needs some quite interesting features from the reflective layer of the system to provide the user experience that you take for granted (and that feels trivial). Imagine a block like that: ``` tt | temp1 temp2 | temp1 := 1. temp2 := 2. self class methods do: [ :each | self halt. each with: temp1 ]. ^ temp2 ``` The block does not reference temp2, so it actually is created as a block that does not know temp2 at all. temp2 is not accessibe from the block or it's context. Yet, when debugging, you want to just be able to write temp2 in the block and eval it (without saving the method), as *if* you would access the temp in this block and recompile, the compiler would compile a different block that would know temp2. So the reflective API of Context (and the infrastructure of reading Variables reflectively), is build in a way that #readVariableNamed: will use the stack to find the value of temps that are not available in the block context, but could be available if they would be referenced statically. And if you think about it, we have just a case like that here, in reverse: if we would use #readVariableNamed: on the context to read the argument, the compiler would not see a read of "key", thus compile a block that does not have that temp available. And if we then read "self" via thisContext, too, the compiler sees a block that it can compile as a clean block: at: key "Answer the value associated with the key." <compilerOptions: #(+ optionCleanBlockClosure)> ^ self at: key ifAbsent: [ "this block is never executed, yet we pay runtime cost to create it if it is a full block. We use instead the reflective API to read the argument and receiver via the stack, making the block clean. We enable cleanBlocks for this method by setting optionCleanBlockClosure as it is not yet enabled by default" KeyNotFound signalFor: (thisContext readVariableNamed: #key) in: thisContext sender receiver "This is equivalent to: self errorKeyNotFound: key" ] Let's look at the printed symbolic bytecode: ``` Dictionary>>#at:) symbolic "'41 <4C> self 42 <40> pushTemp: 0 43 <20> pushConstant: [ "this block is never executed, yet we pay runtime cost to create it if it is a full block. We use instead the reflective API to read the argument and receiver via the stack, making the block clean. We enable cleanBlocks for this method by setting optionCleanBlockClosure as it is not yet enabled by default" KeyNotFound signalFor: (thisContext readVariableNamed: #key) in: thisContext sender receiver "This is equivalent to: self errorKeyNotFound: key" ] 44 <A1> send: at:ifAbsent: 45 <5C> returnTop'" ``` you see that it now uses pushConstant: to push the pre-compiled CleanBlockClosure, which is *much* faster. A very naive benchmark using a fairly large Dictionary (Smalltalk globals): ``` [Smalltalk globals at: #Object] bench 8591996.801/7040335.266 "1.220395972119888" ``` Shows a speedup of ~20%, which is qute a lot! Of course, this is a hack. For one, it just solves this for this one case. And we do not want to add code like that everywhere. And real world impact of speed will be quite limited due to that (it just speeds up Dictionary>#at:) The alternative would be to inline #at:ifAbsent: This inlining, due to the existing subclasses, leads to quite some needed refactorings, and has the same problem of being a solution for this problem in this one place. The real solution in the long term is a JIT that removes blocks like that by inlining automatically for the code it executes, while not changing the image level code at all. This would then solve this for all similar cases everywhere all at once. But the nice aspect of the hack is: it is local (touches just this one method), gives us some speedup now and will be trivially removable when we deploy a better solution in the future. But the code is quite ugly and indeed relies on reflection... which maybe for Dictionary>>#at: is not that nice (e.g. if you want to create a minimal image without reflection) But it is save to add this to your own image, it works in Pharo11 and Pharo12 and I guess even in Pharo10 (not tested there). Marcus

May 19, 2023

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

by Marcus Denker

We released Pharo11 this week! see https://www.pharo.org/news/pharo11-released.html # Pharo 11 - Fix welcomebrowser version #13691 https://github.com/pharo-project/pharo/pull/13691 - Backport fixe #13663: Enabling the setting âShow lines numbers for all browsers #13665 https://github.com/pharo-project/pharo/pull/13665 - fix iceberg version for Pharo 11 #13655 https://github.com/pharo-project/pharo/pull/13655 - fix a bug with cmd+g usage #517 https://github.com/pharo-spec/NewTools/pull/517 - change spotter selection paste default #519 https://github.com/pharo-spec/NewTools/pull/519 # Pharo 12 ## Fixes - Improve some error logging #13689 https://github.com/pharo-project/pharo/pull/13689 - Enabling the setting âShow lines numbers for all browsersâ only shows line numbers for the first method selected in a class #13663 https://github.com/pharo-project/pharo/issues/13663 ## Variables - Allow-Slots-Shadow-PseudoVariables #13704 https://github.com/pharo-project/pharo/pull/13704 - Simplify ReservedVariable: #styleNameIn and remove #nameIsReserved: #13701 https://github.com/pharo-project/pharo/pull/13701 - ReservedVariable: No need for Singleton #13688 https://github.com/pharo-project/pharo/pull/13688 - Added thisProcess pseudovariable using existing bytecode. #13661 https://github.com/pharo-project/pharo/pull/13661 ## SystemOrganizer / RPackage - Remove dead code in RPackageOrganizer default instance #13660 https://github.com/pharo-project/pharo/pull/13660 - Reduces the references to RPackageOrganizer class>>default #13666 https://github.com/pharo-project/pharo/pull/13666 - Move system organizer to RPackage and remove references #13677 https://github.com/pharo-project/pharo/pull/13677 - Remove SystemOrganizer #13690 https://github.com/pharo-project/pharo/pull/13690 - Use Smalltalk organization in DependencyAnalyzer #13671 https://github.com/pharo-project/pharo/pull/13671 ## Protocols / Categories - Do not classify silently methods #13650 https://github.com/pharo-project/pharo/pull/13650 - Start protocol announcements testing + add feature to Announcer #13649 https://github.com/pharo-project/pharo/pull/13649 - Deprecate ProtocolRenamed #13659 https://github.com/pharo-project/pharo/pull/13659 - Small cleanup on protocol cleaning #13642 https://github.com/pharo-project/pharo/pull/13642 - Rename Protocol class>>#name: into #named: #13670 https://github.com/pharo-project/pharo/pull/13670 - Use real protocol in recategorization mecanism #13669 https://github.com/pharo-project/pharo/pull/13669 - Introduce ClassDescription>>#protocolNames and start using it #13658 https://github.com/pharo-project/pharo/pull/13658 - Add some tests on protocol announcements #13706 https://github.com/pharo-project/pharo/pull/13706 - Removal of nonexisting protocol should not announce anything #13702 https://github.com/pharo-project/pharo/pull/13702 ## Code Completion - Completion autoclose menu #13647 https://github.com/pharo-project/pharo/pull/13647 - Completion: improve completion on super #13679 https://github.com/pharo-project/pharo/pull/13679 - Completion: replacement put caret at the right place #13683 https://github.com/pharo-project/pharo/pull/13683 - Completion mini fixes #13696 https://github.com/pharo-project/pharo/pull/13696 - Basic type analysis for better completion #13687 https://github.com/pharo-project/pharo/pull/13687 - More type analysis #13697 https://github.com/pharo-project/pharo/pull/13697 - CompletionEngine do not automatically open empty completion menus #13705 https://github.com/pharo-project/pharo/pull/13705 - NECPreferences remove leftover of captureNavigationKeys #13703 https://github.com/pharo-project/pharo/pull/13703 - Completion: better update #13700 https://github.com/pharo-project/pharo/pull/13700 - Completion browse with Ctrl-B #13699 https://github.com/pharo-project/pharo/pull/13699 ## Cleanups - Clean some code using better condition branches #13668 https://github.com/pharo-project/pharo/pull/13668 - Remove some duplication in image cleaner #13676 https://github.com/pharo-project/pharo/pull/13676 - Message: rename ivar "args" to "arguments #13654 https://github.com/pharo-project/pharo/pull/13654 - Cleanup: Metacello-Platform #13682 https://github.com/pharo-project/pharo/pull/13682 - remove MetacelloPharo30Platform from 01-loadMetacello.st #13684 https://github.com/pharo-project/pharo/pull/13684 - Clean monticello class definition management #13680 https://github.com/pharo-project/pharo/pull/13680

May 15, 2023

Re: [Pharo-users] [ANN] Pharo 11 Released !

by Norbert Hartl

Hurray! Congats to all of you for the hard work once more to bring it to life. And I like the picture that does not lie about us not having HiDPI ð Now I need to upgrade all of my stuff again !! norbert > Am 11.05.2023 um 13:39 schrieb Esteban Lorenzano <estebanlm(a)netc.eu>: > > Dear Pharo users and dynamic language lovers: > > We have released Pharo <https://pharo.org/> version 11! > What is Pharo? > > Pharo is a pure object-oriented programming language and a powerful environment focused on simplicity and immediate feedback. > > > > Simple & powerful language: No constructors, no types declaration, no interfaces, no primitive types. Yet a powerful and elegant language with a full syntax fitting in one postcard! Pharo is objects and messages all the way down. > Live, immersive environment: Immediate feedback at any moment of your development: Developing, testing, debugging. Even in production environments, you will never be stuck in compiling and deploying steps again! > Amazing debugging experience: Pharo environment includes a debugger unlike anything you've seen before. It allows you to step through code, restart the execution of methods, create methods on the fly, and much more! > Pharo is yours: Pharo is made by an incredible community, with more than 100 contributors for the last revision of the platform and hundreds of people constantly contributing with frameworks and libraries. > Fully open-source: Pharo full stack is released under MIT <https://opensource.org/licenses/MIT> License and available on GitHub <https://github.com/pharo-project/pharo> > ... more on the Pharo Features page <http://www.pharo.org/features>. > > In this iteration of Pharo, we continue working on our objectives of improvement, clean-up and modularization. Also, we included a number of usability and speed improvements. A complete list of changes and improvements is available in our Changelog <https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo110Chang…> > Some highlights of this amazing version: > Highlights > > Tools > Iceberg (the git client/VCS control tool) has received a lot of tweaks and fixes to work better with GitHub and other Git services. > Our debugger now incorporates lots of tweaks and notably the capability of adding bindings in the context interaction model. > The is a new implementation of rewrite tools and improved refactoring support. > There is a new tool: The Document Browser, which presents Microdown (markdown compatible) documents placed on the web or locally. > New Tools presented in Calypso (the System Browser) and additional extended Inspectors. > All versions of NewTools, Spec, Roassal and Microdown have been updated with their respective bug fixes and improvements. > System > Extended Full Blocks and Constant Clock closures support. > Additional Inlining and optimizations > Bug Fixes and Clean up. > Ephemeron Finalization support. > Virtual machine > Ephemerons Production Ready. > Initial support for Single-Instruction Multiple-Data (SIMD). > Third-Party Dependency Update (Newer versions, Graphic Libraries using Hardware Acceleration). > Clean Ups: Remove lots of old code, notably old experiments, and dead code. > Development Effort > > This new version is the result of 1412 Pull Requests integrated just in the Pharo repository. We have closed 972 issues and received contributions from more than 70 different contributors. We have also a lot of work in the separate projects that are included in each Pharo release: > > http://github.com/pharo-spec/NewTools <https://github.com/pharo-spec/NewTools> > http://github.com/pharo-spec/NewTools-DocumentBrowser <https://github.com/pharo-spec/NewTools-DocumentBrowser> > http://github.com/pharo-spec/Spec <https://github.com/pharo-spec/Spec> > http://github.com/pharo-vcs/Iceberg <https://github.com/pharo-vcs/Iceberg> > http://github.com/ObjectProfile/Roassal3 <https://github.com/ObjectProfile/Roassal3> > http://github.com/pillar-markup/Microdown <https://github.com/pillar-markup/Microdown> > http://github.com/pillar-markup/BeautifulComments <https://github.com/pillar-markup/BeautifulComments> > http://github.com/pharo-project/pharo-vm <https://github.com/pharo-project/pharo-vm> > Contributors > > We always say Pharo is yours. It is yours because we made it for you, but most importantly because it is made by the invaluable contributions of our great community (yourself). A large community of people from all around the world contributed to Pharo 11.0 by making pull requests, reporting bugs, participating in discussion threads, providing feedback, and a lot of helpful tasks in all our community channels. Thank you all for your contributions. > > The Pharo Team > > Discover Pharo: https://pharo.org/features > Try Pharo: http://pharo.org/download > Learn Pharo: http://pharo.org/documentation

May 12, 2023

Re: Pharo contribution Jenkins end of service

by Guillermo Polito

Thanks Christophe! > El 11 may. 2023, a las 11:32, Christophe Demarey <christophe.demarey(a)inria.fr> escribiÃ³: > > Hi all, > > Some years ago, we provided a Jenkins instance to check the health / quality of projects that are not in Pharo core but important for the community: > https://ci.inria.fr/pharo-contribution/ <https://ci.inria.fr/pharo-contribution/> > > Since, we moved to GitHub and GitHub actions are mainly used to achieve the same goal. Therefore there is no more reason to keep this service. Thatâs why we decided to stop the Pharo contribution Jenkins on 12th June 2023. > If you need to save some data (job artefacts, job setup), let us know. The server is now up but it has not been updated since a while and can stop working from time to time. > > On 12th June 2023, we will shutdown the server and all data will be removed. > > The Pharo team.

May 12, 2023

Re: [ANN] Pharo 11 Released !

by Guillermo Polito

++1 !! :) > El 11 may. 2023, a las 14:02, Gabriel Cotelli <g.cotelli(a)gmail.com> escribiÃ³: > > Congratulations on the new release. Now it's time to adapt the libraries and check that continue working with this version :P > > I think you need to update also https://github.com/pharo-project/pharo/releases <https://github.com/pharo-project/pharo/releases> to tag the commit used to produce the released image. > > Regards, > Gabriel > > On Thu, May 11, 2023 at 8:39â¯AM Esteban Lorenzano <estebanlm(a)netc.eu <mailto:estebanlm@netc.eu>> wrote: > Dear Pharo users and dynamic language lovers: > > We have released Pharo <https://pharo.org/> version 11! > What is Pharo? > > Pharo is a pure object-oriented programming language and a powerful environment focused on simplicity and immediate feedback. > > > > Simple & powerful language: No constructors, no types declaration, no interfaces, no primitive types. Yet a powerful and elegant language with a full syntax fitting in one postcard! Pharo is objects and messages all the way down. > Live, immersive environment: Immediate feedback at any moment of your development: Developing, testing, debugging. Even in production environments, you will never be stuck in compiling and deploying steps again! > Amazing debugging experience: Pharo environment includes a debugger unlike anything you've seen before. It allows you to step through code, restart the execution of methods, create methods on the fly, and much more! > Pharo is yours: Pharo is made by an incredible community, with more than 100 contributors for the last revision of the platform and hundreds of people constantly contributing with frameworks and libraries. > Fully open-source: Pharo full stack is released under MIT <https://opensource.org/licenses/MIT> License and available on GitHub <https://github.com/pharo-project/pharo> > ... more on the Pharo Features page <http://www.pharo.org/features>. > > In this iteration of Pharo, we continue working on our objectives of improvement, clean-up and modularization. Also, we included a number of usability and speed improvements. A complete list of changes and improvements is available in our Changelog <https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo110Chang…> > Some highlights of this amazing version: > Highlights > > Tools > Iceberg (the git client/VCS control tool) has received a lot of tweaks and fixes to work better with GitHub and other Git services. > Our debugger now incorporates lots of tweaks and notably the capability of adding bindings in the context interaction model. > The is a new implementation of rewrite tools and improved refactoring support. > There is a new tool: The Document Browser, which presents Microdown (markdown compatible) documents placed on the web or locally. > New Tools presented in Calypso (the System Browser) and additional extended Inspectors. > All versions of NewTools, Spec, Roassal and Microdown have been updated with their respective bug fixes and improvements. > System > Extended Full Blocks and Constant Clock closures support. > Additional Inlining and optimizations > Bug Fixes and Clean up. > Ephemeron Finalization support. > Virtual machine > Ephemerons Production Ready. > Initial support for Single-Instruction Multiple-Data (SIMD). > Third-Party Dependency Update (Newer versions, Graphic Libraries using Hardware Acceleration). > Clean Ups: Remove lots of old code, notably old experiments, and dead code. > Development Effort > > This new version is the result of 1412 Pull Requests integrated just in the Pharo repository. We have closed 972 issues and received contributions from more than 70 different contributors. We have also a lot of work in the separate projects that are included in each Pharo release: > > http://github.com/pharo-spec/NewTools <https://github.com/pharo-spec/NewTools> > http://github.com/pharo-spec/NewTools-DocumentBrowser <https://github.com/pharo-spec/NewTools-DocumentBrowser> > http://github.com/pharo-spec/Spec <https://github.com/pharo-spec/Spec> > http://github.com/pharo-vcs/Iceberg <https://github.com/pharo-vcs/Iceberg> > http://github.com/ObjectProfile/Roassal3 <https://github.com/ObjectProfile/Roassal3> > http://github.com/pillar-markup/Microdown <https://github.com/pillar-markup/Microdown> > http://github.com/pillar-markup/BeautifulComments <https://github.com/pillar-markup/BeautifulComments> > http://github.com/pharo-project/pharo-vm <https://github.com/pharo-project/pharo-vm> > Contributors > > We always say Pharo is yours. It is yours because we made it for you, but most importantly because it is made by the invaluable contributions of our great community (yourself). A large community of people from all around the world contributed to Pharo 11.0 by making pull requests, reporting bugs, participating in discussion threads, providing feedback, and a lot of helpful tasks in all our community channels. Thank you all for your contributions. > > The Pharo Team > > Discover Pharo: https://pharo.org/features <https://pharo.org/features> > Try Pharo: http://pharo.org/download <http://pharo.org/download> > Learn Pharo: http://pharo.org/documentation <http://pharo.org/documentation>

May 12, 2023

Re: [ANN] Pharo 11 Released !

by Gabriel Cotelli

Congratulations on the new release. Now it's time to adapt the libraries and check that continue working with this version :P I think you need to update also https://github.com/pharo-project/pharo/releases to tag the commit used to produce the released image. Regards, Gabriel On Thu, May 11, 2023 at 8:39â¯AM Esteban Lorenzano <estebanlm(a)netc.eu> wrote: > Dear Pharo users and dynamic language lovers: > > We have released Pharo <https://pharo.org/> version 11! > What is Pharo? > Pharo is a pure object-oriented programming language and a powerful > environment focused on simplicity and immediate feedback. > > > > - Simple & powerful language: No constructors, no types declaration, > no interfaces, no primitive types. Yet a powerful and elegant language with > a full syntax fitting in one postcard! Pharo is objects and messages all > the way down. > - Live, immersive environment: Immediate feedback at any moment of > your development: Developing, testing, debugging. Even in production > environments, you will never be stuck in compiling and deploying steps > again! > - Amazing debugging experience: Pharo environment includes a debugger > unlike anything you've seen before. It allows you to step through code, > restart the execution of methods, create methods on the fly, and much more! > - Pharo is yours: Pharo is made by an incredible community, with more > than 100 contributors for the last revision of the platform and hundreds of > people constantly contributing with frameworks and libraries. > - Fully open-source: Pharo full stack is released under MIT > <https://opensource.org/licenses/MIT> License and available on GitHub > <https://github.com/pharo-project/pharo> > > ... more on the Pharo Features page <http://www.pharo.org/features>. > > In this iteration of Pharo, we continue working on our objectives of > improvement, clean-up and modularization. Also, we included a number of > usability and speed improvements. A complete list of changes and > improvements is available in our Changelog > <https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo110Chang…> > > Some highlights of this amazing version: > Highlights > Tools > > - Iceberg (the git client/VCS control tool) has received a lot of > tweaks and fixes to work better with GitHub and other Git services. > - Our debugger now incorporates lots of tweaks and notably the > capability of adding bindings in the context interaction model. > - The is a new implementation of rewrite tools and improved > refactoring support. > - There is a new tool: The Document Browser, which presents Microdown > (markdown compatible) documents placed on the web or locally. > - New Tools presented in Calypso (the System Browser) and additional > extended Inspectors. > - All versions of NewTools, Spec, Roassal and Microdown have been > updated with their respective bug fixes and improvements. > > System > > - Extended Full Blocks and Constant Clock closures support. > - Additional Inlining and optimizations > - Bug Fixes and Clean up. > - Ephemeron Finalization support. > > Virtual machine > > - Ephemerons Production Ready. > - Initial support for Single-Instruction Multiple-Data (SIMD). > - Third-Party Dependency Update (Newer versions, Graphic Libraries > using Hardware Acceleration). > - Clean Ups: Remove lots of old code, notably old experiments, and > dead code. > > Development Effort > This new version is the result of 1412 Pull Requests integrated just in > the Pharo repository. We have closed 972 issues and received contributions > from more than 70 different contributors. We have also a lot of work in the > separate projects that are included in each Pharo release: > > > - http://github.com/pharo-spec/NewTools > <https://github.com/pharo-spec/NewTools> > - http://github.com/pharo-spec/NewTools-DocumentBrowser > <https://github.com/pharo-spec/NewTools-DocumentBrowser> > - http://github.com/pharo-spec/Spec > <https://github.com/pharo-spec/Spec> > - http://github.com/pharo-vcs/Iceberg > <https://github.com/pharo-vcs/Iceberg> > - http://github.com/ObjectProfile/Roassal3 > <https://github.com/ObjectProfile/Roassal3> > - http://github.com/pillar-markup/Microdown > <https://github.com/pillar-markup/Microdown> > - http://github.com/pillar-markup/BeautifulComments > <https://github.com/pillar-markup/BeautifulComments> > - http://github.com/pharo-project/pharo-vm > <https://github.com/pharo-project/pharo-vm> > > Contributors > We always say Pharo is yours. It is yours because we made it for you, but > most importantly because it is made by the invaluable contributions of our > great community (yourself). A large community of people from all around the > world contributed to Pharo 11.0 by making pull requests, reporting bugs, > participating in discussion threads, providing feedback, and a lot of > helpful tasks in all our community channels. Thank you all for your > contributions. > > The Pharo Team > > Discover Pharo: https://pharo.org/features > Try Pharo: http://pharo.org/download > Learn Pharo: http://pharo.org/documentation >

May 11, 2023

Re: [ANN] Pharo 11 Released !

by Santiago Bragagnolo

Partyyy! Thanks to all who made this new release possible! [image: image.png] El jue, 11 may 2023 a las 13:39, Esteban Lorenzano (<estebanlm(a)netc.eu>) escribiÃ³: > Dear Pharo users and dynamic language lovers: > > We have released Pharo <https://pharo.org/> version 11! > What is Pharo? > Pharo is a pure object-oriented programming language and a powerful > environment focused on simplicity and immediate feedback. > > > > - Simple & powerful language: No constructors, no types declaration, > no interfaces, no primitive types. Yet a powerful and elegant language with > a full syntax fitting in one postcard! Pharo is objects and messages all > the way down. > - Live, immersive environment: Immediate feedback at any moment of > your development: Developing, testing, debugging. Even in production > environments, you will never be stuck in compiling and deploying steps > again! > - Amazing debugging experience: Pharo environment includes a debugger > unlike anything you've seen before. It allows you to step through code, > restart the execution of methods, create methods on the fly, and much more! > - Pharo is yours: Pharo is made by an incredible community, with more > than 100 contributors for the last revision of the platform and hundreds of > people constantly contributing with frameworks and libraries. > - Fully open-source: Pharo full stack is released under MIT > <https://opensource.org/licenses/MIT> License and available on GitHub > <https://github.com/pharo-project/pharo> > > ... more on the Pharo Features page <http://www.pharo.org/features>. > > In this iteration of Pharo, we continue working on our objectives of > improvement, clean-up and modularization. Also, we included a number of > usability and speed improvements. A complete list of changes and > improvements is available in our Changelog > <https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo110Chang…> > > Some highlights of this amazing version: > Highlights > Tools > > - Iceberg (the git client/VCS control tool) has received a lot of > tweaks and fixes to work better with GitHub and other Git services. > - Our debugger now incorporates lots of tweaks and notably the > capability of adding bindings in the context interaction model. > - The is a new implementation of rewrite tools and improved > refactoring support. > - There is a new tool: The Document Browser, which presents Microdown > (markdown compatible) documents placed on the web or locally. > - New Tools presented in Calypso (the System Browser) and additional > extended Inspectors. > - All versions of NewTools, Spec, Roassal and Microdown have been > updated with their respective bug fixes and improvements. > > System > > - Extended Full Blocks and Constant Clock closures support. > - Additional Inlining and optimizations > - Bug Fixes and Clean up. > - Ephemeron Finalization support. > > Virtual machine > > - Ephemerons Production Ready. > - Initial support for Single-Instruction Multiple-Data (SIMD). > - Third-Party Dependency Update (Newer versions, Graphic Libraries > using Hardware Acceleration). > - Clean Ups: Remove lots of old code, notably old experiments, and > dead code. > > Development Effort > This new version is the result of 1412 Pull Requests integrated just in > the Pharo repository. We have closed 972 issues and received contributions > from more than 70 different contributors. We have also a lot of work in the > separate projects that are included in each Pharo release: > > > - http://github.com/pharo-spec/NewTools > <https://github.com/pharo-spec/NewTools> > - http://github.com/pharo-spec/NewTools-DocumentBrowser > <https://github.com/pharo-spec/NewTools-DocumentBrowser> > - http://github.com/pharo-spec/Spec > <https://github.com/pharo-spec/Spec> > - http://github.com/pharo-vcs/Iceberg > <https://github.com/pharo-vcs/Iceberg> > - http://github.com/ObjectProfile/Roassal3 > <https://github.com/ObjectProfile/Roassal3> > - http://github.com/pillar-markup/Microdown > <https://github.com/pillar-markup/Microdown> > - http://github.com/pillar-markup/BeautifulComments > <https://github.com/pillar-markup/BeautifulComments> > - http://github.com/pharo-project/pharo-vm > <https://github.com/pharo-project/pharo-vm> > > Contributors > We always say Pharo is yours. It is yours because we made it for you, but > most importantly because it is made by the invaluable contributions of our > great community (yourself). A large community of people from all around the > world contributed to Pharo 11.0 by making pull requests, reporting bugs, > participating in discussion threads, providing feedback, and a lot of > helpful tasks in all our community channels. Thank you all for your > contributions. > > The Pharo Team > > Discover Pharo: https://pharo.org/features > Try Pharo: http://pharo.org/download > Learn Pharo: http://pharo.org/documentation >

May 11, 2023