August 2022 - Pharo-dev - lists.pharo.org

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

by Marcus Denker

We merged 13 PRs this week: Features ======== - SIMD bytecode support https://github.com/pharo-project/pharo/pull/11516 Fixes ===== - Fix senders/implementors of class variables and shared pools https://github.com/pharo-project/pharo/pull/11490 - Clean version of PR 11498: DrTests: Rerunning test https://github.com/pharo-project/pharo/pull/11510 - 11533-Ring-RGMethodDefinitionisDoIt-missing https://github.com/pharo-project/pharo/pull/11535 - Fix #11540: Selecting a string and pressing Implementors breaks in Calypso New Class pane https://github.com/pharo-project/pharo/pull/11542 - Fix isScripting for block contexts from DoIts https://github.com/pharo-spec/Spec/pull/1297 https://github.com/pharo-spec/NewTools/pull/401 - remove-broken-Fuel-inspector https://github.com/pharo-spec/NewTools/pull/397 - fix closing Spotter by Esc https://github.com/pharo-spec/NewTools/pull/410 Cleanup ======= - Delete .bintray.json https://github.com/pharo-project/pharo/pull/11522 - Fixes: #11514 Removing Refactoring Help package https://github.com/pharo-project/pharo/pull/11521 - Fix spurious creation of stream https://github.com/pharo-project/pharo/pull/11531 Pharo10 ======= - Backport visitWindowExposeEvent to redraw when windows are re-exposed https://github.com/pharo-project/pharo/pull/11484

Aug. 19, 2022

Weeks (30/31/32 ) on the Pharo Issue Tracker

by Marcus Denker

Holiday period, but we merged 15 PRs the last three weeks. Fixes ===== - fix the top and bottom of the rectangle of text input region so that â¦ #11474 https://github.com/pharo-project/pharo/pull/11474 - Fixes: #11342 added some tests to cover to methods that were not called. #11349 https://github.com/pharo-project/pharo/pull/11349 - 10774-FTP-clientgetDataInto-lost-returned-information #11466 https://github.com/pharo-project/pharo/pull/11466 - Improve protocol suggestions when creating method from debugger #11486 https://github.com/pharo-project/pharo/pull/11486 - Fix DoIt highlighting and debugIt in ProcessBrowser #11473 https://github.com/pharo-project/pharo/pull/11473 Test Runner =========== - Fix issue #11496: Executable comments checker of DrTests https://github.com/pharo-project/pharo/pull/11497 - Fixing issue #9545: DrTests should show 'expected failures' and 'passed unexpectedly' #11495 https://github.com/pharo-project/pharo/pull/11495 - NewTestRunner, NewCommandLineRunner #11469 https://github.com/pharo-project/pharo/pull/11469 - CoverageRunner deleted #11504 https://github.com/pharo-project/pharo/pull/11504 Features ======== - CloseAllWindows #11408 https://github.com/pharo-project/pharo/pull/11408 Cleanup ======= - [cleanup] naming consistency of bytecodeS #11488 https://github.com/pharo-project/pharo/pull/11488 - [improvement] add deprecation + transform to bytecode -> bytecodes #11502 https://github.com/pharo-project/pharo/pull/11502 - [cleanup] remove empty test classes #11508 https://github.com/pharo-project/pharo/pull/11508 - Adding comments to SUnit classes #11478 https://github.com/pharo-project/pharo/pull/11478

Aug. 17, 2022

Re: Inovation Technology Award Submission: Polyphemus

by Noury Bouraqadi

Thank you Pierre for the submission :-) Noury On Aug 16 2022, at 10:36 am, pmissech <pierre.misse-chanabier(a)inria.fr> wrote: > Hello, > > Although i will not be able to attend ESUG'22, a friend agreed to > present one of our projects to the innovation award. > **Polyphemus** is a VM related, but public aims at any kind of developers. > Particularly, the video submission talks about how to look at an image > and how to **recover** dead images. > Feel free to contact me if you have any questions ! > Enjoy (and vote for Polyphemus!). > > 5 minutes video, Innovation Technology Award submission: > https://youtu.be/zf3cCtNW830 > Repository: github.com/hogoww/Polyphemus/ > Additionnal information on image recovery: > https://github.com/hogoww/Polyphemus/blob/main/Documentation/ResurrectingDe… > > Cheers !

Aug. 16, 2022

Re: Pharo's syntax highlighter

by Marcus Denker

