2012/10/24 Camillo Bruni <camillobruni@gmail.com>
the current implementation does not make any sense.
despite the grammatical correctness of (1 hour) and the implied
mistake of (2 hour). I think we should change or remove it!

well, you can actually write 2 hours ;P

But I agree that the API should be improved

https://code.google.com/p/pharo/issues/detail?id=6876



On 2012-10-24, at 14:52, Fabrizio Perin <fabrizio.perin@gmail.com> wrote:
> If it not use I don't know but the message
> 1 hour

yes, but technically 0.5 hour is correct (though silly it does not work
properly..)

> makes sense to me.
>
> cheers,
> Fabrizio
>
> 2012/10/24 Santiago Bragagnolo <santiagobragagnolo@gmail.com>
>
>> 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>
>>
>>> 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