October 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] , for vector creation

by Tudor Girba

Hi, > On Oct 25, 2017, at 10:53 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > In Polymath I guess that the vectors are longer. Vectors can be longer. We just use 2D and 3D in Bloc. > But if I'm correct it > is #( 12 23) asVector. I like this one. Weâll definitely take a look. > Doru did you look at Jun because Jun introduced 3DPoint and I wonder > if they did not introduce Vector? I did not look at that. > What would be the alternatives for vector? > Any idea how this is done in other languages > > 1~>2 > 1!2 > 1-}2 Nope. Doru > Stef > > > On Wed, Oct 25, 2017 at 8:56 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> Hi, >> >> Vector is not Bloc-sepcific. We just need it in Bloc and because there wasnât any, we now have one in Bloc. But, it can be pulled out without any issues. >> >> Cheers, >> Doru >> >> >>> On Oct 25, 2017, at 8:21 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >>> >>> For example, in FileReference is adds a file extension. PetitParser uses it as a sequence operator. >>> >>> But in both cases #, is sent to FileReference/Petit parser instance, so it is contained. >>> You would use it on a (generic) Number and tie it to specific Bloc meaning. Maybe have a polymorphic Vector in regular Pharo (I would imagine that PolyMath could also make use of that)? >>> >>> Peter >> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "Obvious things are difficult to teach." >> >> >> >> >> > -- www.tudorgirba.com www.feenk.com "One cannot do more than one can do."

Oct. 26, 2017

Re: [Pharo-dev] Why 2017 sizeInMemory = 0?

by tesonep＠gmail.com

Because it is an immediate value. On 26 Oct 2017 10:06, "Denis Kudriashov" <dionisiydk(a)gmail.com> wrote: Hi. Question from discord, why: 2017 sizeInMemory = 0 ? Looks like a bug, but maybe there is some reason for this.

Oct. 26, 2017

Re: [Pharo-dev] , for vector creation

by Denis Kudriashov

Another question. Will not these vectors deprecate Point in future ? Imaging that we will completely move to Bloc. And what about Rectangle? (Bloc implements own BlRectangle). 2017-10-26 9:26 GMT+02:00 phil(a)highoctane.be <phil(a)highoctane.be>: > #(1 3 4 5 7 -2) asVector > > Meh. > Ugly. > > { 1. 3. 4. a. b } asVector > > is the natural consequence. > > v := (1,3,4,5,7,-2) asVector > > keeps the parens. But why do I need to do that? > > Autoformatting messing with my parentheses is just a mistake. > I put them in, leave them where they are, 'kay? I do not need an editor > that rewrites what I tell it. AST power or not. > > And frankly, I like the "Feenk way of doing things" most of the time, so I > am willing to go that route. > > Phil > > > > On Thu, Oct 26, 2017 at 8:52 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > > > Automatic formatting will turn it into > > > > vector := 1,3,4,5,7,-2. > > > > Which is not as nice. > > > > And even though it looks ok for literal numbers (#(1 3 4 5 7 -2) > asVector would work too), this starts to look quite generic: > > > > vector := width, height, depth. > > > > > > Question: why not extend @ notation? > > > > x @ y @ z? > > > > Peter > > > > > > > > On Thu, Oct 26, 2017 at 8:22 AM, phil(a)highoctane.be <phil(a)highoctane.be> > wrote: > >> > >> I also like the , message for those vectors and the concatenation of > dimensions makes sense. > >> > >> vector := (1,3,4,5,7,-2). > >> > >> looks how it should be. > >> > >> Readable, easy to translate vector stuff from reference text. > >> > >> Phil > >> > >> > >> On Thu, Oct 26, 2017 at 7:00 AM, Nicolai Hess <nicolaihess(a)gmail.com> > wrote: > >>> > >>> > >>> > >>> Am 25.10.2017 10:50 PM schrieb "Torsten Bergmann" <astares(a)gmx.de>: > >>> > >>> Hi, > >>> > >>> there might be reasons for an own 2D vector class (instead of using > Point). > >>> But still I dislike the reimplementation of "," because for me so far > it > >>> has the meaning of "concatenating things". > >>> > >>> > >>> > >>> Like concatenating coordinates :-) > >>> > >>> > >>> > >>> Here you redefine it to create vector instances and it works only up > to three > >>> so far. Right? > >>> > >>> I understand that this gives some similarities with the math notation > (1,2) > >>> but I personally would prefer to use: > >>> > >>> 1@2 asVector > >>> > >>> or Vector2D x: 1 y: 2 > >>> > >>> Thx > >>> T. > >>> > >>> > >>> > >>> > Gesendet: Mittwoch, 25. Oktober 2017 um 20:06 Uhr > >>> > Von: "Tudor Girba" <tudor(a)tudorgirba.com> > >>> > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > >>> > Betreff: [Pharo-dev] , for vector creation > >>> > > >>> > Hi, > >>> > > >>> > As mentioned in the separate thread, we played with introducing the > extension: > >>> > > >>> > , aNumber > >>> > ^ BlVector2D x: self y: aNumber > >>> > > >>> > This means that (10,20) will return a 2D vector. > >>> > > >>> > We also have (10,20,30) which returns a 3D vector. > >>> > > >>> > , is used for different meanings already in the image beside the > collection concatenation. For example, in FileReference is adds a file > extension. And Exceptions create a collection. In other packages, > PetitParser uses it as a sequence operator. > >>> > > >>> > Please voice your concerns. > >>> > > >>> > Cheers, > >>> > Doru > >>> > > >>> > > >>> > -- > >>> > www.tudorgirba.com > >>> > www.feenk.com > >>> > > >>> > "Every thing should have the right to be different." > >>> > > >>> > > >>> > > >>> > > >>> > > >>> > > >>> > >>> > >> > > >

