вÑ, 7 Ñнв. 2020 г. в 20:34, ducasse <stepharo@netcourrier.com>:
Hello Denis
What is Fluid class parser?
This is the name of the class definition we sketched and presented at Maribor. The idea is how to fight the combinatory explosion of parameters (tags, ephemerons, traits, slots, â¦.) For now Iâm putting in place the structure to be able to create a tree of definition nodes for a class definition
Superclass < #MyObject uses: #MyTrait; slots: { #a. #b }; classVariables: { #A. #B }; tags: #(Core) ; package: #MyPackage
The minimal class definition is the following one:
Superclass < #MyObject package: #MyPackage
or Superclass < #MyObject
Interesting to know why superclass is chose for the receiver in new class definition. It does not cover the proxy classes with nil superclass.
Like that we get closer to ruby and other language that have a compact class definition. One of the key constraints is that we do not want to break the syntax. So everything is message based and consistent with the syntax and our motto.
But we will see. I prefer talking with something running. When I worked on the package I rewrote everything three times.
The idea is that this class definition parser should replace the ClassDefinitionParser (which we will keep for the traditional class definition but that in a couple of years from now should vanish).
S.
Is it the name of currently integrated parser?
вÑ, 7 Ñнв. 2020 г. в 19:48, ducasse <stepharo@netcourrier.com>:
Thanks Pablo
Last Week - Working on concurrent programming booklet - Enlumineur - Better iceberg explanation with Pablo - Fluid class parser
This week - Fluid class parser - Enlumineur - Consortium meeting - PBE80 - Working on concurrent programming booklet
Hello, last week was a short one but some things have been done:
- [VM] Porting the GC fix to Pharo 7 / 8 VM - [VM] Building for the different Platforms - [VM] Signing for OSX - [VM] The versions will be available today to start testing it before promoting them to stable. - [Pharo8] Fixing Issues before the release - [VM Dev] Starting to work in improving tests in JIT and GC.
-- Pablo Tesone. tesonep@gmail.com