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

Re: [Pharo-dev] where the...

by Eliot Miranda

On Thu, Jul 31, 2014 at 11:52 PM, Ben Coman <btc(a)openinworld.com> wrote: > Eliot Miranda wrote: > > > > > On Thu, Jul 31, 2014 at 9:48 PM, stepharo <stepharo(a)free.fr> wrote: > >> I can tell you that I do not like jenkins but we have it, it works and it >> is maintained. So I lobotomize myself when I use it and it looks ok :) >> > > I like it very much. But there's a lot of freedom to design the server > and make it easier to find results, etc. For example at Cadence Bob > Westergaard has put a lot of effort into our Jenkins server with tabs > grouping different build tasks by VM, Newspeak, Spur, etc. So I find it > easier to navigate than the Pharo one. In particular it would be great if > thee were pointers to the latest build artifacts on > https://ci.inria.fr/pharo/job/Pharo-4.0/. Is that possible? > > > I think the philosophy was to avoid the CI server also being a file sever > - but perhaps the job result could provide a link to the associated > uploaded http://files.pharo.org/image/40/xxxxx.zip > Ok, if one should go to files.pharo.org then there should be as many links to files.pharo.org in obvious places as possible. But if I, as an outside, think to myself "nbow where would I find the most recent build of Pharo 4?", I would go to the CI server. For me, philosophically, a CI server /is/ a server, of build artifacts, test results and benchmarks. > > cheers -ben > > > Stef >> >> On 1/8/14 01:36, Eliot Miranda wrote: >> >>> *&^% do I find build artifacts for >>> https://ci.inria.fr/pharo/job/Pharo-4.0/lastSuccessfulBuild/? There's >>> no pointer to an image/changes combo I can see. >>> -- >>> Aloha, >>> Eliot >> >> -- > Aloha, > Eliot > > -- Aloha, Eliot

Aug. 1, 2014

Re: [Pharo-dev] Floating point literals in debugger

by Natalia Tymchuk

Thank you. I donât need it, because I know what is written in my code, but it can be the problem for users and I think that it will good to fix it. Best regards, Natalia On Aug 1, 2014, at 5:07 PM, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > Hello, > > Natalia I don't think this is a known bug (few people use Float and Fraction in Pharo). > > The RBParser parse your floating pointers as Fraction and not as Float (I don't know why). > > In the debugger the bytecode pc to source code pointer is mapped by printing the AST. In this case, the AST node (RBLiteralNode) for your float holds a Fraction. The code to print a literal node is as follow: > > visitLiteralNode: aLiteralNode > aLiteralNode value isLiteral > ifFalse: [ self writeString: '''<an unprintable nonliteral value>''' ] > ifTrue: [ self writeString: aLiteralNode token storeString ] > > and isLiteral answers always false for a Fraction. > > A temporary patch consists in adding the method > > Fraction>>isLiteral > ^ true > > Then you can debug your code. > > However, I think a real patch would consists in adding the method isLiteral in Fraction but with correct code to answer true only if the fraction can be a literal. Something similar to Float>>#isLiteral. > > > 2014-08-01 15:40 GMT+02:00 Serge Stinckwich <serge.stinckwich(a)gmail.com>: > Yes, I see also the same problem. > > I didn't realize until now that : 1-1e-6 > is printed as a fraction (try print-it): > (999999/1000000) > > A little bit strange, no ? > > On Fri, Aug 1, 2014 at 3:05 PM, Natalia Tymchuk > <natalia.tymchuk(a)unikernel.net> wrote: > > Hello. > > When I have the following expression > > {1-1e-6. 1e-6. 0} > > in the code and then I debug it I get > > {(1 - '<an unprintable nonliteral value>'). > > '<an unprintable nonliteral value>'. > > 0}. > > > > Is it a known problem or should I report an issue on debug tracker? > > > > Best regards, > > Natalia > > > > > > -- > Serge Stinckwich > UCBN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://www.doesnotunderstand.org/ > >

Aug. 1, 2014

Re: [Pharo-dev] Floating point literals in debugger