Oct. 26, 2017

Re: [Pharo-dev] Why 2017 sizeInMemory = 0?

by Marcus Denker

> On 26 Oct 2017, at 10:05, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > Hi. > > Question from discord, why: > > 2017 sizeInMemory = 0 > > ? > > Looks like a bug, but maybe there is some reason for this. #sizeInMemory only takes into account object header size and the size of the object itself. A small-integer is encoded in the pointer, so it has no size in itself, only the object pointing to it needs space for the pointer, just like for normal object. Marcus

Oct. 26, 2017

Why 2017 sizeInMemory = 0?

by Denis Kudriashov

Hi. Question from discord, why: 2017 sizeInMemory = 0 ? Looks like a bug, but maybe there is some reason for this.

Oct. 26, 2017

Re: [Pharo-dev] , for vector creation

by phil＠highoctane.be

#(1 3 4 5 7 -2) asVector Meh. Ugly. { 1. 3. 4. a. b } asVector is the natural consequence. v := (1,3,4,5,7,-2) asVector keeps the parens. But why do I need to do that? Autoformatting messing with my parentheses is just a mistake. I put them in, leave them where they are, 'kay? I do not need an editor that rewrites what I tell it. AST power or not. And frankly, I like the "Feenk way of doing things" most of the time, so I am willing to go that route. Phil On Thu, Oct 26, 2017 at 8:52 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > Automatic formatting will turn it into > > vector := 1,3,4,5,7,-2. > > Which is not as nice. > > And even though it looks ok for literal numbers (#(1 3 4 5 7 -2) asVector would work too), this starts to look quite generic: > > vector := width, height, depth. > > > Question: why not extend @ notation? > > x @ y @ z? > > Peter > > > > On Thu, Oct 26, 2017 at 8:22 AM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: >> >> I also like the , message for those vectors and the concatenation of dimensions makes sense. >> >> vector := (1,3,4,5,7,-2). >> >> looks how it should be. >> >> Readable, easy to translate vector stuff from reference text. >> >> Phil >> >> >> On Thu, Oct 26, 2017 at 7:00 AM, Nicolai Hess <nicolaihess(a)gmail.com> wrote: >>> >>> >>> >>> Am 25.10.2017 10:50 PM schrieb "Torsten Bergmann" <astares(a)gmx.de>: >>> >>> Hi, >>> >>> there might be reasons for an own 2D vector class (instead of using Point). >>> But still I dislike the reimplementation of "," because for me so far it >>> has the meaning of "concatenating things". >>> >>> >>> >>> Like concatenating coordinates :-) >>> >>> >>> >>> Here you redefine it to create vector instances and it works only up to three >>> so far. Right? >>> >>> I understand that this gives some similarities with the math notation (1,2) >>> but I personally would prefer to use: >>> >>> 1@2 asVector >>> >>> or Vector2D x: 1 y: 2 >>> >>> Thx >>> T. >>> >>> >>> >>> > Gesendet: Mittwoch, 25. Oktober 2017 um 20:06 Uhr >>> > Von: "Tudor Girba" <tudor(a)tudorgirba.com> >>> > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> >>> > Betreff: [Pharo-dev] , for vector creation >>> > >>> > Hi, >>> > >>> > As mentioned in the separate thread, we played with introducing the extension: >>> > >>> > , aNumber >>> > ^ BlVector2D x: self y: aNumber >>> > >>> > This means that (10,20) will return a 2D vector. >>> > >>> > We also have (10,20,30) which returns a 3D vector. >>> > >>> > , is used for different meanings already in the image beside the collection concatenation. For example, in FileReference is adds a file extension. And Exceptions create a collection. In other packages, PetitParser uses it as a sequence operator. >>> > >>> > Please voice your concerns. >>> > >>> > Cheers, >>> > Doru >>> > >>> > >>> > -- >>> > www.tudorgirba.com >>> > www.feenk.com >>> > >>> > "Every thing should have the right to be different." >>> > >>> > >>> > >>> > >>> > >>> > >>> >>> >> >