> On 6 Aug 2022, at 07:26, Pierre Misse Chanabier <pierre.misse-chanabier(a)inria.fr> wrote: > > I do not know the syntax highlighter, but I know the AST fairly well. > The first two points are fairly easy: > > Color method temp variables and block parameter variables differently. Currently they are identified too generally as just #variables. They are therefore always the same color. Can someone point me to the parser classes that extract these features? > > Color differently Classes and other globals? I'm trying to find this distinction as well in the parser classes. If someone familiar with the parsing and related GUI classes can give me some pointers, I'll do the work. > > Let the user assign colors to the first 7 levels of parentheses and first 7 levels of brackets. > > > 1) There is no differences in the AST about temporary / arguments declaration. > They are both at the level of the sequence node of the method/block (the body). > Thankfully we can ask for the parent and have a case for each. > You'd have to modify visitTemporaryDeclarationNode:. > > 2) There is no difference in the AST between classes / Globals. > Because Classes are in fact Globals. > You'd have to ask for the (self class environment classAt: aGlobal name) ifNotNil: [ class behavior ] ifNil: [ global behavior ]. > This is true, but kid of not: the AST does not distinguish kind of variables, as this is not Grammar but âSemanticsâ. That is, every variables use (definition, read, write) just gets one (new) instance of RBVariableNode. But: we do name analysis for the AST. This means that the AST that you have in hand is always annotated with semantic information. For Variables this means that every RBVariableNode instance has a âsemantic variableâ attached to it that models the Variable. (See Hierarchy of the class âVariableâ). Here now we get what we expect: for e.g. a temp there is *one* instance or a temp variable, and all the instances of RBVariableNode that are about that variable reference the one instance. With this, we can actually distinguish all the kinds of variables. (we pushed this so far that actually the compiler just asks the variable to generate bytecode, for example). For ease of use, we have added test methods to RBVariableNode lile isTempVariable, isClassVariable, isInstanceVariable and so on. > A quick look seem that the behavior of the syntax highlighter is in the IconStyler class. > (again, don't know it, just checking this out quickly). The main part of the syntax highlighter is class SHRBTextStyler. This is âjustâ a visitor on the AST (by including the trait TRBProgramNodeVisitor). For example, the method called via the #visitVariableNode: method is this: resolveStyleFor: aVariableNode aVariableNode binding ifNil: [^#default]. aVariableNode isArgumentVariable ifTrue: [ ^#methodArg]. aVariableNode isTempVariable ifTrue: [ ^#tempVar]. aVariableNode isGlobalVariable ifTrue: [ ^#globalVar]. "here we should add support for #classVar" aVariableNode isClassVariable ifTrue: [ ^#globalVar]. aVariableNode isInstanceVariable ifTrue: [ ^#instVar]. "for now we use temp variable here, we could now color them with their own color" aVariableNode isWorkspaceVariable ifTrue: [ ^#tempVar]. (self class formatIncompleteIdentifiers and: [ aVariableNode hasIncompleteIdentifier ]) ifTrue:[ ^#incompleteIdentifier] . "Note: if formatIncompleteIdentifiers is true, a non-exisiting variable might be incomplete" aVariableNode isUndeclaredVariable ifTrue: [ ^#undefinedIdentifier ]. ^#invalid. This shows that we, right now, do not distinguish globals from class variables, but all that would be very easy to add, as the annotated AST has all that information. (I always wanted to rewrite that method to just delegate to the aVariableNode and from there delatete to the Variable subclass and add a #styleSymbol method there, would make all that even simpler). Marcus

Aug. 16, 2022

Re: about object serialization and deserialization

by Sven Van Caekenberghe

Hi Stef, > On 15 Aug 2022, at 20:25, stephane ducasse <stephane.ducasse(a)inria.fr> wrote: > > Hi guys > > It is interesting to think about the design and use of object deserializers. > > https://www.slideshare.net/frohoff1/deserialize-my-shorts-or-how-i-learned-… > > <2204.09388.pdf> Interesting, and indeed, a big problem (especially denial of service attacks). Step one is to be conscious of the problem (which exists across all language/formats). Step two could be to add some sanity checks (limits) to parsers. Would be a nice subject for a (student) project. Sven

Aug. 16, 2022

Inovation Technology Award Submission: Polyphemus

by pmissech

