Re: Issue 5441 in pharo: Fixing timestamp coherence for method changes

Updates:
        Summary: Fixing timestamp coherence for method changes

Comment #10 on issue 5441 by [hidden email]: Fixing timestamp  
coherence for method changes
http://code.google.com/p/pharo/issues/detail?id=5441

So the goal is to use DateAndTime instead of TimeStamp everywhere?


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #11 on issue 5441 by [hidden email]: Fixing timestamp  
coherence for method changes
http://code.google.com/p/pharo/issues/detail?id=5441

There is even the option to remove TimeStamp alltogether: look at the  
differences, it is only about formatting/parsing and the ISO format is  
preferrable anyway.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #12 on issue 5441 by [hidden email]: Fixing timestamp  
coherence for method changes
http://code.google.com/p/pharo/issues/detail?id=5441

Indeed the TimeStamp as it is now is useless.
If something we should have a time-zone-less time point. Consisting of an  
integer for the day and maybe a time indicator with a per second resolution  
(or if wished more, fractions of that).


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #13 on issue 5441 by [hidden email]: Fixing timestamp  
coherence for method changes
http://code.google.com/p/pharo/issues/detail?id=5441

I already did that and am using it myself.

It is called ZTimestamp, see http://mc.stfx.eu/Neo

It is faster and more efficient than DateAndTime.

;-)


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Labels: -Milestone-2.0 Milestone-3.0

Comment #14 on issue 5441 by [hidden email]: Fixing timestamp  
coherence for method changes
http://code.google.com/p/pharo/issues/detail?id=5441

I think we should do that in 3.0....


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker