I should add that there are a lot of similar methods with this behaviour on number, there's day, hour, milliSecond, minute, nanoSecond, second, week. If behaviour was changed, or it was simply deleted, it should probably be in all or none of the above to maintain consistency. On 24 Oct 2012, at 1:45pm, Santiago Bragagnolo <santiagobragagnolo@gmail.com<mailto:santiagobragagnolo@gmail.com>> wrote: I found almost no senders of #Number>>hour, and also have not sense at all. Probably we want to remove it. 2012/10/24 Joe Rickerby <joe.rickerby@square-i.net<mailto:joe.rickerby@square-i.net>> I can't believe I'd be the first person to find this, so sorry if this has been discussed before. I was writing some code today, using Durations. I've come across the hour/hours methods before, and so I know that '2 hour' is really one hour, and that you have to write '2 hours' to have the thing work as expected. It's a little strict for the language to do this, but I can see the logic. What doesn't work for me is when I write '0.5 hour' or '(1/2) hour'. Both will return a duration of 1 hour. In my head I pronounce this 'half an hour', so it's an entirely reasonable thing to write. Can something be done about this? Joe