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

Re: [Pharo-project] DateAndTime millisecond is always 0

by StÃ©phane Ducasse

so simple you see if people wants to get that in pharo - get a changeset out of the text - check in cuis if there are other changes - tests? Stef On Jan 15, 2011, at 9:50 AM, Adrian Lienhard wrote: > On Jan 15, 2011, at 09:21 , StÃ©phane Ducasse wrote: > >> >> On Jan 14, 2011, at 11:24 AM, Denis Kudriashov wrote: >> >>> Sorry, >>> >>> I meen DateAndTime now millisecond and DateAndTime now nanoSecond. >>> >>> As I write in last mail. I found cuis fix of this in Pharo issues >> >> >> where? > > Denis sent a link to the issue in question in a previous mail in this thread: > > http://code.google.com/p/pharo/issues/detail?id=3236 > > Adrian > > > __________________________ > www.adrian-lienhard.ch > twitter.com/adrianlienhard > >

Jan. 15, 2011

Re: [Pharo-project] DateAndTime millisecond is always 0

by StÃ©phane Ducasse

Thanks I could not see it ;/ Stef On Jan 15, 2011, at 9:50 AM, Adrian Lienhard wrote: > On Jan 15, 2011, at 09:21 , StÃ©phane Ducasse wrote: > >> >> On Jan 14, 2011, at 11:24 AM, Denis Kudriashov wrote: >> >>> Sorry, >>> >>> I meen DateAndTime now millisecond and DateAndTime now nanoSecond. >>> >>> As I write in last mail. I found cuis fix of this in Pharo issues >> >> >> where? > > Denis sent a link to the issue in question in a previous mail in this thread: > > http://code.google.com/p/pharo/issues/detail?id=3236 > > Adrian > > > __________________________ > www.adrian-lienhard.ch > twitter.com/adrianlienhard > >

Jan. 15, 2011

Re: [Pharo-project] we will start 1.3 really soon

by Adrian Lienhard

Cool :) BTW, I have a question related to 1.2 from a user's perspective: could we generate a summary to help people migrate from 1.1.1 to 1.2? In particular, the question is which changes in 1.2 are not backwards compatible and may break my code? I've been a bit out of the loop during the last months... so at least for me this is not obvious ;). There's http://code.google.com/p/pharo/wiki/ActionsInPharoOneDotTwo but it doesn't tell the important bits. Cheers, Adrian On Jan 15, 2011, at 09:27 , StÃ©phane Ducasse wrote: > Hi guys > > there are some minors fixes to be addressed (like the preferences use in dev) but we will go 1.3 probably this evening and > we will start to harvest a large list of pending issues. If you have seen fixes in squeak that you think are good please add a bug entry. > After that we will plan for the big changes in 1.3 for me > I would like to see > - collection enh (finishing hashed collection) > - weak structure support > - announcement using weak structure > - file system use > - new package implementation (cyrille worked and will continue to really make sure everything works) > - real beta of OPAL > The goal is to have a release for 1.3 by June/July. > > Stef >

Jan. 15, 2011

Re: [Pharo-project] new Cog VMs

by Philippe Marschall

On 10.01.2011 01:28, Eliot Miranda wrote: > Hi All, > > find new VMs in VM.r2344/ > <http://www.mirandabanda.org/files/Cog/VM/VM.r2344/> (SimpleStackBasedCogit) > and VM.r2345/ > <http://www.mirandabanda.org/files/Cog/VM/VM.r2345/> (StackToRegisterMappingCogit) > and VMMaker-oscog-45. These fix a bug that could cause crashes when > converting an interpreted method to a machine-code method on backward > branch (i.e. when the Vm detects an interpreted method is looping). > > I hope there are no new issues with VM.r2344/ > <http://www.mirandabanda.org/files/Cog/VM/VM.r2344/> (SimpleStackBasedCogit). > However, Matthew Fulmer has found that on linux the VM.r2343/ > <http://www.mirandabanda.org/files/Cog/VM/VM.r2343/> VM.r2345/ > <http://www.mirandabanda.org/files/Cog/VM/VM.r2345/> (StackToRegisterMappingCogit) > VMs crash immediately loading Squeak4.2-10856-beta.image. I can > reproduce this but haven't had time to investigate. > The StackToRegisterMappingCogit VMs do start up this image on Mac and > Windows. > > Agan thanks for pounding on these. I may not be able to attend to the > linux/StackToRegisterMappingCogit/Squeak4.2-10856-beta.image until next > weekend. Apologies. r2346 fixes the issues I sometimes had with when the stack would be messed up the first time a method is executed. Cheers Philippe

Jan. 15, 2011

Re: [Pharo-project] [Pharo-users] Where do I find KeyedSet?

by HernÃ¡n Morales Durand

