I guess it depends on how you'd like to represent a date and time.
We may have 2 representations here, the DateAndTime object and the string.
If you consider that the string '1901-01-01T00:00:00+12:00' actually *
represents* that day and time and it's not just the way you would print it,
then I
On Mar 19, 2010, at 7:39 AM, Carla F. Griggio wrote:
I guess it depends on how you'd like to represent a date and time.
We may have 2 representations here, the DateAndTime object and the string. If
you consider that the string '1901-01-01T00:00:00+12:00' actually represents
that day and
in Squeak
(aDateAndTime offset: '0:12:00:00') = '1901-01-01T00:00:00+12:00'
true
in pharo
(aDateAndTime offset: '0:12:00:00') = '1901-01-01T00:00:00+12:00'.
false.
Apparently the false in pharo comes from a bug in readFrom: in DateAndTime
Now the question
2010/3/17 stephane ducasse stephane.duca...@free.fr:
in Squeak
(aDateAndTime offset: '0:12:00:00') = '1901-01-01T00:00:00+12:00'
true
in pharo
(aDateAndTime offset: '0:12:00:00') = '1901-01-01T00:00:00+12:00'.
false.
Apparently the false in pharo comes from
On 17 March 2010 13:13, Nicolas Cellier
nicolas.cellier.aka.n...@gmail.com wrote:
2010/3/17 stephane ducasse stephane.duca...@free.fr:
in Squeak
(aDateAndTime offset: '0:12:00:00') = '1901-01-01T00:00:00+12:00'
true
in pharo
(aDateAndTime offset: '0:12:00:00') =
I would expect = to be
reflexive self assert: (a = a).
symmetric self assert: (a = b) == (b = a).
transitive self assert: (a = b) (b = c) == (a = c).
Date= does not seem to meet my expectations
Yes the more I think about it the more I'm against this automatic conversion.