by ClÃ©ment Bera

Hello, Natalia I don't think this is a known bug (few people use Float and Fraction in Pharo). The RBParser parse your floating pointers as Fraction and not as Float (I don't know why). In the debugger the bytecode pc to source code pointer is mapped by printing the AST. In this case, the AST node (RBLiteralNode) for your float holds a Fraction. The code to print a literal node is as follow: visitLiteralNode: aLiteralNode aLiteralNode value isLiteral ifFalse: [ self writeString: '''<an unprintable nonliteral value>''' ] ifTrue: [ self writeString: aLiteralNode token storeString ] and isLiteral answers always false for a Fraction. A temporary patch consists in adding the method Fraction>>isLiteral ^ true Then you can debug your code. However, I think a real patch would consists in adding the method isLiteral in Fraction but with correct code to answer true only if the fraction can be a literal. Something similar to Float>>#isLiteral. 2014-08-01 15:40 GMT+02:00 Serge Stinckwich <serge.stinckwich(a)gmail.com>: > Yes, I see also the same problem. > > I didn't realize until now that : 1-1e-6 > is printed as a fraction (try print-it): > (999999/1000000) > > A little bit strange, no ? > > On Fri, Aug 1, 2014 at 3:05 PM, Natalia Tymchuk > <natalia.tymchuk(a)unikernel.net> wrote: > > Hello. > > When I have the following expression > > {1-1e-6. 1e-6. 0} > > in the code and then I debug it I get > > {(1 - '<an unprintable nonliteral value>'). > > '<an unprintable nonliteral value>'. > > 0}. > > > > Is it a known problem or should I report an issue on debug tracker? > > > > Best regards, > > Natalia > > > > > > -- > Serge Stinckwich > UCBN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://www.doesnotunderstand.org/ > >

Aug. 1, 2014

Re: [Pharo-dev] Has someone ever built a "sort block generator"

by Camille Teruel

On 1 aoÃ»t 2014, at 16:50, Henrik Johansen <henrik.s.johansen(a)veloxit.no> wrote: > > On 01 Aug 2014, at 4:47 , Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > >> >> >> >> On Fri, Aug 1, 2014 at 11:31 AM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: >> Y asked for the same thing a few days ago in http://forum.world.st/Multiple-sorting-helper-td4770613.html >> >> Something like: >> sorter := MultipleSortCriteria new >> add: #lastName; >> add: [:each | each personalInfo age ] ascending: false. >> aCollection asSortedCollection: sorter. >> >> >> Exactly!!! >> And... what is most important for me, is that to the MultipleSortCriteria I would like to ask #sortBlock :) >> >> Thanks Esteban for better explaining what I was looking for ;) > > I always liked this approach: > http://objology.blogspot.no/2010/11/tag-sortfunctions-redux.html > > Donât think anyoneâs ported it to Pharo yet though. Yes it looks cool! We can try to port it then > > Cheers, > Henry

Aug. 1, 2014

Re: [Pharo-dev] Has someone ever built a "sort block generator"

by Camille Teruel

On 1 aoÃ»t 2014, at 16:47, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > > > On Fri, Aug 1, 2014 at 11:31 AM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > Y asked for the same thing a few days ago in http://forum.world.st/Multiple-sorting-helper-td4770613.html > > Something like: > sorter := MultipleSortCriteria new > add: #lastName; > add: [:each | each personalInfo age ] ascending: false. > aCollection asSortedCollection: sorter. > > > Exactly!!! > And... what is most important for me, is that to the MultipleSortCriteria I would like to ask #sortBlock :) To sort a collection with such an object it only has to answer #value:value:, so is there a special reason you want to generate a block from it? Because generating such blocks might be a bit cumbersome and the object already does the job, no? > > Thanks Esteban for better explaining what I was looking for ;) > > > you could add something like: > sorter := MultipleSortCriteria new > add: #lastName; > add: #firstName ascending: false nullsFirst: true. > aCollection asSortedCollection: sorter. > > Regards! > > > Esteban A. Maringolo > > > 2014-08-01 2:40 GMT-03:00 Damien Cassou <damien.cassou(a)gmail.com>: > > On Thu, Jul 31, 2014 at 10:50 PM, stepharo <stepharo(a)free.fr> wrote: > > what are you doing? > > > I think Mariano would like something like this: > > persons sorted: #(lastname firstname birthdate) asSortBlock > > that would sort by lastname, and if lastnames are equal by firstnames > and if both lastnames and firstnames are equal by birthdate. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill > > > > > > -- > Mariano > http://marianopeck.wordpress.com

