you are welcome :)
On Jun 9, 2013, at 12:53 PM, José Comesaña wrote:
> Done.
>
> Sorry for my ignorance, :).
>
> Thanks
>
> 2013/6/7 Stéphane Ducasse
> thanks :)
> This is less work for us and the process can automatically check the code and
> run the tests automatically.
> Stef
>
>
Done.
Sorry for my ignorance, :).
Thanks
2013/6/7 Stéphane Ducasse
> thanks :)
> This is less work for us and the process can automatically check the code
> and run the tests automatically.
> Stef
>
>
thanks :)
This is less work for us and the process can automatically check the code and
run the tests automatically.
Stef
On Jun 7, 2013, at 10:16 PM, José Comesaña wrote:
> Ok, I will correct it tomorrow.
>
> Txs
>
>
>
> El 07/06/2013, a las 21:45, Stéphane Ducasse
> escribió:
>
>> Jose
Ok, I will correct it tomorrow.
Txs
El 07/06/2013, a las 21:45, Stéphane Ducasse
escribió:
> Jose
>
> normally we do not summit code in the pane of the bug tracker, we commit a
> slice (click + slice in the monticello browser)
> in the inbox folder.
>
> Stef
>
> On Jun 7, 2013, at 9:12
Jose
normally we do not summit code in the pane of the bug tracker, we commit a
slice (click + slice in the monticello browser)
in the inbox folder.
Stef
On Jun 7, 2013, at 9:12 PM, Stéphane Ducasse wrote:
> tx I will look at it.
>
> Stef
>
> On Jun 7, 2013, at 8:57 PM, José Comesaña wrot
tx I will look at it.
Stef
On Jun 7, 2013, at 8:57 PM, José Comesaña wrote:
> Done.
>
> I hope I have made it correctly. If not, please tell me.
>
> Regards
>
> 2013/6/7 Stéphane Ducasse
> Here it is https://pharo.fogbugz.com/default.asp?10869
>
> Stef
>
>
>
>
> On Jun 7, 2013, at 8:17
Done.
I hope I have made it correctly. If not, please tell me.
Regards
2013/6/7 Stéphane Ducasse
> Here it is https://pharo.fogbugz.com/default.asp?10869
>
> Stef
>
>
>
>
> On Jun 7, 2013, at 8:17 PM, Stéphane Ducasse
> wrote:
>
>
>
> Hi again.
>
> I have one first test for #readFrom:pattern:
Here it is https://pharo.fogbugz.com/default.asp?10869
Stef
On Jun 7, 2013, at 8:17 PM, Stéphane Ducasse wrote:
>
>
>> Hi again.
>>
>> I have one first test for #readFrom:pattern:. What can I do now to send it,
>> where, to whom?.
>
> I will create a bug entry for you and you create a sl
> Hi again.
>
> I have one first test for #readFrom:pattern:. What can I do now to send it,
> where, to whom?.
I will create a bug entry for you and you create a slice with the test and the
fix and you publish it in the pharo inbox.
Stef
>
> Regards
>
> 2013/6/7 Sven Van Caekenberghe
>
Hi again.
I have one first test for #readFrom:pattern:. What can I do now to send it,
where, to whom?.
Regards
2013/6/7 Sven Van Caekenberghe
>
> On 07 Jun 2013, at 14:28, José Comesaña wrote:
>
> > Answers in red.
> >
> > Regards
> >
> > 2013/6/7 Sven Van Caekenberghe
> >
> > On 07 Jun 2013
>>
>>
>> I had made the fixes myself, creating a new class for dates (I don't need
>> the complexity of Date just for determining if a date is past, I don't need
>> date arithmetic either). I just wanted to inform, mainly because the bug
>> seems to be still present in Pharo 3.0.
>>
>> Anyway
can you open a bug entry and publish a slice so that we do not fix it.
Stef
On Jun 7, 2013, at 12:36 PM, Sven Van Caekenberghe wrote:
> Hi José,
>
> On 07 Jun 2013, at 12:02, José Comesaña wrote:
>
>> Hello everybody.
>>
>> I would like to add a new improvement to this thread.
>>
>> I hav
On 07 Jun 2013, at 14:28, José Comesaña wrote:
> Answers in red.
>
> Regards
>
> 2013/6/7 Sven Van Caekenberghe
>
> On 07 Jun 2013, at 13:26, José Comesaña wrote:
>
> > Thank you Sven.
> >
> > I had made the fixes myself, creating a new class for dates (I don't need
> > the complexity of
Answers in red.
Regards
2013/6/7 Sven Van Caekenberghe
>
> On 07 Jun 2013, at 13:26, José Comesaña wrote:
>
> > Thank you Sven.
> >
> > I had made the fixes myself, creating a new class for dates (I don't
> need the complexity of Date just for determining if a date is past, I don't
> need date
On 07 Jun 2013, at 13:26, José Comesaña wrote:
> Thank you Sven.
>
> I had made the fixes myself, creating a new class for dates (I don't need the
> complexity of Date just for determining if a date is past, I don't need date
> arithmetic either). I just wanted to inform, mainly because the b
On 6/6/2013 2:14 PM, Camillo Bruni wrote:
can you save an image with the inspector opened on both x and y, x asTime and y
asTime
and provide a link to it? like that I can inspect it in all detail...
yes. probably tomorrow.
please ping me if I forget.
thanks
On 2013-06-06, at 17:51, dmacq
Thank you Sven.
I had made the fixes myself, creating a new class for dates (I don't need
the complexity of Date just for determining if a date is past, I don't need
date arithmetic either). I just wanted to inform, mainly because the bug
seems to be still present in Pharo 3.0.
Anyway, your solut
Hi José,
On 07 Jun 2013, at 12:02, José Comesaña wrote:
> Hello everybody.
>
> I would like to add a new improvement to this thread.
>
> I have noticed that Date class has a bug, or at least something to improve in
> readFrom:pattern: method. The initial comment states that "A year given usi
Hello everybody.
I would like to add a new improvement to this thread.
I have noticed that Date class has a bug, or at least something to improve
in readFrom:pattern: method. The initial comment states that "A year given
using only two decimals is considered to be >2000.".
But this seems to be i
can you save an image with the inspector opened on both x and y, x asTime and y
asTime
and provide a link to it? like that I can inspect it in all detail...
On 2013-06-06, at 17:51, dmacq wrote:
> I tried it again this morning and still had the problem.
>
> This is interesting.
>
> | x y |
>
I tried it again this morning and still had the problem.
This is interesting.
| x y |
x := DateAndTime year: 1991 day: 196 hour: 20 minute: 5 second: 7.
y := DateAndTime year: 1991 month: 7 day: 15 hour: 20 minute: 5 second: 7.
x = y <-- True
But
| x y |
x := DateAndTime year:
On 05/06/13 9:02 PM, dmacq wrote:
DateAndTime now asTime inspect -> 8:58:38.218 pm which is correct.
THis is from a virgin image (no package imports) created by unzipping the
Windows download.
I will try a different DateAndTime instance creation method tomorrow and let
you know.
This is st
DateAndTime now asTime inspect -> 8:58:38.218 pm which is correct.
THis is from a virgin image (no package imports) created by unzipping the
Windows download.
I will try a different DateAndTime instance creation method tomorrow and let
you know.
This is strange. Thanks.
--
View this mess
On 2013-06-06, at 02:53, dmacq wrote:
> TimeZone local inspect > a TimeZone(LT-4:00)
> TimeZone local offset inspect -> aDuration -0:04:00:00
that seems normal. can you upload your image somewhere (dropbox) and have an
inspector open on the strange DateAndTime instance?
and another try
TimeZone local inspect > a TimeZone(LT-4:00)
TimeZone local offset inspect -> aDuration -0:04:00:00
--
View this message in context:
http://forum.world.st/DateAndTime-asTime-tp4691870p4691877.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
it keeps on being strange ;), another try, what is your time zone?
TimeZone local inspect
TimeZone local offset inspect
On 2013-06-06, at 01:14, dmacq wrote:
> SystemVersion current ---> Pharo2.0 of 7 March 2013 update 20596
>
> The string is from the inspector window.
>
> I get the same thin
SystemVersion current ---> Pharo2.0 of 7 March 2013 update 20596
The string is from the inspector window.
I get the same thing in a fresh image.
--
View this message in context:
http://forum.world.st/DateAndTime-asTime-tp4691870p4691873.html
Sent from the Pharo Smalltalk Users mailing list ar
On 2013-06-06, at 00:41, dmacq wrote:
> In Pharo V2, if I execute this snippet:
>
> | x |
> x := DateAndTime year: 1991 day: 196 hour: 20 minute: 5 second: 7.
> x asTime inspect
>
> I get '12:0-54:0-53 am' which is not what I expect.
- where did you get this string from? that looks very stran
28 matches
Mail list logo
