Re: [Pharo-users] Bug in Date>>readFrom:pattern: ? Pharo2.0

2013-07-29 Thread Marcus Denker
On Jul 30, 2013, at 12:47 AM, José Comesaña wrote: > I think so. I think Stef created 10869 and I 10870. I had made the > corrections and written the tests. Anyway, it is possible that I had made it > bad. I thought I had commited the slice, but... > > If you tell me how, I will do it again.

Re: [Pharo-users] Bug in Date>>readFrom:pattern: ? Pharo2.0

2013-07-29 Thread José Comesaña
I think so. I think Stef created 10869 and I 10870. I had made the corrections and written the tests. Anyway, it is possible that I had made it bad. I thought I had commited the slice, but... If you tell me how, I will do it again. Regards 2013/7/29 Marcus Denker > > On Jul 29, 2013, at 2:34

Re: [Pharo-users] Bug in Date>>readFrom:pattern: ? Pharo2.0

2013-07-29 Thread Marcus Denker
On Jul 29, 2013, at 2:34 PM, José Comesaña wrote: > It was already discussed and modified: > https://pharo.fogbugz.com/default.asp?10869 > This one is just an open report… no action was done. I have merged it into Issue 11222 But there is a third issue about exactly the same, this I think

Re: [Pharo-users] Bug in Date>>readFrom:pattern: ? Pharo2.0

2013-07-29 Thread José Comesaña
It was already discussed and modified: https://pharo.fogbugz.com/default.asp?10869 Regards 2013/7/24 Sabine Knöfel > Hi, > > Date readFrom: '4.2.13' readStream pattern: 'd.m.yy' > > Does not return 4.2.2013 but 4.2.0013 > > The comment is saying > "A year given using only two decimals is consid

Re: [Pharo-users] Bug in Date>>readFrom:pattern: ? Pharo2.0

2013-07-24 Thread Sven Van Caekenberghe
On 24 Jul 2013, at 18:20, Stéphane Ducasse wrote: > I remember that once camillo suggested to use the same approach as in dart > where you can specify a strategy. The ZTimestamp package contains such an example-based parser/formatter (load from the config browser or from http://www.smalltalk

Re: [Pharo-users] Bug in Date>>readFrom:pattern: ? Pharo2.0

2013-07-24 Thread Stéphane Ducasse
I remember that once camillo suggested to use the same approach as in dart where you can specify a strategy. > I agree > > The comment of mmdd is saying > "Format the date in ISO 8601 standard like '2002-10-22' > The result is of fixed size 10 characters long.." > > so

Re: [Pharo-users] Bug in Date>>readFrom:pattern: ? Pharo2.0

2013-07-24 Thread Sabine Knöfel
I agree The comment of mmdd is saying "Format the date in ISO 8601 standard like '2002-10-22' The result is of fixed size 10 characters long.." so I would say the selector is not choosen very careful. There is a discussion in Fogbuz about >>readFrom:pattern: https://pharo.fog

Re: [Pharo-users] Bug in Date>>readFrom:pattern: ? Pharo2.0

2013-07-24 Thread Mariano Martinez Peck
I also hate #mmdd Date today mmdd -> '2013-07-24' I would expect '20130724' Cheers, On Wed, Jul 24, 2013 at 5:59 AM, Sabine Knöfel wrote: > Hi, > > I created a bug, hoping that I filled out every field correctly. > > > https://pharo.fogbugz.com/f/cases/11222/Date-readFrom-pattern-year

Re: [Pharo-users] Bug in Date>>readFrom:pattern: ? Pharo2.0

2013-07-24 Thread Sabine Knöfel
Hi, I created a bug, hoping that I filled out every field correctly. https://pharo.fogbugz.com/f/cases/11222/Date-readFrom-pattern-year-2-decimals-not-20xx-but-00xx Sabine On Wed, Jul 24, 2013 at 9:52 AM, Stéphane Ducasse [via Smalltalk] wrote: > Hello Sabine > probably a bug. > If you can wri

Re: [Pharo-users] Bug in Date>>readFrom:pattern: ? Pharo2.0

2013-07-24 Thread Stéphane Ducasse
Hello Sabine probably a bug. If you can write some tests and publish them on the bugtracker this will help. If you provide the fix (it will be faster to get it fixed) please run the tests to make sure that we do not introduce side effects. Stef > Hi, > > Date readFrom: '4.2.13' readStream patte

[Pharo-users] Bug in Date>>readFrom:pattern: ? Pharo2.0

2013-07-24 Thread Sabine Knöfel
Hi, Date readFrom: '4.2.13' readStream pattern: 'd.m.yy' Does not return 4.2.2013 but 4.2.0013 The comment is saying "A year given using only two decimals is considered to be >2000" So, the comment is not ok or this is a bug? Sabine -- View this message in context: http://forum.world.st/Bu