about dateAndTime and TimeStamp
one of these days we will have to remove TimeStamp because it just adds noise to the system (in fact I would not have any problem to see DateAndTime renamed as timestamp - but having the two for nothing looks useless to me). Stef
Am 26.02.2014 um 21:29 schrieb Pharo4Stef <pharo4Stef@free.fr>:
one of these days we will have to remove TimeStamp because it just adds noise to the system (in fact I would not have any problem to see DateAndTime renamed as timestamp - but having the two for nothing looks useless to me).
+100 I donât really get what the use of it is, too. The mere fact that DateAndTime printString returns ISO8601 dates and TimeStamp does not makes me always use DateAndTime instead. My problem is that I often take a âsnapshot of timeâ (like in a log event) that for me as a non-native speaker is more related to the word timeStamp than DatenAndTime which sounds like a date and time management object. But everytime I write timeStamp := DateAndTime now it feels wrong. So I would be glad if there would be some clarification here. Norbert
I share the same idiomatic feeling with Norbert. However it is completely counter-intuitive (and counter productive too) that you can't instantiate a DateAndTime using the class side builder #date:time:, it is available in Pharo 2.0, but #date:time: was removed in a 3.0 image I tried a month ago. Regards! Esteban A. Maringolo 2014-02-26 17:36 GMT-03:00 Norbert Hartl <norbert@hartl.name>:
Am 26.02.2014 um 21:29 schrieb Pharo4Stef <pharo4Stef@free.fr>:
one of these days we will have to remove TimeStamp because it just adds noise to the system (in fact I would not have any problem to see DateAndTime renamed as timestamp - but having the two for nothing looks useless to me).
+100
I don't really get what the use of it is, too. The mere fact that DateAndTime printString returns ISO8601 dates and TimeStamp does not makes me always use DateAndTime instead. My problem is that I often take a "snapshot of time" (like in a log event) that for me as a non-native speaker is more related to the word timeStamp than DatenAndTime which sounds like a date and time management object. But everytime I write
timeStamp := DateAndTime now
it feels wrong. So I would be glad if there would be some clarification here.
Norbert
On 26 Feb 2014, at 23:03, Esteban A. Maringolo <emaringolo@gmail.com> wrote:
I share the same idiomatic feeling with Norbert.
However it is completely counter-intuitive (and counter productive too) that you can't instantiate a DateAndTime using the class side builder #date:time:, it is available in Pharo 2.0, but #date:time: was removed in a 3.0 image I tried a month ago.
strange, Did you report it before? Stef
Regards!
Esteban A. Maringolo
2014-02-26 17:36 GMT-03:00 Norbert Hartl <norbert@hartl.name>:
Am 26.02.2014 um 21:29 schrieb Pharo4Stef <pharo4Stef@free.fr>:
one of these days we will have to remove TimeStamp because it just adds noise to the system (in fact I would not have any problem to see DateAndTime renamed as timestamp - but having the two for nothing looks useless to me).
+100
I don't really get what the use of it is, too. The mere fact that DateAndTime printString returns ISO8601 dates and TimeStamp does not makes me always use DateAndTime instead. My problem is that I often take a "snapshot of time" (like in a log event) that for me as a non-native speaker is more related to the word timeStamp than DatenAndTime which sounds like a date and time management object. But everytime I write
timeStamp := DateAndTime now
it feels wrong. So I would be glad if there would be some clarification here.
Norbert
On 26 Feb 2014, at 23:03, Esteban A. Maringolo <emaringolo@gmail.com> wrote:
I share the same idiomatic feeling with Norbert.
However it is completely counter-intuitive (and counter productive too) that you can't instantiate a DateAndTime using the class side builder #date:time:, it is available in Pharo 2.0, but #date:time: was removed in a 3.0 image I tried a month ago.
No, it is not, DateAndTime class>>#date:time: is there alright.
Regards!
Esteban A. Maringolo
2014-02-26 17:36 GMT-03:00 Norbert Hartl <norbert@hartl.name>:
Am 26.02.2014 um 21:29 schrieb Pharo4Stef <pharo4Stef@free.fr>:
one of these days we will have to remove TimeStamp because it just adds noise to the system (in fact I would not have any problem to see DateAndTime renamed as timestamp - but having the two for nothing looks useless to me).
+100
I don't really get what the use of it is, too. The mere fact that DateAndTime printString returns ISO8601 dates and TimeStamp does not makes me always use DateAndTime instead. My problem is that I often take a "snapshot of time" (like in a log event) that for me as a non-native speaker is more related to the word timeStamp than DatenAndTime which sounds like a date and time management object. But everytime I write
timeStamp := DateAndTime now
it feels wrong. So I would be glad if there would be some clarification here.
Norbert
2014-02-27 5:12 GMT-03:00 Sven Van Caekenberghe <sven@stfx.eu>:
On 26 Feb 2014, at 23:03, Esteban A. Maringolo <emaringolo@gmail.com> wrote:
I share the same idiomatic feeling with Norbert.
However it is completely counter-intuitive (and counter productive too) that you can't instantiate a DateAndTime using the class side builder #date:time:, it is available in Pharo 2.0, but #date:time: was removed in a 3.0 image I tried a month ago.
No, it is not, DateAndTime class>>#date:time: is there alright.
Yes, it is now. I swear it wasn't there before :) Regards, -- Esteban.
Everything is ready to do just that, see https://pharo.fogbugz.com/f/cases/12197/should-remove-TimeStamp we just decided not to do the actual removal for 3.0 On 26 Feb 2014, at 21:29, Pharo4Stef <pharo4Stef@free.fr> wrote:
one of these days we will have to remove TimeStamp because it just adds noise to the system (in fact I would not have any problem to see DateAndTime renamed as timestamp - but having the two for nothing looks useless to me).
Stef
participants (4)
-
Esteban A. Maringolo -
Norbert Hartl -
Pharo4Stef -
Sven Van Caekenberghe