February 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [ANN] NativeBoost project moved to new hosting: smalltalkhub

by Camillo Bruni

On 2013-02-05, at 12:52, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 4 February 2013 19:19, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> Igor >> >> I think that camillo made this because NativeBoost is an essential part of our infrastructure >> and this is good to know that it is working. >> So I think that we should thank camillo for the time he spent on that. >> > > It is pretty useless right now. If it would run on all platforms, it > would worth having. then add slaves.... you strike me with laziness again! > But in current state, It feels like extra micromanagement to me.

Feb. 5, 2013

Re: [Pharo-project] [ANN] NativeBoost project moved to new hosting: smalltalkhub

by Igor Stasenko

On 4 February 2013 19:19, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Igor > > I think that camillo made this because NativeBoost is an essential part of our infrastructure > and this is good to know that it is working. > So I think that we should thank camillo for the time he spent on that. > It is pretty useless right now. If it would run on all platforms, it would worth having. But in current state, It feels like extra micromanagement to me. > Stef > -- Best regards, Igor Stasenko.

Feb. 5, 2013

Re: [Pharo-project] [Pharo-users] Slides Fosdem13 from this morning

by Sven Van Caekenberghe

On 05 Feb 2013, at 11:40, Marcus Denker <marcus.denker(a)inria.fr> wrote: > On Feb 3, 2013, at 12:23 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> Hi, >> >> Here are my slides from the talk today at FOSDEM; >> >> http://marcusdenker.de/talks/13Fosdem/2013-FOSDEM-Pharo.pdf > > And on SlideShare (with >1000 views in a day, not badâ¦) > > http://www.slideshare.net/MarcusDenker/fosdem-13-pharo-20-update Cool ! And a good presentation as well. Sven -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

Feb. 5, 2013

Re: [Pharo-project] Slides Fosdem13 from this morning

by Marcus Denker

On Feb 3, 2013, at 12:23 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Hi, > > Here are my slides from the talk today at FOSDEM; > > http://marcusdenker.de/talks/13Fosdem/2013-FOSDEM-Pharo.pdf And on SlideShare (with >1000 views in a day, not badâ¦) http://www.slideshare.net/MarcusDenker/fosdem-13-pharo-20-update

Feb. 5, 2013

Re: [Pharo-project] Strange behaviour in Spec

by Andrei Vasile Chis