Aug. 1, 2014

Re: [Pharo-dev] Has someone ever built a "sort block generator"

by phil＠highoctane.be

Grids, collections, and sorting/filtering + paging. And xls export. I guess we all have this kind of need in Seaside apps (and/or datatables). Maybe we could have a hangout about these things. I use the MagritteReport thing with some Twitter Bootstrap additions for reports. Is there any best practice article somewhere that you use as a reference for your designs? Phil On Friday, August 1, 2014, Henrik Johansen <henrik.s.johansen(a)veloxit.no> wrote: > > On 01 Aug 2014, at 4:47 , Mariano Martinez Peck <marianopeck(a)gmail.com > <javascript:_e(%7B%7D,'cvml','marianopeck(a)gmail.com');>> wrote: > > > > > On Fri, Aug 1, 2014 at 11:31 AM, Esteban A. Maringolo < > emaringolo(a)gmail.com > <javascript:_e(%7B%7D,'cvml','emaringolo(a)gmail.com');>> wrote: > >> Y asked for the same thing a few days ago in >> http://forum.world.st/Multiple-sorting-helper-td4770613.html >> >> Something like: >> sorter := MultipleSortCriteria new >> add: #lastName; >> add: [:each | each personalInfo age ] ascending: false. >> aCollection asSortedCollection: sorter. >> >> > Exactly!!! > And... what is most important for me, is that to the MultipleSortCriteria > I would like to ask #sortBlock :) > > Thanks Esteban for better explaining what I was looking for ;) > > > I always liked this approach: > http://objology.blogspot.no/2010/11/tag-sortfunctions-redux.html > > Donât think anyoneâs ported it to Pharo yet though. > > Cheers, > Henry > -- --- Philippe Back Visible Performance Improvements Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail:phil@highoctane.be | Web: http://philippeback.eu Blog: http://philippeback.be | Twitter: @philippeback Youtube: http://www.youtube.com/user/philippeback/videos High Octane SPRL rue cour Boisacq 101 | 1301 Bierges | Belgium Pharo Consortium Member - http://consortium.pharo.org/ Featured on the Software Process and Measurement Cast - http://spamcast.libsyn.com Sparx Systems Enterprise Architect and Ability Engineering EADocX Value Added Reseller

Aug. 1, 2014

Re: [Pharo-dev] Strange behavior of blocks

by Serge Stinckwich

On Fri, Aug 1, 2014 at 4:43 PM, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > Hello, > > Nice way to reproduce easily the SmallInteger bug :) > > | state values | > values := (1 to: 100000) collect: [ :t | state := { t . t + 1 . t + 2 }]. > values select: [ :e | e isInteger ] Maybe we should convert this as a test in order to avoid any regression in the future ? > This bug was present in some VMs and it is fixed in the latest VMs. Ok, thank you ClÃ©ment. I was not aware of this bug until now. > The stable Mac VM still have the bug. > > If you need a VM without the bug, go there: > > http://files.pharo.org/vm/pharo/30/ > > Click on your OS, then select the zip file named 'latest.zip' and download > it. > > The latest VM does not have the bug. I'm using PharoLauncher and apparently the mac OS X version still use the buggy VM. Thank you. Regards, -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

Aug. 1, 2014

Re: [Pharo-dev] Has someone ever built a "sort block generator"

by Henrik Johansen

