Re: Issue 3806 in pharo: Duration>>hours is broken

Comment #13 on issue 3806 by [hidden email]: Duration>>hours is  
broken
http://code.google.com/p/pharo/issues/detail?id=3806

So we break the most obvious prose in the name of ANSI? Even when we have  
suffered consequences because of it? Breaks intuition in every possible way  
(and we decided to patch it in the comments!) This is not even consistent  
with smalltalk's intent.

Guys making a system less intuitive may seem smart to some people but is  
actually making us look either stupid or masochists.

Is the standard so freaking sacred? wonder why...




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

Comment #14 on issue 3806 by [hidden email]: Duration>>hours is  
broken
http://code.google.com/p/pharo/issues/detail?id=3806

If ANSI is sacred is a different discussion.

I think Joachim summarizes it very well:  
http://joachimtuchel.wordpress.com/2011/04/29/durations-and-the-ansi-standard/


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

Comment #15 on issue 3806 by [hidden email]: Duration>>hours is  
broken
http://code.google.com/p/pharo/issues/detail?id=3806

the asHours seems like a path of least pain. But yes this 2 days hours sucks


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

Updates:
        Labels: Type-Cleanup

Comment #16 on issue 3806 by [hidden email]: Duration>>hours is  
broken
http://code.google.com/p/pharo/issues/detail?id=3806

So what is the next action on this report?

Close? Change something?


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

Updates:
        Status: Workneeded

Comment #17 on issue 3806 by [hidden email]: Duration>>hours is  
broken
http://code.google.com/p/pharo/issues/detail?id=3806

no comment since sept 24: Close


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

Comment #18 on issue 3806 by [hidden email]: Duration>>hours is  
broken
http://code.google.com/p/pharo/issues/detail?id=3806

added conversion methods and tests in
SLICE-Issue-3806-Duration-hours-is-broken-CamilloBruni.1

but there's still a question regarding the returned value, IMO all the  
conversion methods should return a float / fraction. I didn't touch  
asSeconds but that one only return the seconds part of a duration ignoring  
all more detailed specs


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

Comment #19 on issue 3806 by [hidden email]: Duration>>hours is  
broken
http://code.google.com/p/pharo/issues/detail?id=3806

hence, is not converting (information gets destroyed)


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

Updates:
        Status: FixToInclude
        Labels: Milestone-1.4

Comment #20 on issue 3806 by [hidden email]: Duration>>hours is  
broken
http://code.google.com/p/pharo/issues/detail?id=3806

Thanks camillo


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

Updates:
        Status: Integrated

Comment #21 on issue 3806 by [hidden email]: Duration>>hours is  
broken
http://code.google.com/p/pharo/issues/detail?id=3806

in 14263


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