Oct. 26, 2017

Re: [Pharo-dev] , for vector creation

by Peter UhnÃ¡k

Automatic formatting will turn it into vector := 1,3,4,5,7,-2. Which is not as nice. And even though it looks ok for literal numbers (#(1 3 4 5 7 -2) asVector would work too), this starts to look quite generic: vector := width, height, depth. Question: why not extend @ notation? x @ y @ z? Peter On Thu, Oct 26, 2017 at 8:22 AM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > I also like the , message for those vectors and the concatenation of > dimensions makes sense. > > vector := (1,3,4,5,7,-2). > > looks how it should be. > > Readable, easy to translate vector stuff from reference text. > > Phil > > > On Thu, Oct 26, 2017 at 7:00 AM, Nicolai Hess <nicolaihess(a)gmail.com> > wrote: > >> >> >> Am 25.10.2017 10:50 PM schrieb "Torsten Bergmann" <astares(a)gmx.de>: >> >> Hi, >> >> there might be reasons for an own 2D vector class (instead of using >> Point). >> But still I dislike the reimplementation of "," because for me so far it >> has the meaning of "concatenating things". >> >> >> >> Like concatenating coordinates :-) >> >> >> >> Here you redefine it to create vector instances and it works only up to >> three >> so far. Right? >> >> I understand that this gives some similarities with the math notation >> (1,2) >> but I personally would prefer to use: >> >> 1@2 asVector >> >> or Vector2D x: 1 y: 2 >> >> Thx >> T. >> >> >> >> > Gesendet: Mittwoch, 25. Oktober 2017 um 20:06 Uhr >> > Von: "Tudor Girba" <tudor(a)tudorgirba.com> >> > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> >> > Betreff: [Pharo-dev] , for vector creation >> > >> > Hi, >> > >> > As mentioned in the separate thread, we played with introducing the >> extension: >> > >> > , aNumber >> > ^ BlVector2D x: self y: aNumber >> > >> > This means that (10,20) will return a 2D vector. >> > >> > We also have (10,20,30) which returns a 3D vector. >> > >> > , is used for different meanings already in the image beside the >> collection concatenation. For example, in FileReference is adds a file >> extension. And Exceptions create a collection. In other packages, >> PetitParser uses it as a sequence operator. >> > >> > Please voice your concerns. >> > >> > Cheers, >> > Doru >> > >> > >> > -- >> > www.tudorgirba.com >> > www.feenk.com >> > >> > "Every thing should have the right to be different." >> > >> > >> > >> > >> > >> > >> >> >> >

Oct. 26, 2017

[ANN] Pharo Consortium New Platinum Member: JPMorgan Chase

by Marcus Denker

The Pharo Consortium is very happy to announce that JPMorgan Chase has joined the Consortium as a Platinum Member. About - JPMorgan Chase: https://www.jpmorganchase.com - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium is to allow companies and institutions to support the ongoing development and future of Pharo. Individuals can support Pharo via the Pharo Association: - http://association.pharo.org

Oct. 26, 2017

Re: [Pharo-dev] , for vector creation

by phil＠highoctane.be

I also like the , message for those vectors and the concatenation of dimensions makes sense. vector := (1,3,4,5,7,-2). looks how it should be. Readable, easy to translate vector stuff from reference text. Phil On Thu, Oct 26, 2017 at 7:00 AM, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > Am 25.10.2017 10:50 PM schrieb "Torsten Bergmann" <astares(a)gmx.de>: > > Hi, > > there might be reasons for an own 2D vector class (instead of using Point). > But still I dislike the reimplementation of "," because for me so far it > has the meaning of "concatenating things". > > > > Like concatenating coordinates :-) > > > > Here you redefine it to create vector instances and it works only up to > three > so far. Right? > > I understand that this gives some similarities with the math notation (1,2) > but I personally would prefer to use: > > 1@2 asVector > > or Vector2D x: 1 y: 2 > > Thx > T. > > > > > Gesendet: Mittwoch, 25. Oktober 2017 um 20:06 Uhr > > Von: "Tudor Girba" <tudor(a)tudorgirba.com> > > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > > Betreff: [Pharo-dev] , for vector creation > > > > Hi, > > > > As mentioned in the separate thread, we played with introducing the > extension: > > > > , aNumber > > ^ BlVector2D x: self y: aNumber > > > > This means that (10,20) will return a 2D vector. > > > > We also have (10,20,30) which returns a 3D vector. > > > > , is used for different meanings already in the image beside the > collection concatenation. For example, in FileReference is adds a file > extension. And Exceptions create a collection. In other packages, > PetitParser uses it as a sequence operator. > > > > Please voice your concerns. > > > > Cheers, > > Doru > > > > > > -- > > www.tudorgirba.com > > www.feenk.com > > > > "Every thing should have the right to be different." > > > > > > > > > > > > > > >