On 01 Aug 2014, at 4:47 , Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > > > On Fri, Aug 1, 2014 at 11:31 AM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > Y asked for the same thing a few days ago in http://forum.world.st/Multiple-sorting-helper-td4770613.html > > Something like: > sorter := MultipleSortCriteria new > add: #lastName; > add: [:each | each personalInfo age ] ascending: false. > aCollection asSortedCollection: sorter. > > > Exactly!!! > And... what is most important for me, is that to the MultipleSortCriteria I would like to ask #sortBlock :) > > Thanks Esteban for better explaining what I was looking for ;) I always liked this approach: http://objology.blogspot.no/2010/11/tag-sortfunctions-redux.html Donât think anyoneâs ported it to Pharo yet though. Cheers, Henry

Aug. 1, 2014

Re: [Pharo-dev] Has someone ever built a "sort block generator"

by Mariano Martinez Peck

On Fri, Aug 1, 2014 at 11:31 AM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > Y asked for the same thing a few days ago in > http://forum.world.st/Multiple-sorting-helper-td4770613.html > > Something like: > sorter := MultipleSortCriteria new > add: #lastName; > add: [:each | each personalInfo age ] ascending: false. > aCollection asSortedCollection: sorter. > > Exactly!!! And... what is most important for me, is that to the MultipleSortCriteria I would like to ask #sortBlock :) Thanks Esteban for better explaining what I was looking for ;) > > you could add something like: > sorter := MultipleSortCriteria new > add: #lastName; > add: #firstName ascending: false nullsFirst: true. > aCollection asSortedCollection: sorter. > > Regards! > > > Esteban A. Maringolo > > > 2014-08-01 2:40 GMT-03:00 Damien Cassou <damien.cassou(a)gmail.com>: > > On Thu, Jul 31, 2014 at 10:50 PM, stepharo <stepharo(a)free.fr> wrote: >> > what are you doing? >> >> >> I think Mariano would like something like this: >> >> persons sorted: #(lastname firstname birthdate) asSortBlock >> >> that would sort by lastname, and if lastnames are equal by firstnames >> and if both lastnames and firstnames are equal by birthdate. >> >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >> "Success is the ability to go from one failure to another without >> losing enthusiasm." >> Winston Churchill >> >> > -- Mariano http://marianopeck.wordpress.com

Aug. 1, 2014

Re: [Pharo-dev] Strange behavior of blocks

by ClÃ©ment Bera

Hello, Nice way to reproduce easily the SmallInteger bug :) | state values | values := (1 to: 100000) collect: [ :t | state := { t . t + 1 . t + 2 }]. values select: [ :e | e isInteger ] This bug was present in some VMs and it is fixed in the latest VMs. The stable Mac VM still have the bug. If you need a VM without the bug, go there: http://files.pharo.org/vm/pharo/30/ Click on your OS, then select the zip file named 'latest.zip' and download it. The latest VM does not have the bug. 2014-08-01 15:20 GMT+02:00 Serge Stinckwich <serge.stinckwich(a)gmail.com>: > Dear all, > > using Sci-Smalltalk, we found with Natalia that sometimes blocks have > strange behavior : > https://groups.google.com/forum/#!topic/scismalltalk/HmGpTkzLOdQ > > I was able to create a more simpler example using only Pharo. > If you try, the following expression, there is no problem: > > |state values | > values := (1 to: 10000) collect: [ : t| state := { t. t+1. t+2.}]. > (1 to: 10000) do:[:i | (values at:i) at:2]. > > and you do more iterations, an error appears (Instances of > SmallInteger are not indexable), > because from time to time, an array is replaced by an integer: > > |state values | > values := (1 to: 100000) collect: [ : t| state := { t. t+1. t+2.}]. > (1 to: 100000) do:[:i | (values at:i) at:2]. > > and if you move the state variable inside the block, it works again : > > | values | > values := (1 to: 100000) collect: [ : t| |state| state := { t. t+1. t+2.}]. > (1 to: 100000) do:[:i | (values at:i) at:2]. > > Same problem in Pharo 3.0 or Pharo 4.0 > > Regards, > -- > Serge Stinckwich > UCBN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://www.doesnotunderstand.org/ > >

Aug. 1, 2014