Hello, Although i will not be able to attend ESUG'22, a friend agreed to present one of our projects to the innovation award. **Polyphemus** is aÂ VM related, but public aims at any kind of developers. Particularly, the video submission talks about how to look at an image and how to **recover** dead images. Feel free to contact me if you have any questions ! Enjoy (and vote for Polyphemus!). 5 minutes video, Innovation Technology Award submission: https://youtu.be/zf3cCtNW830 Repository: github.com/hogoww/Polyphemus/ Additionnal information on image recovery: https://github.com/hogoww/Polyphemus/blob/main/Documentation/ResurrectingDe… Cheers !

Aug. 16, 2022

MPLR 2022 -- Call for Participation

by Guillermo Polito

======================================================================== Call for Participation MPLR 2022 - 19th International Conference on Managed Programming Languages & Runtimes September 14-15, 2022 in Brussels, Belgium https://soft.vub.ac.be/mplr22/ Follow us @MPLR_Conf ======================================================================== The 19th International Conference on Managed Programming Languages & Runtimes (MPLR, formerly ManLang) is a premier forum for presenting and discussing novel results in all aspects of managed programming languages and runtime systems, which serve as building blocks for some of the most important computing systems in use, ranging from small-scale (embedded and real-time systems) to large-scale (cloud-computing and big-data platforms) and anything in between (desktop, mobile, IoT, and wearable applications). This year, MPLR will be held at the campus of the Vrije Universiteit Brussel(VUB) in Brussels, Belgium. Keynotes -------- Performance Optimizations in the .NET GC Dr. Maoni Stephens, Microsoft, USA Static Compilation of JavaScript Dr. Manuel Serrano, Inria Sophia-Antipolis, France Accepted Papers --------------- Automatic Array Transformation to Columnar Storage at Run Time Lukas Makor et al. Compressed Forwarding Tables Reconsidered Jonas Norlinder et al. Event-Based Out-of-place Debugging Tom Lauwaerts et al. Machine-Learning-Based Self-Optimizing Compiler Heuristics Raphael Mosaner et al. SecSharp: Towards Efficient Trusted Execution in Managed Languages Gilang Mentari Hamidy et al. A Model Checking Framework for a New Collector Framework Bochen Xu et al. Porting a JIT compiler to RISC-V: Challenges and Opportunities Quentin Ducasse et al. Analyzing and Predicting Energy Consumption of Garbage Collectors in OpenJDK Marina Shimchenko et al. Better Understanding the Costs and Benefits of Automatic Memory Management Kunal Sareen et al. Dynamic Taint Analysis with Label-Defined Semantics Jacob Kreindl et al. Attendance ---------- Thanks to our generous sponsors, we were able to significantly reduce this yearâs registration fees. Early Registration Fees: Students: 175 Euro Regular: 250 Euro In addition to the conference participation, the registration includes: - 2-day transportation ticket in the Brussels area - welcome reception on Wednesday, September 14 - guided tour to the city hall and conference banquet on Thursday, September 15 More details, and link to registration system: https://soft.vub.ac.be/mplr22/registration/ Important Dates --------------- Early Registration: 23 August 2022 Conference Dates: 14-15 September 2022

Aug. 16, 2022

about object serialization and deserialization

by stephane ducasse

Hi guys It is interesting to think about the design and use of object deserializers. https://www.slideshare.net/frohoff1/deserialize-my-shorts-or-how-i-learned-…

Aug. 15, 2022

Re: [Pharo-users] Omnibase/Monibase repository removal

by stephane ducasse

> On 12 Aug 2022, at 07:25, Yanni Chiu <yannix7db(a)gmail.com <mailto:yannix7db@gmail.com>> wrote: > > Sounds good. Using Fuel to serialize/deserialize should be fine, but I had unhappy experience with early versions where a newer Fuel version could not read content written by earlier Fuel versions. I agree with you. It ws an important requirements that got dropped. And then after we never got to time to revisit it and I always felt ashamed because migrating data is super important to me.

Aug. 12, 2022

Re: [Pharo-users] Omnibase/Monibase repository removal

by Norbert Hartl