Hi, A very simple way to reproduce is to open a transcript and execute this code: 50 timesRepeat: [|list| list := ListComposableModel new. list items: #(1 2). list whenListChanged: [:aList| Transcript crShow: aList = list listItems]. list listItems. "Call listItems to set the cache" list items: #(1 2 3) ]. If should print both true and false. Every time it prins false the events were triggered in the wrong order. Andrei On Tue, Feb 5, 2013 at 9:26 AM, Goubier Thierry <thierry.goubier(a)cea.fr>wrote: > Le 04/02/2013 17:27, Andrei Vasile Chis a Ã©crit : > > Hi, >> >> While playing with spec I started to have some quite random and >> strange behaviour. >> I'll try to explain what happen, because it might be a nasty/not that >> nasty bug. >> >> I had a ListComposableModel and some very simple code like: >> aListComposableModel whenListChanged: [ :aList | >> aListComposableModel setSelectedItem: aList first ]. >> >> From time to time this code seem to randomly fail because the selection >> wasn't set. >> I manage to reduce the error to the following equivalent code: >> aListComposableModel whenListChanged: [ :aList | >> aList = aListComposableModel listItems ]. >> >> What happen was that sometimes the list held by the model was the >> previous list and not the new list, >> which was actually correctly passes to the block. >> >> This seem to be caused by the way ListComposableModel uses announcers to >> update its internal state. >> In ListComposableModel>>**registerEvents there is the code: listHolder >> whenChangedDo: [ self refreshListItems ]. >> >> This registers an announcement that should clear the cache: >> ListComposableModel >>refreshListItems >> listItemsCache := nil. >> ^ self changed: #listElementAt: >> >> In my code by using 'aListComposableModel whenListChanged:' I also >> register an event that should be executed >> when the elements of the list change. >> >> So by now the listHolder containing the elements of the list has two >> registered events. >> The problem is that in order for this to work correctly they have to >> execute in the order they >> were added: first invalidate the cache, then the other events registered >> by the user. >> However I do not think that announcers guarantee this. So from time to >> time they >> execute in the wrong way. This means that the code in the >> whenListChanged: block will >> execute in a state in which internaly aListComposableModel still >> contains the previous list. >> >> Does this make sense? >> > > Yes. It would mean the two announcers are kept in a Set... Maybe having > private and public events would be the way to go ? A private one for > clearing the cache and public ones, triggered after, for the > whenListChanged: block ? > > It would be nice to have a test case checking that. I'd be interested to > know this can happen with announcements. > > Thierry > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 > >

Feb. 5, 2013

[Pharo-project] [update 2.0] #20513

by Marcus Denker

20513 ----- Issue 7417: When future cant wait (fix potential caveat with Delay) http://code.google.com/p/pharo/issues/detail?id=7417 Issue 7419: smartchars broken http://code.google.com/p/pharo/issues/detail?id=7419 Issue 7418: Put a setting to enable/disable the uncommented class icon http://code.google.com/p/pharo/issues/detail?id=7418 Diff information: http://ss3.gemstone.com/ss/Pharo20/Nautilus-MarcusDenker.409.diff http://ss3.gemstone.com/ss/Pharo20/NECompletion-MarcusDenker.85.diff http://ss3.gemstone.com/ss/Pharo20/Kernel-MarcusDenker.1302.diff

Feb. 5, 2013

Re: [Pharo-project] pharo-contribution CI server

by Camillo Bruni

Chrstophe completed most of the migration, I contacted the maintainers, and I will kill the old jobs this week On 2013-02-04, at 15:46, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > + 1 > > After we can contact the cogdroid maintainer to see if he wants. > > Stef > >> >> On 2013-02-03, at 21:39, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >>> >>> On Feb 3, 2013, at 9:35 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: >>>> >>>> - Pharo-2.0-Kernel >>>> - CogDroid >>> >>> why this two are not pharo? because we do not maintain them? >>> I think they are important for us >> >> who maintains them, that is indeed the question. If they turn red, who can fix them? >> >> - Pharo 2.0 Kernel is basically red >> - CogDroid is red as well >> >> Did I ever hear any complaints? No, so they are not used nor maintained by us! >> => they go on pharo-contributions where they can grow until they are stable >> >> Everything under https://ci.inria.fr/pharo has to be green, otherwise it is bad >> publicity. Stuff under pharo-contribution can have any state, preferably green of >> course, but we do not care. >> >> Of course if we have people in our team that volunteer to run and fix the builds >> I am happy to keep them under /pharo. But otherwise it's just additional work >> >> > >

Feb. 5, 2013

Re: [Pharo-project] Strange behaviour in Spec

by Goubier Thierry

Le 04/02/2013 17:27, Andrei Vasile Chis a Ã©crit : > Hi, > > While playing with spec I started to have some quite random and > strange behaviour. > I'll try to explain what happen, because it might be a nasty/not that > nasty bug. > > I had a ListComposableModel and some very simple code like: > aListComposableModel whenListChanged: [ :aList | > aListComposableModel setSelectedItem: aList first ]. > > From time to time this code seem to randomly fail because the selection > wasn't set. > I manage to reduce the error to the following equivalent code: > aListComposableModel whenListChanged: [ :aList | > aList = aListComposableModel listItems ]. > > What happen was that sometimes the list held by the model was the > previous list and not the new list, > which was actually correctly passes to the block. > > This seem to be caused by the way ListComposableModel uses announcers to > update its internal state. > In ListComposableModel>>registerEvents there is the code: listHolder > whenChangedDo: [ self refreshListItems ]. > > This registers an announcement that should clear the cache: > ListComposableModel >>refreshListItems > listItemsCache := nil. > ^ self changed: #listElementAt: > > In my code by using 'aListComposableModel whenListChanged:' I also > register an event that should be executed > when the elements of the list change. > > So by now the listHolder containing the elements of the list has two > registered events. > The problem is that in order for this to work correctly they have to > execute in the order they > were added: first invalidate the cache, then the other events registered > by the user. > However I do not think that announcers guarantee this. So from time to > time they > execute in the wrong way. This means that the code in the > whenListChanged: block will > execute in a state in which internaly aListComposableModel still > contains the previous list. > > Does this make sense? Yes. It would mean the two announcers are kept in a Set... Maybe having private and public events would be the way to go ? A private one for clearing the cache and public ones, triggered after, for the whenListChanged: block ? It would be nice to have a test case checking that. I'd be interested to know this can happen with announcements. Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Feb. 5, 2013

Re: [Pharo-project] Nanosecond-precision DateAndTime?

by Sven Van Caekenberghe

On 05 Feb 2013, at 07:00, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Hello > > 2013/2/4 Igor Stasenko <siguctua(a)gmail.com> > On 4 February 2013 16:56, Igor Stasenko <siguctua(a)gmail.com> wrote: > > On 4 February 2013 16:48, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> Yes, I just can't understand all this code ;-) > >> > >> The nanoseconds seemed overly ambitious to me. > >> > >> That was one of the reasons I am using my own ZTimestamp (loadable from the Configuration browser), together with the confusion coming from timezones (they are not needed internally, only for representations). > >> > >> If you keep the julianDayNumber, you can fit millisecond precision in a small integer as milliSecondsSinceMidnight. > >> > >> 60 * 60 * 24 * 1000 < SmallInteger maxVal > >> > >> Ideally, there should be one Timestamp interface with multiple implementations of different precisions, mixed transparently. One should only pay the price (space or time) for extra features when they are really needed. > >> > > > > i am not against having highly precise storage format (which would > > allow storing at arbitrary precision).. > > what i don't understand is why having so much logic in order to > > emulate such precision: > > to my opinion, if OS/VM don't provides such precision, so be it.. use > > what is given, > > because doing so "neat" hacks with millisecond clock is just waste of > > code as to me, > > because it is really belongs to primitive (so you don't have chance to > > be interrupted, nor you need to wait till "new second" will happen :) > > ). > > > > clarification: > i meant, related to system time, like > DateAndTime>>now , or TimeStamp>>now.. > > > those two is by their nature is system-dependent.. and so, if > underlying system does not supports higher > than 1 ***second precision, there is no way how you will get it. > > A bit offtopic maybe but could you explain (or somebody) difference between DateAndTime and TimeStamp? When I need date and time object I always start to think what class I should use. There is basically no difference, the only difference is in their external representation. DateAndTime now is more portable, and has a more technically correct ISO representation. > For synthesizing dates and stamps (like reading from file) .. it is > another story (the logic in the methods i presented > is related only to system *current* time). > > > -- > Best regards, > Igor Stasenko. > >

