Brent Pinkney-2 wrote:
Hi, I am that mental toddler that coded up the ANSI compliant date and time package.
Please refer to ANSI spec §5.8.2.11. I promise it will only take a minute.
Instead of a polite enquiry as to why the implementation is such, you had to define obvious for yourself and chuck in an insult. Bona fide arsehole
PS. Try now guess why there is both #seconds and #asSeconds.
Brent
Hi Brent, I think not everyone here knows the exact content from Smalltalk ANSI. When someone questions an implementation it is probably a good idea to first cross-reference the ANSI standard, so I have added a link to the http://webstore.ansi.org/RecordDetail.aspx?sku=ANSI+INCITS+319-1998+(R2007) ANSI INCITS 319-1998 (R2007) on http://www.world.st/about world.st/about and also made the draft PDF available. I noticed you mentioned someone insulted you? I probably missed that bit and I think everyone here agrees that there is no need to insult anyone, we are all adults here ... well at least I think so :) ANSI 5.8.2.11 Draft wrote:
5.8.2.11 Message: hours Synopsis Answer the number of complete hours in the receiver. Definition: Answer an between -23 and 23 inclusive that represents the number of complete hours in the receiver, after the number of complete days has been removed. If the receiver is less than #zero then the result will be less than or equal to 0. Return Values unspecified Errors None
ps. I am not sure what the "(R2007)" means since the draft PDF looks like it is still from 1997. Does anyone know if there is a way to make this information available for free rather than 30 USD from the ansi.org website? -- View this message in context: http://forum.world.st/Issue-3806-in-pharo-Duration-hours-is-broken-tp3348315... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.