hi Yanni, > Am 12.08.2022 um 07:25 schrieb Yanni Chiu <yannix7db(a)gmail.com>: > > Sounds good. Using Fuel to serialize/deserialize should be fine, but I had unhappy experience with early versions where a newer Fuel version could not read content written by earlier Fuel versions. That is indeed the weakest part of Fuel I know and something I need to take care off. I will use Fuel without that part of the header that barks on versions. What needs to be done is to see what changed between versions and make a way to migrate. For this the database files will most likely have a version that is dedicated to the Fuel version being used. > > In my mind, a disk-based B-tree is the fundamental data structure for any database (e.g. GemStone, Omnibase, Relational DBs all have it), but I donât see it mentioned so far. Everything else about a "database" is optional, IMHO. > Ah, right, I didn't write about it but it is essential. My plan would be to also have a disk based b-tree dictionary that can keep parts like the keys (maybe even incrementally) in memory. But I'm not an expert in b-trees so I need to figure out what is the gap between the requirements of a b-tree and my plans ;) Also b-tree will come later after you are able to write/read something reliable. > For example, a query language is not needed at all, if the data items are equivalent to objects running in a Smalltalk VM - the query language is Smalltalk itself. It âjustâ has to mesh well with the indexing. > I think it needs a query DSL. Using blocks has serious limitations doing a proper query. The usage of instVars needs to be well known in order to analyze a query for index usage. Furthermore is the problem like #collect:thenSelect: even more severe in a database. So for indexes and query optimizations it should be a query DSL that is more like aCollection select firstName = 'Norbert' I will experiment a bit. The combination of multiple queries in smalltalk and using binary messages is a problem of its own. > Another feature is MVCC. How much concurrency is needed, and how it is implemented, is an implementation choice. Iâd mentioned LMDB on Discord. It has single writer, many readers. Choosing to have multiple simultaneous writers has a cost. When there is one or more big machines, it seems sensible have the big machines use multiple writers. But when these databases scale up, the database ends up sharded, with parts of the data spread over multiple machines. Why not just start there, with many small machines owning a small part of the database, and use just a single writer process. The application can then deal with concurrency, conflicts and assembling results, in whatever manner best suits. > Almost all databases have only a single writer for one set of data. Sharding is a way to have virtual partitions of your data where you can have a writer per virtual partition removing the conflit potential. MVCC is not about having multiple writers as it is hardly possible. The benefits of MVCC are that data in a transaction is fully isolated and writers do not block readers. I personally like that a MVCC database is an append-only store for object data. You have to have one concurrency approach and MVCC is not really hard to implement. In ApptiveGrid we have a fully partioned model per user where inter-user-references use URNs as content address notation. This way we have hundreds of databases where each has a single writer. This is my main focus but I think we are on the same page regarding that. If nothing changes my talk at ESUG will talk about this. > So I see the end goal to be a set of frameworks, and some ârecipesâ for putting the frameworks together, to solve the âpersistenceâ problem. These are just half-baked ideas of course. Iâll follow the project, and hope to contribute. Thanks. I don't how far this project will get. But I have a need and ideas. Just need time :) Let's see where the journey gets. Norbert > > Yanni > > On Wed, Aug 10, 2022 at 7:08 AM Norbert Hartl <norbert(a)hartl.name <mailto:norbert@hartl.name>> wrote: > FYI > > As the license situation around Omnibase is unlikely to change and such a license is not an enabler for collaboration I came to the conclusion that there is no other way than to start a new OO database (what a surprise! :) ) > > If you are interested or want to see what will happen in the next months you can have a look at > > https://github.com/ApptiveGrid/Soil <https://github.com/ApptiveGrid/Soil> > > After half a day of work it can already serialize and partition a simple graph and store it to disk in a way it can be read back even when partitioned. Thanks to having Fuel we do not need to reinvent the wheel and have serialization/materialization done. > Of course this is super simple and does not comes close to anything usable but a good start. I've also added a documentation in the github repo to describe the most important parts for me that I will target. > > Questions, critiques and laughs are appreciated, > > Norbert > >> Am 08.08.2022 um 15:18 schrieb Norbert Hartl <norbert(a)hartl.name <mailto:norbert@hartl.name>>: >> >> To all Omnibase and Monibase users. >> >> It turned out that neither of those are open source. The author of the database contacted me clarifying the situation that he has the copyright and never released something open source. This means that I will remove the Omnibase repositories in few weeks from >> >> https://github.com/ApptiveGrid/MoniBase <https://github.com/ApptiveGrid/MoniBase> >> >> and >> >> https://github.com/pharo-nosql/OmniBase <https://github.com/pharo-nosql/OmniBase> >> >> I'm very sorry about that but someone just took the code 9 years before, copied it on github and put illegally an MIT license to the repository. We only want free software in our repositories and hence the above will go away. >> >> As we see it essential to have a good OO database in pharo we will see how much effort it will be build a small and simple OO database that can replace Omnibase. >> >> regards, >> >> Norbert >

Aug. 12, 2022