Oct. 26, 2017

Re: [Pharo-dev] feenk log

by ClÃ©ment Bera

Hi, Good work, In PolyMaths/SciSmalltalk vectors and matrix are already implemented efficiently. I would recommend to share the same implementation. In the next few years, I think we will improve the performance of those vectors/matrix library using the processor vector instructions, and it would be nice if we have to improve one but not two libraries of vectors and matrix (This is the polie way of saying I am going to improve one library and the others will have to do it themselves). Regards, On Wed, Oct 25, 2017 at 5:53 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > Our team is working on a couple of projects that are relevant for the core > of Pharo, namely GT and Bloc/Brick. At ESUG we were asked by several > people, and Stef in particular, to make the progress on these projects more > transparent. To this end, we will start two streams of signals: > - fine grained info bits on out Twitter account (several times a week): > https://twitter.com/feenkcom > - a less often but regular (probably every 2 weeks) activity log message > sent to this mailing list > > Please let us know if you see an issue with this. > > In the meantime, letâs start. > > Bloc: > - Over the past couple of weeks Alex worked on transformations and > measurements in the core system. It turns out that there was room for quite > a number of performance optimizations and for making the system more > debuggable. > - At the low level, this involved adding matrix and vector support. > https://twitter.com/feenkcom/status/923123870537863168 > https://twitter.com/feenkcom/status/916300180848349185 > - At a higher level, it implies keeping track of measurements > https://twitter.com/AliakseiSyrel/status/915203525931622400 > - And of transformations: > https://twitter.com/feenkcom/status/919603739656417281 > https://twitter.com/feenkcom/status/917116164484096001 > - The BlScalableElement is now working properly > > GT Examples: > - The current repository with unary-based examples is at: > https://github.com/feenkcom/gtoolkit-examples > - We now have a runner in the inspector that allows us to both see the > source code and run and play with the resulting object: > https://twitter.com/feenkcom/status/923210686204989442 > - Andrei made the âafterâ behavior to work with unary examples. > > Cheers, > The feenk team > > -- > www.tudorgirba.com > www.feenk.com > > "Being happy is a matter of choice." > > > > > > -- ClÃ©ment BÃ©ra Pharo consortium engineer https://clementbera.wordpress.com/ BÃ¢timent B 40, avenue Halley 59650 Villeneuve d'Ascq

Oct. 26, 2017