Hi Stef 2011/1/15 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > > On Jan 14, 2011, at 6:24 PM, HernÃ¡n Morales Durand wrote: > >> Try PluggableSet >> >> http://www.mail-archive.com/pharo-project@lists.gforge.inria.fr/msg22890.ht… >> >> Is there a way for you guys to deprecate deleted classes or mantain a >> record of deleted behaviors? (IIRC VW did this from 2.x versions) > > We try but we do not have the engineers of VW. > Now find somebody that pay us just 3 engineers full time for two years and you will not > recognized pharo and its process. I know we are very few, but what about this idea, instead of just deleting a class we may adopt these simple rules: 1 - If deleting a class add the deleted class name somewhere (in a method?) 2 - If renaming a class, make the class to know its previous names like #previousNames (Norberto Manzanos implemented this for his own package management and I think is a great idea) doesn't require tools, just some consensus and maybe a modified #deleteClass to enforce this "policy" it sounds feasible for you? what do you think? HernÃ¡n

Jan. 15, 2011

Re: [Pharo-project] DateAndTime millisecond is always 0

by Adrian Lienhard

On Jan 15, 2011, at 09:21 , StÃ©phane Ducasse wrote: > > On Jan 14, 2011, at 11:24 AM, Denis Kudriashov wrote: > >> Sorry, >> >> I meen DateAndTime now millisecond and DateAndTime now nanoSecond. >> >> As I write in last mail. I found cuis fix of this in Pharo issues > > > where? Denis sent a link to the issue in question in a previous mail in this thread: http://code.google.com/p/pharo/issues/detail?id=3236 Adrian __________________________ www.adrian-lienhard.ch twitter.com/adrianlienhard

Jan. 15, 2011

[Pharo-project] we will start 1.3 really soon

by StÃ©phane Ducasse

Hi guys there are some minors fixes to be addressed (like the preferences use in dev) but we will go 1.3 probably this evening and we will start to harvest a large list of pending issues. If you have seen fixes in squeak that you think are good please add a bug entry. After that we will plan for the big changes in 1.3 for me I would like to see - collection enh (finishing hashed collection) - weak structure support - announcement using weak structure - file system use - new package implementation (cyrille worked and will continue to really make sure everything works) - real beta of OPAL The goal is to have a release for 1.3 by June/July. Stef

Jan. 15, 2011

Re: [Pharo-project] DateAndTime millisecond is always 0

by StÃ©phane Ducasse

On Jan 14, 2011, at 11:24 AM, Denis Kudriashov wrote: > Sorry, > > I meen DateAndTime now millisecond and DateAndTime now nanoSecond. > > As I write in last mail. I found cuis fix of this in Pharo issues where? Denis please provide more information else we all have to spend more time to answer and decide the next action. Stef > > 2011/1/14 Adrian Lienhard <adi(a)netstyle.ch> > Hi Denis, > > There's no method milliseconds (at least in my Pharo 1.1.1 image). Can you be more specific? > > I assume you want to get the milli seconds of a timestamp, rather than the millisecond clock (DateAndTime millisecondClockValue). > > When you create a new timestamp (TimeStamp now) the milli/nano seconds are indeed 0. The reason is that the timestamp is initialized from "Time totalSeconds". > > So I consider this not as a bug but something that could be improved. > > Cheers, > Adrian > > BTW, I remember having seen a fix on Mantis (= Squeak bug tracker) which asserts that TimeStamp now < TimeStamp now. > > > On Jan 14, 2011, at 10:20 , Denis Kudriashov wrote: > > > Hello. > > > > How I can get current time milliseconds parameter? > > > > I try DateAndTime millisecond. But it always zero. > > And DateAndTime nanoSecond is always zero too. > > > > Is it bug? > > > > I use Pharo1.1 > > >

Jan. 15, 2011

Re: [Pharo-project] about GLMOrangeUITheme [WAS] Re: [update 1.2] #12302

by StÃ©phane Ducasse

Improve the infrastructure so that we can get rid of most of the subclasses. Now the best way to make sure that this will happen is that some people see it right in front of their nose. Did you notice for example that we were just some to attend the irc? So how can we really communicate? Stef > > > On Thu, Jan 13, 2011 at 9:15 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > 12302 > ----- > > - GLMOrangeUITheme. Thanks Igor Stasenko > > I don't agree with this kind of changes. > Tomorrow I want Watery2BlackTheme and GLMYellowUITHeme and what? we are going to integrate it also? > > I don't understand. The change should be to create a setting to set the color and then igor runs a script in his own image that set it to orange. Me to yellow. And you to pink. > > > - Issue 3538: Add a "Browse test" in the TestRunner failed/error list. Thanks Benjamin van Ryseghem > > Stef >

Jan. 15, 2011

Re: [Pharo-project] Eeekk.. Morphic-Themes are now part of Morphic package

by StÃ©phane Ducasse

when you send a fix, it is better that this is well structured. I do not have a super brain to get exactly in your mind set so the duller the integrator job the better. We verify that there is no mess and that the system load well but I would like to open the process. Stef > I was surprised to see it part of morphic. It introducing dependency loop, > > Actually the name 'Morphic-Themes' was only a suggestion how to name a > separate package, > but not meant to merge it with Morphic. > > we should fix that now. > > -- > Best regards, > Igor Stasenko AKA sig. >

Jan. 15, 2011