January 2020 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Little challenge

by Alexandre Bergel

You are very right. Unfortunately, there are many situation like this. Consider: Point allInstances size "101283" Point allInstances asSet size "11381" 'String' class allInstances size "111492" 'String' class allInstances asSet size â57874" A lot of duplication aroundâ¦ Cheers, Alexandre > On 08-01-2020, at 21:42, ducasse <stepharo(a)netcourrier.com> wrote: > > > Hi > > I would like know how many instances of Color are instantiated by a theme. > I would like to know how many times the same color is created. > > Iâm creating a theme using a dictionary instead of stupidly returning color. > May be like that I can use an LRUCache to see the number of hits. > > I will see if I can instrument Color new. > > We really need tools that help us measuring things. > > Any other ideas? > > S. > >

Jan. 8, 2020

Re: [Pharo-dev] Little challenge

by ducasse

luckily not :) > On 8 Jan 2020, at 22:07, Esteban Maringolo <emaringolo(a)gmail.com> wrote: > > I'll make the first guess: 10^6 calls. > > Esteban A. Maringolo > > On Wed, Jan 8, 2020 at 6:03 PM ducasse <stepharo(a)netcourrier.com> wrote: >> >> So now I know how many instance of colors are created when we switch theme and it looks like a real plague. >> I will let you guess the number but this is not a small one :( >> >> I will check on my lovely theme if using a dictionary can manage it. >> >>> On 8 Jan 2020, at 21:51, ducasse <stepharo(a)netcourrier.com> wrote: >>> >>> Color >> basicNew >>> Transcript show: '.'; cr. >>> ^ super basicNew >>> >>> >>> This is scary. >>> I will save in a file because we are creating so many spurious colors that it is nearly not possible to see the amount. >>> >>> >> >> >> >

Jan. 8, 2020

Re: [Pharo-dev] Little challenge

by Esteban Maringolo

I'll make the first guess: 10^6 calls. Esteban A. Maringolo On Wed, Jan 8, 2020 at 6:03 PM ducasse <stepharo(a)netcourrier.com> wrote: > > So now I know how many instance of colors are created when we switch theme and it looks like a real plague. > I will let you guess the number but this is not a small one :( > > I will check on my lovely theme if using a dictionary can manage it. > > > On 8 Jan 2020, at 21:51, ducasse <stepharo(a)netcourrier.com> wrote: > > > > Color >> basicNew > > Transcript show: '.'; cr. > > ^ super basicNew > > > > > > This is scary. > > I will save in a file because we are creating so many spurious colors that it is nearly not possible to see the amount. > > > > > > >

Jan. 8, 2020

Re: [Pharo-dev] Little challenge

by ducasse

So now I know how many instance of colors are created when we switch theme and it looks like a real plague. I will let you guess the number but this is not a small one :( I will check on my lovely theme if using a dictionary can manage it. > On 8 Jan 2020, at 21:51, ducasse <stepharo(a)netcourrier.com> wrote: > > Color >> basicNew > Transcript show: '.'; cr. > ^ super basicNew > > > This is scary. > I will save in a file because we are creating so many spurious colors that it is nearly not possible to see the amount. > >

Jan. 8, 2020

Re: [Pharo-dev] Little challenge

by ducasse

Color >> basicNew Transcript show: '.'; cr. ^ super basicNew This is scary. I will save in a file because we are creating so many spurious colors that it is nearly not possible to see the amount.

Jan. 8, 2020

Little challenge

by ducasse

Hi I would like know how many instances of Color are instantiated by a theme. I would like to know how many times the same color is created. Iâm creating a theme using a dictionary instead of stupidly returning color. May be like that I can use an LRUCache to see the number of hits. I will see if I can instrument Color new. We really need tools that help us measuring things. Any other ideas? S.

Jan. 8, 2020

Smalltalk job offers at Barcelona

by ducasse

Hello Pharoers Please distribute aroundâ¦. Lifeware is looking for smart people and Smalltalkers for positions at Barcelona. If you are interested please contact Massimo Arnoldi <massimo.arnoldi(a)lifeware.ch> S.

Jan. 8, 2020

Re: [Pharo-dev] [Mm10s] 2020-01-06

by Denis Kudriashov

Ð²Ñ, 7 ÑÐ½Ð². 2020 Ð³. Ð² 20:34, ducasse <stepharo(a)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(a)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(a)gmail.com >> > >> >> >> >> >

Jan. 8, 2020

Re: [Pharo-dev] [Mm10s] 2020-01-06

by Denis Kudriashov

Hi Sven. It was an example of definition format which new parser targets. Ð²Ñ, 7 ÑÐ½Ð². 2020 Ð³. Ð² 22:20, Sven Van Caekenberghe <sven(a)stfx.eu>: > It sounds wrong to call this a parser, it is a builder, no ? > > It is plain Pharo syntax that builds a representation, IIUC. > > > On 7 Jan 2020, at 21:32, ducasse <stepharo(a)netcourrier.com> wrote: > > > > 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 > > > > 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(a)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(a)gmail.com > >> > > >> > >> > >> > > > > >

Jan. 8, 2020

Re: [Pharo-dev] [Mm10s] 2020-01-06

by Sven Van Caekenberghe

It sounds wrong to call this a parser, it is a builder, no ? It is plain Pharo syntax that builds a representation, IIUC. > On 7 Jan 2020, at 21:32, ducasse <stepharo(a)netcourrier.com> wrote: > > 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 > > 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(a)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(a)gmail.com >> > >> >> >> >

Jan. 7, 2020