Feb. 5, 2013

Re: [Pharo-project] Nanosecond-precision DateAndTime?

by Denis Kudriashov

Hello 2013/2/4 Igor Stasenko <siguctua(a)gmail.com> > On 4 February 2013 16:56, Igor Stasenko <siguctua(a)gmail.com> wrote: > > On 4 February 2013 16:48, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> Yes, I just can't understand all this code ;-) > >> > >> The nanoseconds seemed overly ambitious to me. > >> > >> That was one of the reasons I am using my own ZTimestamp (loadable from > the Configuration browser), together with the confusion coming from > timezones (they are not needed internally, only for representations). > >> > >> If you keep the julianDayNumber, you can fit millisecond precision in a > small integer as milliSecondsSinceMidnight. > >> > >> 60 * 60 * 24 * 1000 < SmallInteger maxVal > >> > >> Ideally, there should be one Timestamp interface with multiple > implementations of different precisions, mixed transparently. One should > only pay the price (space or time) for extra features when they are really > needed. > >> > > > > i am not against having highly precise storage format (which would > > allow storing at arbitrary precision).. > > what i don't understand is why having so much logic in order to > > emulate such precision: > > to my opinion, if OS/VM don't provides such precision, so be it.. use > > what is given, > > because doing so "neat" hacks with millisecond clock is just waste of > > code as to me, > > because it is really belongs to primitive (so you don't have chance to > > be interrupted, nor you need to wait till "new second" will happen :) > > ). > > > > clarification: > i meant, related to system time, like > DateAndTime>>now , or TimeStamp>>now.. > > > those two is by their nature is system-dependent.. and so, if > underlying system does not supports higher > than 1 ***second precision, there is no way how you will get it. > A bit offtopic maybe but could you explain (or somebody) difference between DateAndTime and TimeStamp? When I need date and time object I always start to think what class I should use. > > For synthesizing dates and stamps (like reading from file) .. it is > another story (the logic in the methods i presented > is related only to system *current* time). > > > -- > Best regards, > Igor Stasenko. > >

Feb. 5, 2013