December 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] DateAndTime class>>midnight

by Camillo Bruni

midnight should be local time and DateAndTime work internally with UTC time only so yes this is wrong :), #seconds should be 0 and only the timezone has "special" values. On 2012-12-29, at 18:51, Max Leske <maxleske(a)gmail.com> wrote: > Possible bug in 2.0 which messes with equality checks: > > "DateAndTime midnight" will answer a DateAndTime with seconds set to the UTC seconds. In my case (UTC +1) that's -3600 seconds. I'm pretty sure that seconds should be 0. > This messes up equality checks for Date because Date class>>current uses #midnight. > > Please confirm and I'll open a bug report. > > Cheers, > Max

Dec. 29, 2012

[Pharo-project] DateAndTime class>>midnight

by Max Leske

Possible bug in 2.0 which messes with equality checks: "DateAndTime midnight" will answer a DateAndTime with seconds set to the UTC seconds. In my case (UTC +1) that's -3600 seconds. I'm pretty sure that seconds should be 0. This messes up equality checks for Date because Date class>>current uses #midnight. Please confirm and I'll open a bug report. Cheers, Max

Dec. 29, 2012

[Pharo-project] [update 2.0] #20461

by StÃ©phane Ducasse

20461 ----- - Issue 4018: Color class enhancement. Thanks Alexander Bergel. http://code.google.com/p/pharo/issues/detail?id=4018 - Issue 7187: Doit is broken in spec. Thanks Benjamin van Ryseghem http://code.google.com/p/pharo/issues/detail?id=7187 Diff information: http://ss3.gemstone.com/ss/Pharo20/Spec-Tools-StephaneDucasse.77.diff http://ss3.gemstone.com/ss/Pharo20/Graphics-Primitives-StephaneDucasse.97.d… Stef

Dec. 29, 2012

Re: [Pharo-project] 20460: It looks like we broke doit in Spec tools.

by StÃ©phane Ducasse

Thanks ben! Stef On Dec 29, 2012, at 3:26 PM, Benjamin wrote: > Ok, I open a bug entry then > > Ben > > On Dec 29, 2012, at 3:23 PM, StÃ©phane Ducasse wrote: > >> In the code pane of sender or implementor >> "self new foo" >> >> -> self is nil >> >> Stef >> On Dec 29, 2012, at 3:07 PM, Benjamin wrote: >> >>> Can you detail the steps to reproduce please ? >>> >>> Ben :) >>> >>> >>> On Dec 29, 2012, at 2:50 PM, StÃ©phane Ducasse wrote: >>> >>>> It looks like we broke doit in Spec tools. >>>> I need help :) >>>> >>>> Stef >>>> >>> >>> >> >> > >

Dec. 29, 2012

[Pharo-project] [update 2.0] #20460

by StÃ©phane Ducasse

20460 ----- - Issue 7178: MC cache resynching http://code.google.com/p/pharo/issues/detail?id=7178 Diff information: http://ss3.gemstone.com/ss/Pharo20/Ring-Monticello-StephaneDucasse.12.diff http://ss3.gemstone.com/ss/Pharo20/Ring-Core-Kernel-StephaneDucasse.88.diff

Dec. 29, 2012

Re: [Pharo-project] 20460: It looks like we broke doit in Spec tools.

by Benjamin

Ok, I open a bug entry then Ben On Dec 29, 2012, at 3:23 PM, StÃ©phane Ducasse wrote: > In the code pane of sender or implementor > "self new foo" > > -> self is nil > > Stef > On Dec 29, 2012, at 3:07 PM, Benjamin wrote: > >> Can you detail the steps to reproduce please ? >> >> Ben :) >> >> >> On Dec 29, 2012, at 2:50 PM, StÃ©phane Ducasse wrote: >> >>> It looks like we broke doit in Spec tools. >>> I need help :) >>> >>> Stef >>> >> >> > >

Dec. 29, 2012

Re: [Pharo-project] 20460: It looks like we broke doit in Spec tools.

by StÃ©phane Ducasse

In the code pane of sender or implementor "self new foo" -> self is nil Stef On Dec 29, 2012, at 3:07 PM, Benjamin wrote: > Can you detail the steps to reproduce please ? > > Ben :) > > > On Dec 29, 2012, at 2:50 PM, StÃ©phane Ducasse wrote: > >> It looks like we broke doit in Spec tools. >> I need help :) >> >> Stef >> > >

Dec. 29, 2012

Re: [Pharo-project] 20460: It looks like we broke doit in Spec tools.

by Benjamin

Can you detail the steps to reproduce please ? Ben :) On Dec 29, 2012, at 2:50 PM, StÃ©phane Ducasse wrote: > It looks like we broke doit in Spec tools. > I need help :) > > Stef >

Dec. 29, 2012

[Pharo-project] 20460: It looks like we broke doit in Spec tools.

by StÃ©phane Ducasse

It looks like we broke doit in Spec tools. I need help :) Stef

Dec. 29, 2012

Re: [Pharo-project] Extracting a ZipArchive in 2.0

by Camillo Bruni

try to have a look at the other ensure* methods on FileReference or AbstractFileReference. I think you need #ensureFile or #ensureDirectory :) On 2012-12-27, at 17:28, Vanessa PeÃ±a Araya <van.c.pena(a)gmail.com> wrote: > Hi, > > I want to extract a ZipArchive in Pharo 2.0, as the title says. I'm trying to do it with this: > > zipArchive > extractAllTo: aDirectory > informing: bar > overwrite: false > > I'm trying the new file system but my problem is that ZipArchiveMember calls a method called "assureExistence", which does not exist... anywhere. > > Has anyone experience something like this? > > Thanks, > Vanessa. >

Dec. 28, 2012